Difference between revisions of "Release Integration"
From Gcube Wiki
Manuele.simi (Talk | contribs) |
Manuele.simi (Talk | contribs) (→Release Preparation) |
||
| Line 11: | Line 11: | ||
* Align the component to the gCubeTemplate defined here: https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents | * Align the component to the gCubeTemplate defined here: https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents | ||
| − | ** remember that the CHANGELOG.md file must have the current release tag | + | ** remember that the CHANGELOG.md file must have a section that 'tags' the work done in the current release. This tag is expected in the format 'v<version>] [r<release>] - <date>' (see the [CHANGELOG.md](https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents/CHANGELOG.md) template) |
| − | * Remove the | + | * Remove the -SNAPSHOT postfix from the version in the pom on the master branch |
* Create a new subticket of "gCube Release Next" defined here: https://support.d4science.org/issues/17579 | * Create a new subticket of "gCube Release Next" defined here: https://support.d4science.org/issues/17579 | ||
** The subject ticket must uniquely identify the component | ** The subject ticket must uniquely identify the component | ||
| − | + | ||
| + | When the all these steps have been completed the ticket can be set to Available state. The Release Manager is in charge to add all the Available tickets to the new Release. | ||
Once the preparation steps are completed, the integration phase can be started. | Once the preparation steps are completed, the integration phase can be started. | ||
| − | *After the integration phase, the component master branch must be | + | *After the integration phase, the component master branch must be frozen until the release will be declared closed by Release Manager. |
Revision as of 14:39, 19 June 2020
Preliminary steps
In order to develop a new component for gCube, the developer must perform the following steps:
- Upgrade and test the component in development environment
- Deploy the SNAPSHOT version on gcube-snapshots repository
- Add the maven-parent 1.1.0 to the component pom
Release Preparation
In order to prepare a new component for the integration within a gCube release, the developer must perform the following steps:
- Align the component to the gCubeTemplate defined here: https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents
- remember that the CHANGELOG.md file must have a section that 'tags' the work done in the current release. This tag is expected in the format 'v<version>] [r<release>] - <date>' (see the [CHANGELOG.md](https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents/CHANGELOG.md) template)
- Remove the -SNAPSHOT postfix from the version in the pom on the master branch
- Create a new subticket of "gCube Release Next" defined here: https://support.d4science.org/issues/17579
- The subject ticket must uniquely identify the component
When the all these steps have been completed the ticket can be set to Available state. The Release Manager is in charge to add all the Available tickets to the new Release.
Once the preparation steps are completed, the integration phase can be started.
- After the integration phase, the component master branch must be frozen until the release will be declared closed by Release Manager.
