Difference between revisions of "Major/Minor Release Cycle procedure"
From Gcube Wiki
(→Release Preparation) |
(→Components Delivery) |
||
| Line 39: | Line 39: | ||
= Components Delivery = | = Components Delivery = | ||
| − | When a component must be released in a gCube release, it is required to trace all the release phase with a component release ticket (CRT) that contains the status and the history of the | + | When a component must be released in a gCube release, it is required to trace all the release phase with a component release ticket ('''CRT''') that contains the status and the history of the release of the component. |
= Components Integration = | = Components Integration = | ||
Revision as of 11:38, 5 October 2015
Contents
Introduction
This section describes the Release Cycle procedure focusing on activities to be executed and roles involved. The release cycle is supported and partially automated by several tools described in datails in section Tools.
Acronyms List
| CRT | Component Release Ticket |
| EPC | ETICS Project Configuration (e.g. org.gcube.1-6-0) |
| ESC | ETICS Subsystem Configuration (e.g. org.gcube.annotation-management.1-1-0) |
| ECC | ETICS Component Configuration (e.g. org.gcube.annotation-management.abe.1-1-0) |
| Dev | Developer role |
| PRT | Project Release Ticket |
| SMan | Subsystem Manager role |
| SRT | Subsystem Release Ticket |
| RMan | Release Manager role |
| TTeam | the set of Testers |
Release Preparation
When a new release of gCube system is decided, several preparatory activities are request to configure the different tools to host the integration of the new release:
- RMan creates a sprint on the Tracking System for the release (e.g. "Release gCube 3.9.0")
- RMan creates the PRT
{name: <EPC-Name>, status: New, sprint: <Release-Sprint>} - RMan creates the EPC cloning it from org.gcube.HEAD
- RMan updates the PRT
{status: New -> Available}
Components Delivery
When a component must be released in a gCube release, it is required to trace all the release phase with a component release ticket (CRT) that contains the status and the history of the release of the component.
