Cloud iNfrastructure Telco Taskforce Technical Release Process ¶
Table of Contents ¶
Scope ¶
The scope of this document is to define the release management and its process for planning, scheduling and controlling the build, in addition to proof reading and release deployment. This document defines the release model by organising the git branches and managing the code and other artefacts efficiently in well-structured format. It should be considered a living document until it is agreed and signed by all the parties.
Release Model ¶
As a guiding principle, all the development occurs in “Master” branch. All the contribution for the milestone (especially M3) goes into ”Master”. After M4 (Proof Reading), at one point in the release candidate (for now maintain Release Candidate 0) for Baldy and based on experience we shall increase or limit what get into the final release. To make this happen, branch out from “Master”, create a delivery branch (“Baldy”, “Baraque”, etc). Developers can continue their next release branch work in “Master”. At the end of each release, artifacts are “tagged” in GitHub according to the guideline and principles defined.
To deliver a fixes into the latest release, simply apply the fixes on the “master” branch and then cherry pick technique will be applied for a particular PR which would agree jointly and tag it (4.0.1-Baldy). In case, if the “master” has evolved significantly then apply the fixes on the latest release branch directly. As shown in the below diagram.
Figure 1: Specimen Release Model
During the development cycle when working with release branches, developers or architects should open up a “pull request” in GitHub so that team members can see what you are preparing to release.
Release Delivery Timeline ¶
The table below captured the list of events, long holidays only, release plan and sign off with corresponding dates. The release plan consists of all the milestones associated with the release candidate.
|
Title |
F eb/20 |
M ar/20 |
A pr/20 |
M ay/20 |
J un/20 |
J ul/20 |
A ug/20 |
S ep/20 |
|---|---|---|---|---|---|---|---|---|
|
E vents |
||||||||
|
ONES NA 2020 |
2 0/Apr to 2 3/Apr |
|||||||
|
ONES - Ant werp, Be lgium (Pro posed Re lease Name: ** Baraq ue**) |
2 9/Sep to 2/Oct |
|||||||
|
Long Hol idays |
||||||||
|
E aster (U K/US) |
1 0/Apr to 1 3/Apr |
|||||||
|
L abour Day (C hina) |
1/May to 5/May |
|||||||
|
D ragon Boat Fes tival (C hina) |
2 5/Jun to 2 7/Jun |
|||||||
|
** Baldy (P ropos ed)** |
||||||||
|
M1 (Re lease Pl annin g/Req uirem ents) |
1/Feb |
|||||||
|
M2 ( Issue Log ging) |
2 1/Feb |
|||||||
|
M3 (F reeze Cont ribut ions) |
[ST RIKEO UT:03 /Apr] |
0 1/May |
||||||
|
M4 (F reeze Proof Rea ding) |
[ST RIKEO UT:09 /Apr] |
0 7/May |
||||||
|
Re lease Cand idate |
[ST RIKEO UT:13 /Apr] |
1 1/May |
||||||
|
Baldy Sig n-Off |
[ST RIKEO UT:17 /Apr] |
1 5/May |
||||||
|
Ba raque (P ropos ed) |
||||||||
|
M1 (Re lease Pl annin g/Req uirem ents) |
2 9/May |
[ST RIKEO UT:17 /Jun] |
||||||
|
M2 ( Issue Log ging) |
1 9/Jun |
[ST RIKEO UT:01 /Jul] |
||||||
|
M3 (F reeze Cont ribut ions) |
1 4/Sep |
|||||||
|
M4 (F reeze Proof Rea ding) |
1 8/Sep |
|||||||
|
Re lease Cand idate |
2 1/Sep |
|||||||
|
Baldy Sig n-Off |
2 5/Sep |
Figure 2: 2020 Release Roadmap
Events ¶
The list of events for the technical F2F planning captured from LGN events. • [STRIKEOUT:ONES NA 2020 (Los Angeles, California) - April 20 & 21. Technical meetings April 22 & 23rd. ] • [STRIKEOUT:LFN DDF (Seoul, South Korea) - June 1-4. ] • ONES Europe 2020 (Antwerp, Belgium) - September 29 & 30. Technical meetings October 1 & 2.
Release Sign-off ¶
|
Name and Title of Approver |
Decision |
Reason for Rejection |
Date |
|---|---|---|---|
|
|
☐ Approved ☐ Rejected |
||
|
|
☐ Approved ☐ Rejected |
||
|
|
☐ Approved ☐ Rejected |
Table 1: Specimen Release Signoff