MEETING TITLE
dd mmm hh:mm to hh:mm CET
Work RoadMap
1º Sprint: 28Jan > 8 Fev (2 weeks) > Completed
2º Sprint: 11Fev > 22Fev (2 weeks) > Completed
3º Sprint: 25Fev > 8Mar (2 weeks) > WE ARE HERE
4º Sprint: 11Mar > 22Mar (2 weeks) (<- both weeks, or perhaps just the last week could be the code freeze?)
- Release date: 25March (Monday) > OpenNCP X.X.X
-- Release Notes
Agenda
- Topic:
Location
...
Release Management Brainstorming
Estimated: 11:00 to 12:00 CET.
Performed: 11:05 to 12:00 CET.
Agenda
- Release management handover
LOCATION
- AdobeConnect:
http://ec-wacs.adobeconnect.com/openncp/
Room Passcode: markus.kalliola or michele.foucart
------------------------------------------------------------------------------------------------
If you have never attended an Adobe Connect meeting before:
Test your connection: http://ec-wacs.adobeconnect.com/common/help/en/support/meeting_test.htm
Get a quick overview: http://www.adobe.com/products/adobeconnect.html
Adobe, the Adobe logo, Acrobat and Adobe Connect are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
------------------------------------------------------------------------------------------------
Participants:
- Alexandre Santos
- Joao Cunha
- ParticipantS
- Participant
- Participant
- Participant
- Participant
- Participant
- Participant
- Participant
Topic
History
...
Components
...
- Release management handover:
The role of the release manager is really important because he is the guardian of the integrity of the source code, release etc.
...
...
...
...
...
...
...
Improvement
...
- is created (https://openncp.atlassian.net/wiki/x/C4BIAQ)
Kostas Karkaletsis proposed to create a master pom file for the OpenNCP release who will manage the version of all components of the concerned release because of the number of components and complexity of the current OpenNCP.
- is created (https://openncp.atlassian.net/wiki/x/C4BIAQ)
...
- Example: OpenNCP-1.0.0 is composend by client-connector-1.0.1 and epsos-ws-server-3.5.0 etc.
It will prevent manual download of the artefacts.
Alexandre Santos: If you build an OpenNCP with master you have to build all components?
TODO: Test faisability
- Example: OpenNCP-1.0.0 is composend by client-connector-1.0.1 and epsos-ws-server-3.5.0 etc.
...
- of the master parent pom.
TODO: Check credentials into
- of the master parent pom.
...
- JoinUp server, who could release an artefact.
- JoinUp server, who could release an artefact.
- Current situation:
Source control tool is Git and hosted into a Bitbucket server (https://bitbucket.org/openncp/) and community release process id described in details Release Management and Release Plan and Actions.
The repository should contain at least 2 branches:
MASTER -->always current production version (for instance: version 1.0.0).
DEVELOP --> source code of next version,
- Current situation:
...
- this branch has to be always
...
- healthy while committing (Jenkins tests and build help to validate the commit).
...
- Version+SNAPSHOT (for instance: 1.1.0-SNAPSHOT).
The gitflow model further operates with feature, release and hotfix branches.
Example: New feature name SMP
- Version+SNAPSHOT (for instance: 1.1.0-SNAPSHOT).
...
- (Gitlfow command in order to create a new branch and start to work here --> then changing
...
- Git repository).
Gitflow finish SMP --
- Git repository).
...
- > merge automatic + delete
...
- new feature branch.
Hotfix from master branch + correct +
- new feature branch.
...
- Gitflow finish --> merge master.
Release --> freeze
- Gitflow finish --> merge master.
...
http://danielkummer.github.io/git-flow-cheatsheet/
...
- source code into DEVELOP branch and changing Pom file.
All of the samples are executed according the following picture who describes the current way to work with branches:
- source code into DEVELOP branch and changing Pom file.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
- :
...