Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

OpenNCP - Release Management - Knowledge Transfer

18th June

Estimated - 13:30 to 14:15 CEST

Performed -  

 

 

AGENDA

...

13:30 to 14:20 CEST

AGENDA

1) Overview of the release management process;

 

...

 

LOCATION

- Wiki+ WorkBench + AdobeConnect

PARTICIPANTS

Today's Meeting Participants:

...

Michele Foucard <Michele.FOUCART@ext.ec.europa.eu>,Invited Members List:

Licinio Mano <licinio.mano@spms.min-saude.pt>,


Invited Members List:

Stéphane Spahni <stephane.spahni@hcuge.ch>,

...

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

RELATED PAGES

 

 

MEETING NOTES

a) Overview of the release management process;

+++++++++++++++

...

...

 

...

-- Nexus Web: https://joinup.ec.europa.eu/nexus/index.html#nexus-search;quick~eu/europa/ec/joinup/ecc

-- JoinUP Nexus - Releases: https://joinup.ec.europa.eu/nexus/content/repositories/releases/

-- JoinUP Nexus - Snapshots: https://joinup.ec.europa.eu/nexus/content/repositories/snapshots/

 

Deploy to JoinUP requires a maven command: "mvn clean deploy” 

To run this command it is needed to config the credentials to repositories in a file on the user root ~/.m2/settings.xml (more information on http://maven.apache.org/settings.html#Servers)

++++++++++++++

 

...

MEETING NOTES

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

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:

    • Steen Manniche
    • Ivo Pinheiro
    • Kostas Karkaletsis

The idea is to have more people engaged with this process. Perhaps someone from the DG-Santé?

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:

...

We should have also some meetings about the Continuous Integration: next step to be taken. (To Be Scheduled after the Release Management Meetings).

ACTIONS NEEDED

Today's meeting actions: