From 59953f787a1517f2cb526b4f87efb8f30a38f77b Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Thu, 13 Aug 2020 11:33:53 -0500 Subject: [PATCH] Switch networking-baremetal to cycle-with-rc Deliverables following the cycle-with-intermediary model are expected to release multiple times throughout the development cycle. Since networking-baremetal only released once last cycle, and has not done a release yet this cycle, this proposes changing the release model to cycle-with-rc so the expectation is only that it will release an RC by the end of the cycle prior to doing the final release. This is just a suggestion for the team to consider. The important point is past the milestone-2 point, downstream planning starts happening for what will be included in the release. We just want to try to avoid the situation where downstream expects something to be included, but we need to unexpectedly drop it from the coordinated release late in the cycle. For the team, please respond to this patch in one of the following ways: * -1 this patch and follow up with an intermediary release * +1 this patch and we will switch over the release model * -1 this patch, but acknowledge a release will be done prior to the RC1 deadline. Change-Id: I3467602aeeb80979a16cc10a8eeb788fbbad98c5 Signed-off-by: Sean McGinnis --- deliverables/victoria/networking-baremetal.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deliverables/victoria/networking-baremetal.yaml b/deliverables/victoria/networking-baremetal.yaml index 8c658cbc96..fe500597a3 100644 --- a/deliverables/victoria/networking-baremetal.yaml +++ b/deliverables/victoria/networking-baremetal.yaml @@ -2,7 +2,7 @@ storyboard: openstack/networking-baremetal team: ironic type: other -release-model: cycle-with-intermediary +release-model: cycle-with-rc include-pypi-link: true repository-settings: openstack/networking-baremetal: {}