openstack
/
releases
Code Issues Proposed changes

update the release process steps related to documentation 

After the doc-migration, the release team no longer branches the
openstack-manuals repository. They can also establish the new landing
pages for the soon-to-be-open series earlier, and update the series
status for soon-to-be-released series at the same time.

Change-Id: Ide6522e33bdb213eb8d260cea0352e0a014dedb0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2017-07-31 12:01:24 -04:00
parent 89a385d023
commit e1acee644e
1 changed files with 11 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
PROCESS.rst
View File

@ -298,6 +298,13 @@ candidates are coming.
9. The week before final release test the release process using the
openstack/release-test repository.
10. Notify the documentation team that it should be safe to apply
their process to create the new release series landing pages for
docs.openstack.org. Their process works better if they wait until
most of the projects have their stable branches created, but they
can do the work before the final release date to avoid having to
synchronize with the release team on that day.
Final Release
=============
@ -320,24 +327,20 @@ Final Release
3. Add documentation links on the series page on releases.o.o.
See https://review.openstack.org/#/c/381005 for an example.
4. Notify the documentation team that the final release has been
tagged so they can update the documentation landing page. (They
might wait to do that until the press release is published.)
5. Mark series as released on releases.o.o, by updating doc/source/index.rst
4. Mark series as released on releases.o.o, by updating doc/source/index.rst
and doc/source/$series/index.rst.
See https://review.openstack.org/#/c/381006 for an example.
6. Update the default series name in
5. Update the default series name in
``openstack/releases/openstack_releases/defaults.py`` to use the
new series name.
7. Send release announcement email to
6. Send release announcement email to
``openstack-announce@lists.openstack.org``, based on
``templates/final.txt``. Coordinate the timing of the email with
the press release from the Foundation staff.
8. Declare ``openstack/releases`` unfrozen.
7. Declare ``openstack/releases`` unfrozen.
Post-Final Release
==================
@ -372,10 +375,3 @@ cycle-trailing Final Release
2. Remove the refs/heads/stable/$series from the project gerrit
ACLs. This can be done by reverting the original ACL patch.
R+4 Branch Documentation Repos
==============================
1. The documentation team waits to branch their repositories until a
few weeks after the final release. Be available to help with
creating the branches if needed.