openstack/releases
Code Issues Proposed changes

Add Cycle-Highlights to process.rst

Browse Source 
Cycle highlights are now a regular part of a release and should
be included in the process document so we can promote and
collect them in a routine manner.

Change-Id: I025c029469e3fae85485b87351da9ec487ff5c89
This commit is contained in:
Kendall Nelson
2019-02-11 14:34:25 -08:00
committed by Sean McGinnis
parent f526b5dc54
commit e073100963
1 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -206,6 +206,10 @@ Milestone-3
tools/aclissues.py ../project-config ../governance tools/aclissues.py ../project-config ../governance
#. Email openstack-discuss to give PTLs a heads up to start thinking about
what they might want to include in their deliverables file as cycle-highlights
and that RC1 is the deadline for them.
Between Milestone-3 and RC1 Between Milestone-3 and RC1
=========================== ===========================
@@ -220,6 +224,9 @@ Between Milestone-3 and RC1
tox -e venv -- propose-library-branches --include-clients tox -e venv -- propose-library-branches --include-clients
#. Include a reminder in the weekly countdown email reminding PTLs of the
RC1 deadline for cycle-highlights.
RC1 week RC1 week
======== ========
@@ -295,6 +302,8 @@ RC1 week
templates in openstack-zuul-jobs. For example, see templates in openstack-zuul-jobs. For example, see
https://review.openstack.org/545268/. https://review.openstack.org/545268/.
#. Email openstack-discuss list to remind PTLs that cycle-highlights are due
this week so that they can be included in release marketing preparations.
Between RC1 and Final Between RC1 and Final
===================== =====================