openstack/releases
Code Issues Proposed changes

add release warning and forced release steps to the process

Browse Source 
Change-Id: I910d06b3d7fab38f0c481aa5a8ad9c76fdef36cd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2018-02-02 10:44:46 -05:00
parent 1856af6b1f
commit 92ce471686
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
PROCESS.rst
View File

@ -137,6 +137,12 @@ Between Milestone-2 and Milestone-3
an artifact signing key (but not replace the current one yet), and an artifact signing key (but not replace the current one yet), and
begin the attestation process. begin the attestation process.
5. Two weeks before milestone 3, warn cycle-with-intermediary projects
without any releases that the release team will tag HEAD of master
for their project if they have not prepared a release by the
following week so that there is a fallback release to use for the
cycle and as a place to create their stable branch.
Final Library Release (week before Milestone-3) Final Library Release (week before Milestone-3)
=============================================== ===============================================
@ -159,6 +165,9 @@ Final Library Release (week before Milestone-3)
the final release and import it into a Google Docs spreadsheet for the final release and import it into a Google Docs spreadsheet for
collaborative editing and monitoring. collaborative editing and monitoring.
6. Tag HEAD of master for any cycle-with-intermediary project without
any releases. Do not create branches for non-library projects.
Milestone-3 Milestone-3
=========== ===========
@ -206,6 +215,11 @@ Between Milestone-3 and RC1
master->master instead of previous->master. At the end of Ocata master->master instead of previous->master. At the end of Ocata
this caused trouble for the Ironic team, for example. this caused trouble for the Ironic team, for example.
4. Warn cycle-with-intermediary projects that have releases more than
2 months old that we will use their existing release as a point for
branching if they have not prepared a newer release by the RC1
deadline.
RC1 RC1
=== ===