openstack/releases
Code Issues Proposed changes

Update cycle-trailing process

Browse Source 
Update process document to reflect changes in the cycle-trailing
deadline.

Change-Id: I428991368f02f2aeaa5dfb8303bbe4b040ba97b7
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis 2018-09-04 12:09:38 -05:00
parent 83ee611f5d
commit 8155e84046
No known key found for this signature in database
GPG Key ID: CE7EE4BFAF8D70C8
1 changed files with 11 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
doc/source/reference/process.rst
View File

@ -389,22 +389,21 @@ Final Release
Post-Final Release
==================
1. The week after the final release, process any late or blocked
#. The week after the final release, process any late or blocked
release requests for deliverables for any branch (treating the new
series branch as stable).
2. The week after the final releases for milestone-based projects are
tagged, use ``propose-final-releases --all`` to tag the existing
most recent release candidates as the final release for projects
using the cycle-trailing model.
3. Ask liaisons and PTLs of cycle-trailing projects to review and +1
the final release proposal from the previous step so their approval
is included in the metadata that goes onto the signed tag.
cycle-trailing Final Release
============================
1. Two weeks after the final release for milestone-based projects,
approve the final release patch created earlier.
#. A week before the cycle-trailing deadline, use
``propose-final-releases --all`` to tag the existing most recent release
candidates as the final release for the cycle-trailing projects.
#. Ask liaisons and PTLs of cycle-trailing projects to review and +1
the final release proposal from the previous step so their approval
is included in the metadata that goes onto the signed tag.
#. On the cycle-trailing deadline approve the final release patch created
earlier.