...

• 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 functionality/interfaces without audit logging BUT we MUST raise the incompatibilities to the Marcello Melgara

[Licinio]

• Why and what where the reasons for 2.x.x breaks 1.x.x

[Konstantin]

• Incompatibilities
  • Specifications concerning audit messages are incompatible;
  • It does not affect semantic interoperability or other interoperability dimensions.
  • ATNA changes?? not yet stable.

...

• Agrees with konstantin
• Thinks: we could just skip the audit logging and focus in interfaces and functionality;

[Marcello Mel]

...

[Fonseca]

• Functional changes are not to big, so it may be possible to merge branches.

[LicinioNext Steps]

• 1st: Licinio > 3 lines email to raise the question to TPM:

  Jira Legacy
  server JIRA (openncp.atlassian.net) key AA-32

  , in order to put it in the risk assessment sheet.
  • TPM and NEPC
  • Risk in software development incompatibilities;
  • Risk of stopping pilots already in operation;
• 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]Gareth]

In the OpenNCP development project we lack a dedicated test team.  Normally there would be test specialists who do test planning and conduct system tests during a sprint.  This is followed by acceptance test when the software goes through a cycle of QA and bug fixing.  I’ve always thought it strange that we don’t follow this practice

3. Development Status

...

• HCER:
  
  • Konstantin: meeting: request to GNOMON for GUI implementation > that Marcello is checking with Gnomon
  • Marcello: negotiation with Gnomon; risk of stop the development of HCER tool - negotiation with PMT and project coordinator;
  • Marcello: conversation with Gnomon regarding LRT and MTC, to manage effort;
  • Konstantin: CDA Specifications and content are clear;
• OpenNCP
  • Portal, TM and TSAM: for sustainability, SHOULD be ready for improvement without of the initial providers.

 

NEXT Steps

...