From b922b6dfebf0771f44d2a1a880fc377cdb1f48a6 Mon Sep 17 00:00:00 2001 From: Doug Hellmann Date: Thu, 9 Feb 2017 12:35:53 -0500 Subject: [PATCH] update release process with stronger branch directions Update the release process document to address the issue we ran into with Ironic this cycle because we didn't encourage them strongly enough to branch early enough. Change-Id: Ie864b0e34d9f704dcad7497646117030eb18d1dd Signed-off-by: Doug Hellmann --- PROCESS.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/PROCESS.rst b/PROCESS.rst index fd905e88f8..2575701bc9 100644 --- a/PROCESS.rst +++ b/PROCESS.rst @@ -157,6 +157,16 @@ Between Milestone-3 and RC1 2. Encourage release:independent projects to add the history for any releases not yet listed in their deliverable file. +3. Remind projects using all release models to prepare their new + stable branch request around the RC1 target date. + + As soon as grenade is updated for the new branch (see the RC1 + instructions that follow), projects without stable branches may + start seeing issues with their grenade jobs because without the + stable branch the branch selection will cause the jobs to run + master->master instead of previous->master. At the end of Ocata + this caused trouble for the Ironic team, for example. + RC1 ===