OpenNCP - Strategic Release Plan
15 Mar 08:30 to 09:30 CET
Work RoadMap
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) > WE ARE HERE (<- both weeks, or perhaps just the last week could be the code freeze?)
- Release date: 25March (Monday) > OpenNCP 2.0.0
-- Release Notes
Agenda
- Release Management Plan
- QA Process - Team
- Development Status
Location
Skype: skype: steen.manniche (if Steen not available: sirLicman)
Participants:
Licinio Mano <licinio.mano@iuz.pt>,
Gareth Woodham <Gareth.Woodham@apotekensservice.se>,
Steen Manniche <STMA@ssi.dk>,
Alexander Berler (a.berler@gnomon.com.gr) <a.berler@gnomon.com.gr>,
Anders Nyström <Anders.Nystrom@apotekensservice.se>,
Arnaud Gaudinat <arnaud.gaudinat@hesge.ch>,
Fredrik Dahlman <fredrik.dahlman@cag.se>,
Gergely Heja <heja.gergely@eski.hu>,
Ivo Pinheiro (ivo.pinheiro@iuz.pt) <ivo.pinheiro@iuz.pt>,
Konstantin Hypponen <konstantin.hypponen@kela.fi>,
Kostas Karkaletsis <k.karkaletsis@gnomon.com.gr>,
Marcello Melgara <Marcello.Melgara@cnt.lispa.it>,
Marcelo Fonseca <marcelo.fonseca@iuz.pt>,
Mika Myllyvirta <mika.myllyvirta@kela.fi>,
Mindaugas Ajauskas <mindaugas.ajauskas@lispa.it>,
Norbert Repas <norbert.repas@elga.gv.at>,
Stefan Gustafsson (stefan.gustafsson@callistaenterprise.se) <stefan.gustafsson@callistaenterprise.se>,
Aarne Roosi (Aarne.Roosi@affecto.com) <Aarne.Roosi@affecto.com>,
Stéphane Spahni <stephane.spahni@hcuge.ch>
Giorgio Cangioli <giorgio.cangioli@gmail.com>
1. Release Management Plan (2 versions vs 1 version)
[Marcelo Marcello Mel]
- We are few in the OpenNCP Community
- We should not proliferate technical solutions
- We should not start something call 2.x and maintain something call 1.x.
- 2.0.0 should be fully compliant with the the 1.x.x
- Work for sustainability, to many branches will be difficult to maintain in the future.
- Witch are the audit messages incompatibilities?
- Should we rise the issue in order to avoid the incompatibilities?
...
- Agrees with konstantin
- Thinks: we could just skip the audit logging and focus in interfaces and functionality;
[Marcelo Marcello Mel]
- Agrees with functionality/interfaces without audit logging BUT we MUST raise the incompatibilities to the Marcelo MelgarraMarcello Melgara
[Fonseca]
- Functional changes are not to big, so it may be possible to merge branches.
[Licinio]
- 1st: Licinio > 3 lines email to raise the question to TPM:
, in order to put it in the risk assessment sheet.Jira Legacy server JIRA (openncp.atlassian.net) key AA-32 - TPM and NEPC
- 2nd: Prepare a WikiPage about mitigation plan regarding version merging
- Current Release plan: Maintaining legacy branches (aka the 1.1.n vs. 2.x shootout)
2. QA Process - Team
[to do]
3. Development Status
[to do]
...