openstack/releases
Code Issues Proposed changes

Fix schedule generation instructions

Browse Source 
Change-Id: Iebbd751f0e25364cd35f3153cc908911b8c062e9
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
This commit is contained in:
Sean McGinnis 2020-02-14 11:18:11 -06:00
parent 4f58927795
commit 13c2870029
No known key found for this signature in database
GPG Key ID: CE7EE4BFAF8D70C8
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -303,9 +303,10 @@ Between Milestone-2 and Milestone-3
#. 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
event. Using the Monday of 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`` to generate the release schedule YAML file.
For example::
./tools/list_weeks.py t 2019-04-15 2019-10-16