Revision as of 08:40, 19 June 2020

Preliminary steps

In order to integrate a new component in a gCube release, some preparatory steps (performed by the Developer) are needed:

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 and the current version tag
Remove the snapshot from the master branch
Create a new subticket of gCube Release Next master ticket: https://support.d4science.org/issues/17579
- The subject ticket must uniquely identify the component
When the previos steps are completed the ticket can be set to Available state. The Release Manager is in charge of add all the Available ticket to the new Release.

Once the preparation steps are completed, the integration phase can be started.

@@ Line 1: / Line 1: @@
-= Release Preparation =
+= Preliminary steps =
-In order to integrate a new component in a gCube release, some '''preparatory steps''' (performed by the Developer) are needed:
 * Upgrade and test the component in development environment
 * Deploy the SNAPSHOT version on gcube-snapshots repository
@@ Line 9: / Line 9: @@
-= Release Integration =
+= Release Preparation =
-Once the preparation steps are completed, the integration phase can be started.
+In order to integrate a new component in a gCube release, some '''preparatory steps''' (performed by the Developer) are needed:
-The rules to attach a component to a new gCube Release are the following ones:
 * Align the component to the gCubeTemplate defined here: https://code-repo.d4science.org/gCubeCI/Templates/src/branch/master/gCubeComponents
@@ Line 20: / Line 18: @@
 ** The subject ticket must uniquely identify the component
 * When the previos steps are completed the ticket can be set to Available state. The Release Manager is in charge of add all the Available ticket to the new Release.
+Once the preparation steps are completed, the integration phase can be started.