OpenNCP Weekly Sprint Meeting
2nd September 15:00 to 16:00 CET
Work RoadMap - epSOS 2 Services
1º Sprint: 28Jan > 8 Fev (2 weeks) > Completed
2º Sprint: 11Fev > 22Fev (2 weeks) > Completed
3º Sprint: 25Fev > 8Mar (2 weeks) > Completed
4º Sprint: 11Mar > 22Mar (2 weeks) Completed
5º Sprint: 25Mar > 8Apr (2 weeks) Completed
6º Sprint: 22Apr> 3May (2 weeks) > Completed
7º Sprint: 6May> 17May (2 weeks) > Completed
8º Sprint: 20May> 31May (2 weeks) > Completed
9º Sprint: 3June> 14June (2 weeks) > Completed
10º Sprint: 24June > 19July (4 weeks) > in Progress
- Release OpenNCP 2.0.1 >
31 July, 2013 (Wednesday) 6th August
ROADMAP
[in progress] OpenNCP V2.0.2 2013-09-10 Transformation Manager + Emergency Scenario + Bug Fixing
OpenNCP V2.0.3 (after PPT) 2013-10-02 OPERATION Ready for: PAC + HCER epSOS 2 Services
OpenNCP V2.1.0 2013-10-30 PPT Ready for: MRO + TSAM-sync (adaptation for CTS2 compliance)
OpenNCP V2.1.1 (after PPT) 2013-12-05 OPERATION Ready for: ??
Agenda
0) OpenNCP Promotion Documentation
a) Bug Fixing
b) Transformation Manager Update
c) Next PPT scope (for PNs moving from V1 to V2)
Location
Skype (sirLicman) + Jira Board + MeetingWords (http://meetingwords.com/xUSZ4A1zfM)
Participants:
MEETING NOTES
0. Documentation
- GW & NR > Review > legal notices (bilateral meeting)
-- LKM: Final Review and epSOS.eu publishing;
a) Bug Fixing
https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=2
b) Transformation Manager Update
- GW & IP (bilateral meeting), to check what still missing
c) Next PPT scope (for PNs moving from V1 to V2)
- draft on a simplified PPT for those switching from OpenNCP1 to OpenNCP2.
Proposed tests for switch from OpenNCP1.x to OpenNCP2.x (after discussion with Eric):
• The tests of previous table are relevant for regression test:
• In the case of regression, in spite of having to pass AT LEAST THREE, we could accept, as in the past the rule of:
- AT LEAST ONE scrutiny test passed per relevant document
- AT LEAST ONE WF test with ONE PN
- AT LEAST ONE e2e functional test with ALL PNs
• In view of a sustainable testing, the discussion in > should be finalised
FI, SW: are aligned with the simplification and believe they can assure the needed effort for the PPT-slot
Konstantin Porposal:
- Continuous PPT environment, where testing tools are always available for quality improvement
- Test Tool
Schedule: late September;
NEXT Steps
- NEXT MEETING - 10 September, 10h00 CET