Difference between revisions of "Release Integration"

From Gcube Wiki
Jump to: navigation, search
(Release Preparation)
(Release Preparation)
Line 15: Line 15:
 
* 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.
  
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.
+
Then, the '''Release Manager''' is in charge to add all the Available tickets to the new Release and the '''integration phase''' of the new release can start.
  
Once the preparation steps are completed, the integration phase can be started.
+
*During the integration phase, the master branch of each component under release must be frozen until the release is declared closed by Release Manager. As per feature branching policy, any work must be performed in a separate feature or fix branch.
 
+
*After the integration phase, the component master branch must be frozen until the release will be declared closed by Release Manager.
+

Revision as of 13:44, 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:

Then, the Release Manager is in charge to add all the Available tickets to the new Release and the integration phase of the new release can start.

  • During the integration phase, the master branch of each component under release must be frozen until the release is declared closed by Release Manager. As per feature branching policy, any work must be performed in a separate feature or fix branch.