openstack/releases
Code Issues Proposed changes

update release process with stronger branch directions

Browse Source 
Update the release process document to address the issue we ran into
with Ironic this cycle because we didn't encourage them strongly enough
to branch early enough.

Change-Id: Ie864b0e34d9f704dcad7497646117030eb18d1dd
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann
2017-02-09 12:35:53 -05:00
parent 2010a24353
commit b922b6dfeb
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
PROCESS.rst
View File

@@ -157,6 +157,16 @@ Between Milestone-3 and RC1
2. Encourage release:independent projects to add the history for any
releases not yet listed in their deliverable file.
3. Remind projects using all release models to prepare their new
stable branch request around the RC1 target date.
As soon as grenade is updated for the new branch (see the RC1
instructions that follow), projects without stable branches may
start seeing issues with their grenade jobs because without the
stable branch the branch selection will cause the jobs to run
master->master instead of previous->master. At the end of Ocata
this caused trouble for the Ironic team, for example.
RC1
===