From 038e855fb12d3ccea80867346bb40cb77a93fa56 Mon Sep 17 00:00:00 2001 From: Thierry Carrez Date: Thu, 14 Mar 2019 17:50:22 +0100 Subject: [PATCH] Reorder steps on RC1 week process 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 --- doc/source/reference/process.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/source/reference/process.rst b/doc/source/reference/process.rst index 19eedf2f09..b6a39a0755 100644 --- a/doc/source/reference/process.rst +++ b/doc/source/reference/process.rst @@ -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 =====================