OpenNCP Weekly Sprint Meeting
21 MAY 10:00 to 11: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) (<- both weeks, or perhaps just the last week could be the code freeze?) Completed
- Release date: 25March (Monday) > OpenNCP 2.0.0 > Postpone
5º Sprint: 25Mar > 8Apr (2 weeks) Completed
- Release date: 10Apr (Thursday) > OpenNCP 1.1.2 > Completed (Release Notes)
- Release date: 11Apr (Thursday) > OpenNCP 2.0.0 > Postpone
6º Sprint: 22Apr> 3May (2 weeks) > Completed
- Release date: 8May (Wednesday) > OpenNCP 1.1.3 > Completed (Release Notes)
7º Sprint: 6May> 17May (2 weeks) > in progress
- Release date: 22 May (Thursday) > OpenNCP 2.0.0 (planned)
Agenda
1. PAC Demonstration progress
2. HCER Development progress
3. Test Automation Implementation progress
4. OpenNCP version merging progress (1.1.3 to 2.0.0)
Location
Skype (sirLicman) + EtherPad (not available)
Participants:
MEETING NOTES
1. PAC Demonstration progress
- [MF] Demonstration IMPEDED:
--- [MF] Will double check the fix announce by CareCom and verify if any other intervention is needed;
--- [MF] PAC Service: It will no be ready for 22nd May;
--- [MM] For PAC we should use the validate the document with PS Schematron and Model based validators;
+++++++++++++++++++++++
Terminology Central Services
-- Service down (Waiting for answer about the issue)
-- Service down (Waiting for answer about the issue)
-- Translation Only, Sync Not Possible, Still under migration work
-- Sync Not Possible, Still under migration work
+++++++++++++++++++++++
2. HCER Development progress
-- [MM - Impediment] The TM and TSAM (PoSam) - they will be release in June 3.
3. Test Automation Implementation progress
-- ACTION: Try to schedule a meeting with Mustafa, having as framework Norbert email;
- [LM] Unfortunately there was no member available for implement the "Test Automation" mechanisms.
4. OpenNCP version merging progress (1.1.3 to 2.0.0)
- [IP] Request for comments:
1. Merge branch release/1.1.3 with develop branch
2. If critical issues need to be solved it will be created an hotfix branch from master to fix this issues.
3. This should be the strategy to be used from now on:
-- For the critical issues: should be created an hotfix branch that, after the issues are solved should be merged with master branch and develop branch.
-- For new features/developments: the new developments should be made on the develop branch.
- [LKM] The merge will occur in the beginning of the next week: 21 and 22 May.
- [Mustafa] 4th PPT-slot as May 27th - June 7th.
NEXT Steps
- [To Do - Licinio] Schedule 'next' meeting - proposed date May 28st, 2013, 10h00 CET