openstack/releases
Code Issues Proposed changes

move the process document into the published reference guide

Browse Source 
Move our process document into the reference guide published on the
website so it is easier to provide folks with links to explain the
various stages of the cycle.

Adding the new page also requires fixing up some RST warnings so
Sphinx would run properly, and fixing some markup so the rendered page
looked OK.

Change-Id: If6280b60b8802d3908c233a30547ec442cb2804e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit is contained in:
Doug Hellmann 2018-07-17 09:09:11 -04:00
parent 00a9ae9448
commit c35df6fa6f
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
doc/source/index.rst
View File

@ -128,3 +128,4 @@ References
reference/release_models
reference/deliverable_types
reference/reviewer_guide
reference/process

13
PROCESS.rst → doc/source/reference/process.rst
View File

@ -119,10 +119,11 @@ Between Milestone-2 and Milestone-3
will control the stable/$series branch prior to release. They
should reach out to the stable-maint-core group for additions.
2. Notify the Infrastructure team to `generate
<https://docs.openstack.org/infra/system-config/signing.html#generation>`_
an artifact signing key (but not replace the current one yet), and
begin the attestation process.
2. Notify the Infrastructure team to `generate an artifact signing key`_
(but not replace the current one yet), and
begin the attestation process.
.. _generate an artifact signing key: https://docs.openstack.org/infra/system-config/signing.html#generation
5. Two weeks before milestone 3, warn cycle-with-intermediary projects
that had changes over the cycle but no release yet that the release
@ -258,7 +259,9 @@ RC1
create the stable/$series branch for ``openstack/requirements``.
Then announce that the requirements freeze is lifted from master.
Note that we wait until after the other projects have branched to
.. note::
We wait until after the other projects have branched to
create the branch for requirements because tests for the stable
branches of those projects will fall back to using the master
branch of requirements until the same stable branch is created,