OpenNCP - Release Management - Knowledge Transfer

20th July

Estimated - 13:00 to 14:00 CEST

Performed -  13:00 to 13:45 CEST

AGENDA

1) Overview of the release management process;

...

PARTICIPANTS

Today's Meeting Participants:

...

Michele Foucard <Michele.FOUCART@ext.ec.europa.eu>,

Invited Members List:Jerome Subiger <jerome.subiger@ext.ec.europa.eu>,

(holidays) Rui Alves <rui.alves@spms.min-saude.pt>,

(holidays) Markus Kalliola <markus.kalliola@ec.europa.eu>,Jerome Subiger <jerome.subiger@ext.ec.europa.eu>,

Invited Members List:

Yacoubou Waolany <yacoubou.waolany@ext.ec.europa.eu>,

...

Luca Pagliara <luca.pagliara@cnt.lispa.it>,

RELATED PAGES

• Release Management: https://openncp.atlassian.net/wiki/x/OQCp
  • Maintaining legacy branches (aka the 1.1.n vs. 2.x shootout):https://openncp.atlassian.net/wiki/x/HoDD
  • Release Plan and Actions: https://openncp.atlassian.net/wiki/x/XQAYAw
    
    
• OpenNCP Releases:https://openncp.atlassian.net/wiki/x/GoAmAg
  
• OpenNCP Release Notes:https://openncp.atlassian.net/wiki/x/C4BIAQ
  • 2.2.0 Release Changelog and Notes:https://openncp.atlassian.net/wiki/x/EgFPAw
    
    
• Version Management:https://openncp.atlassian.net/wiki/x/CQB9
  
  
• Continuous Integration Workflow: https://openncp.atlassian.net/wiki/x/F4BL
• Integration of CI Environment With Gazelle Services: https://openncp.atlassian.net/wiki/x/MIDh

...

• Latest Release Management Meeting: https://openncp.atlassian.net/wiki/x/UAAYAw

MEETING NOTES

1) Overview of the release management process (Licínio)  Release management process 

a) Developer's Corner

i) Release Management

Assure that the final artifacts are uploaded to JoinUp -> Release. Who is responsible? Release Manager.

The OpenNCP Release Manager history:

...

markus.kalliola: Yes This role fits the EC. Maybe Jerome or Yacoubou.

ii) Release Notes

Example: 1.2.1 - Version Numbering

Lists all the components affected.

Shows what has changed...

The credentials for the JoinUp repository are currently held by Licinio Kustra Mano and Kostas Karkaletsis.

The work from the Release Manager goes beyond...

• Identify what is a major or minor Release, what is Release Candidate... We use the gitflow semantics.
• Responsible to prepare branches and assure that the code is placed in the right place...

iii) Release Plan and Actions

Kostas Karkaletsis is the key person to explain the actions on this page;

Distinguish Developers from Users:

• Developers: contribute with code;
• Users: Most likely are the countries that will adopt the code.

Update JIRA Projects:

• Support
• Development (new things)

We have to pay attention to the fields of the issues: OpenNCP Version affected and Fix version.

When there is a release: Send an e-mail to the community (you can find examples in the comment section of some of the Release Notes)

michele.foucart: Who decides what to be released? Which changes are validated by whom?

Licinio Kustra Mano:

Governance Model Page

There is the Steering Board, Technical Comitte (who includes Release Management) and the Development Team;

BiWeekly Meetings join everyone to make such decisions, get questions and evetually open issues, etc.

michele.foucart: About Testing and Quality Analysis: Is there a link for test scenarios? Regression Tests? And the acceptance criteria?

Licinio Kustra Mano:

Continuous Integration Workflow Page

Integration Testing - Automated

We do not have Regression Testes - these are made by the countries - we do unit testing and integration testing

•  michele.foucart may identify some lacks on this page and share them later.

...

Licinio Kustra Mano:

Another "awesome" page related to CI: Integration of CI Environment With Gazelle Services:

Let's schedule a next meeting having the Release Manager:

•  Rui Alves (Unlicensed) to set up a Doodle checking everyone's availability for next week.

...

 [ Licinio Kustra Mano explained this one during the 1st Tcon  ]

ii) Release Notes [ Licinio Kustra Mano explained this one  1st Tcon  ]

iii) Release Plan and Actions [ Kostas Karkaletsis explained this one  2nd Tcon  ]

• • • Kostas Karkaletsis: alerted local repository issues when releasing, its important to clean the local repositories..
      • If the release is made with Jenkins its no additional measures are needed.
        •  But if it is made manually in your local machine, there is the need for cleaning local repositories in order to assure no deprecated artefacts are included in the release packages.
    • Alexandre Santos: 
      • raises some issues connected to the Continuous Integration process, namely how the release management process is related with the Continuous Integration.
      • there is also the concern on how much the current process of CI will be affected by the announced moving from Jenkins to Bamboo.

2) EOB

• michele.foucart: is taking over the responsibility of the migrating process of the Continuous Integration Server (currently using Jenkins at iUZ).
  • This topic should now gather our attention taking in consideration the deadline presented by iUZ (end September) 

ACTIONS NEEDED

Today's meeting actions:

•  michele.foucart may identify some lacks on this page and share them later.
•  Rui Alves (Unlicensed) to set up a Doodle checking everyone's availability for next week.
• Licinio Kustra Mano: Next release will be handled by the @Alexandre and @João supervised by @Kostas, and observed by @Jerome
•  Kostas Karkaletsis: Will work to enhance the topic description taking in consideration the most challenging tasks to be done during the process;
•  michele.foucart: Schedule a CI meeting for 2 weeks from now, 31st July 10h00 CEST (proposed agenda: a) Follow up release management activities; b) Progress monitoring of CI migration)

...