From 2914a51c2ebcc940c9557c0c468c1287903e8664 Mon Sep 17 00:00:00 2001 From: Doug Hellmann Date: Wed, 18 May 2016 16:10:39 -0400 Subject: [PATCH] clarify language about expectations for cycle-with-intermediary releases During Mitaka we had some cycle-with-intermediary projects surprised that the release team wanted them to produce releases at the end of the cycle. This change expands the existing language to clarify that expectation. Change-Id: I673f0d88511966361daad7a9943e0efc360b061e Signed-off-by: Doug Hellmann --- reference/tags/release_cycle-with-intermediary.rst | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/reference/tags/release_cycle-with-intermediary.rst b/reference/tags/release_cycle-with-intermediary.rst index ae700a27f..1c9d3ba83 100644 --- a/reference/tags/release_cycle-with-intermediary.rst +++ b/reference/tags/release_cycle-with-intermediary.rst @@ -57,8 +57,10 @@ choose between the :ref:`tag-release:cycle-with-milestones`, Requirements ============ -* "release:cycle-with-intermediary" projects commit to produce a release to - match the end of the 6-month development cycle. +* "release:cycle-with-intermediary" projects commit to produce a + release near the end of the 6-month development cycle to be used + with projects using the other cycle-based release models that are + required to produce a release at that time. * Release tags for deliverables using this tag are reviewed and applied by the Release Management team.