From ed0e471a3cc526633d73c81d3c32d36ce68f6e83 Mon Sep 17 00:00:00 2001 From: Thierry Carrez Date: Fri, 2 Aug 2019 11:36:17 +0200 Subject: [PATCH] Allow multiple releses in cycle-automatic In some cases, teams want to push intermediary releases for cycle-automatic deliverables. This should be OK, as long as cycle-automatic is limited to specific deliverables. Adjust language in the doc to match that. Change-Id: I8bec726892de5d05a90fb7ac84bcf442c057f819 --- doc/source/reference/release_models.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/source/reference/release_models.rst b/doc/source/reference/release_models.rst index 9521273458..62589d3345 100644 --- a/doc/source/reference/release_models.rst +++ b/doc/source/reference/release_models.rst @@ -123,9 +123,10 @@ cycle-automatic =============== The "cycle-automatic" model is used by specific technical deliverables -that just need to be automatically released once (and only once) at the -end of a cycle. Those do not need a stable branch created. This may be -applied only to "tempest-plugin" or "other" deliverables. +that need to be automatically released once at the end of a cycle. +Those may, optionally, also be released in the middle of the cycle. +Those do not need a stable branch created. This may be applied only +to "tempest-plugin" or "other" deliverables. * "cycle-automatic" deliverables will be automatically released by the release team once at the end of a cycle, using the current HEAD of the