openstack/releases
Code Issues Proposed changes

Merge "move the process document into the published reference guide"

Browse Source
This commit is contained in:
Zuul 2018-07-19 10:23:04 +00:00 committed by Gerrit Code Review
commit 1a40177201
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/release_models
reference/deliverable_types reference/deliverable_types
reference/reviewer_guide reference/reviewer_guide
reference/process

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

@ -119,11 +119,12 @@ Between Milestone-2 and Milestone-3
will control the stable/$series branch prior to release. They will control the stable/$series branch prior to release. They
should reach out to the stable-maint-core group for additions. should reach out to the stable-maint-core group for additions.
2. Notify the Infrastructure team to `generate 2. Notify the Infrastructure team to `generate an artifact signing key`_
<https://docs.openstack.org/infra/system-config/signing.html#generation>`_ (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.
.. _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 5. Two weeks before milestone 3, warn cycle-with-intermediary projects
that had changes over the cycle but no release yet that the release that had changes over the cycle but no release yet that the release
team will tag HEAD of master for their project if they have not prepared team will tag HEAD of master for their project if they have not prepared
@ -258,7 +259,9 @@ RC1
create the stable/$series branch for ``openstack/requirements``. create the stable/$series branch for ``openstack/requirements``.
Then announce that the requirements freeze is lifted from master. 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 create the branch for requirements because tests for the stable
branches of those projects will fall back to using the master branches of those projects will fall back to using the master
branch of requirements until the same stable branch is created, branch of requirements until the same stable branch is created,