From a0e9fb43816a2f4091f77964785c94eb287dfce1 Mon Sep 17 00:00:00 2001 From: Jean-Philippe Evrard Date: Fri, 20 Sep 2019 17:13:22 +0200 Subject: [PATCH] Clarify release-test purpose This is not clear what release-test is for. I expected the repo to be used for final release, as a canary test. I expected things had to done with it beforehand. But I only got a confirmation through IRC (as this is not yet documented in the process), that it only serves during RC/final release time. This should clarify it. Change-Id: I9ba636a8a3147466a1e661c074a050ff14a6d394 --- doc/source/reference/process.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/source/reference/process.rst b/doc/source/reference/process.rst index cf60dc78bf..a019c8cdcb 100644 --- a/doc/source/reference/process.rst +++ b/doc/source/reference/process.rst @@ -322,6 +322,9 @@ RC1 week #. At the same time, generate RC1 release requests (including the ``stable/$series`` branch creation) for all cycle-with-rc deliverables. + Keep in mind you can use `release-test` as a canary test. `release-test` + needs to have a RC1 anyway for preparing the final release. + #. Those patches will be used as a base to communicate with the team: if a team wants to wait for a specific patch to make it to the release, someone from the team can -1 the patch to have it held, or update