openstack/releases
Code Issues Proposed changes

Improve cycle end/beginning process documentation

Browse Source 
There were some inaccuracies and some missing information for some of
the tasks to be performed between cycles.

Change-Id: I48af839c200b316c28185cd992a83c996dd740e4
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis
2019-09-16 13:26:32 -05:00
parent 78b8bf44cb
commit ef31f7a022
1 changed files with 20 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -14,13 +14,18 @@ Before PTG (after closing previous release)
#. Update the link to the documentation on the newly opened cycle page #. Update the link to the documentation on the newly opened cycle page
to point to the right place on docs.openstack.org. to point to the right place on docs.openstack.org.
#. Create the $series-relmgt-tracking etherpad using ``tools/list_weeks.py``. #. Create the $series-relmgt-tracking etherpad using the
``make-tracking-etherpad`` command.
For example:: For example::
tools/list_weeks.py t 2019-04-15 2019-10-16 tox -e venv -- make-tracking-pad ussuri
#. Use ``init-series`` to create stub deliverable files based on the The output from this command can be pasted into a
contents of the previous release. ``$SERIES-relmgt-tracking`` etherpad. Set title formatting for the top
sections. Then highlight all listed weeks and set to **Heading 3** style.
Fill in the contents of one of the weeks with the typical items, then copy
and past that into each subsequent week to prepare for the rest of the
cycle.
Between Summit and Milestone-1 Between Summit and Milestone-1
============================== ==============================
@@ -511,3 +516,14 @@ Post-Final Release
#. Remind PTLs of cycle-trailing projects to prepare their releases. #. Remind PTLs of cycle-trailing projects to prepare their releases.
#. Plan the next release cycle schedule based on the number of desired weeks or
by making sure the cycle ends within a few weeks of the next developer
event. Using the first Monday following the close of the last cycle, and the
Monday of the planned last week of the new cycle, use the tool
``tools/weeks.py`` to generate the release schedule YAML file. For example::
./tools/list_weeks.py t 2019-04-15 2019-10-16
The generated output can be used to set up the schedule similar to what was
done for the `Ussuri release <https://review.opendev.org/#/c/679822/>`_.