openstack/releases
Code Issues Proposed changes

Reorder steps on RC1 week process

Browse Source 
For RC1 week the steps are roughly in chronological order.
In order to get cycle-highlights in time for the deadline,
move that point up.

Change-Id: I40fd38599b0851dd596f9669edd8d26ccedd8c2a
This commit is contained in:
Thierry Carrez 2019-03-14 17:50:22 +01:00
parent f86daa37b0
commit 038e855fb1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -242,6 +242,9 @@ RC1 week
someone from the team can -1 the patch to have it held, or update
that patch with a different commit SHA.
#. Email openstack-discuss list to remind PTLs that cycle-highlights are due
this week so that they can be included in release marketing preparations.
#. By the end of the week, ideally we would want a +1 from the PTL and/or
release liaison to indicate approval. However we will consider the absence
of -1 or otherwise negative feedback as an indicator that the automatically
@ -307,9 +310,6 @@ RC1 week
templates in openstack-zuul-jobs. For example, see
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
=====================