OpenNCP Weekly Sprint Meeting
26th August 11:00 to 12: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
Agenda
a) Dissemination documentation progress
b) Bug Fixing progress
c) TransformationManager update progress
d) RoadMap consolidation (dates and features included)
Location
Skype (sirLicman) + Jira Board + MeetingWords (http://meetingwords.com/csPSTM2Iwm)
Participants:
MEETING NOTES
a) Dissemination documentation progress
- LKM: shared the terms for the glossary;
-- Kathrin: witing feedback;
-- Marcello: for the website, it is enough to provide 1 line: "an Open Source version is publicly made available.
-- [ACTION] LKM: epSOS Technical Aspects >
-- [ACTION] Norbert Review available 30 August!!!,
---- [NR] Short Note: On Tuesday (27/08/2013) and Friday (30/08/2013) I am out of office, so in the worst case the review will be completed on Monday. thx.
b) Bug Fixing progress
https://openncp.atlassian.net/secure/RapidBoard.jspa?rapidView=2
- (Gareth available today and tomorrow): - dificult to understand what has changed since last version
d) RoadMap consolidation (dates and features included)
- PPT need for PNs that adopt 2.0.2?
-- [LKM] OpenNCP Recommendation to TPM
-- [OpenNCP Comm] believes that there is no need for doing that;
-- [MM] Relaxation may be accepted by TPM, but each PN is responsible for there implementation;
-- [MM] which are the minimal test to do, having in mind jump from V1 to V2 (Simplification PPT)???
---- [KTT] all PPT tests could be skipped, except documents validation and e2e testing;
---- [NR] A test has meaning and purpose only when it is performed as detailed as possible. I´v tried it in the past with ClosedSourceOpenNCP incl. Scrutiny tests and so on. Only in this case is it possible to detect errors. But we have reached such a stage in the project where the requirements to fulfill and to behave consistently becomes more difficult. This role should be adopted and monitored by the regression automation, where possible.
---- [GW] We totally agree that a suite of regression tests should be performed when changing version, minor or major doesn't really matter. Both maj/min releases can potentiallyt introduce new bugs
---- [GW] we feel that regression tests hsould be a subset of the ppt test suite. countries upgrading a version and doing ppt should do regression tests only, not full ppt
---- [GW] full ppt requires large effort from country. this will deter countries from upgrading, many may choose to stay on old version., this creates maintenance problems
---- [LKM] the V1 to v2 jump also had big improvments and bug fixes. What tests should be done regarding those changes? Post this uqestion to Kostas and Marcelo fonseca
---- Probably the solution may be NOT REGRESSION TEST but a simplified QA stage before entering operation with new version.
- RoadMap
OSS NCP V2.0.2 2013-09-10 Transformation Manager + Emergency Scenario + Bug Fixing
OSS NCP V2.0.3 (after PPT) 2013-10-02 OPERATION Ready for: PAC + HCER epSOS 2 Services
OSS NCP V2.1.0 2013-10-30 PPT Ready for: MRO + TSAM-sync (adaptation for CTS2 compliance)
OSS NCP V2.1.1 (after PPT) 2013-12-05 OPERATION Ready for: ??
NEXT Steps
- Next meeting - 2nd - September 15h00 CET