openstack/releases
Code Issues Proposed changes

Merge "Add some branch prep steps to the process doc"

Browse Source
This commit is contained in:
Zuul 2020-05-27 11:47:38 +00:00 committed by Gerrit Code Review
commit 0a18586488
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -480,6 +480,9 @@ Between Milestone-2 and Milestone-3
R-8 week
========
#. Make sure the next development series name has been added to the
``data/series_status.yaml`` file.
#. Send the following weekly email content::
Development Focus
@ -556,6 +559,18 @@ R-7 week (Extra-ATC deadline week)
.. _generate an artifact signing key: https://docs.openstack.org/infra/system-config/signing.html#generation
#. Check with the Technical Committee to make sure Python runtimes have been
determined for the next development cycle and that Zuul job templates have
been created to include those runtimes.
The upcoming release deadlines may include the creation of stable branches.
When that branching is performed, automated patches will be proposed to the
master branch of those repos to switch them over to the next cycle's job
template. If the template is not defined yet, those patches will get a Zuul
error. A recheck of failed patches will clear that up once the template is
defined, but it is best if any errors can be avoided to make sure the
patches get approved in a timely manner.
#. Send the following weekly email content::
Development Focus