From 3dbcdcd3eea893bec79e44edff2f680ab18453bd Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Thu, 13 Aug 2020 11:33:40 -0500 Subject: [PATCH] Switch cloudkitty to cycle-with-rc Deliverables following the cycle-with-intermediary model are expected to release multiple times throughout the development cycle. Since cloudkitty 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: I218ebeb6a7659cc714c18720b35c8456c2f02bae Signed-off-by: Sean McGinnis --- deliverables/victoria/cloudkitty.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deliverables/victoria/cloudkitty.yaml b/deliverables/victoria/cloudkitty.yaml index c1d1aaf354..104e99b60d 100644 --- a/deliverables/victoria/cloudkitty.yaml +++ b/deliverables/victoria/cloudkitty.yaml @@ -1,7 +1,7 @@ --- include-pypi-link: true storyboard: openstack/cloudkitty -release-model: cycle-with-intermediary +release-model: cycle-with-rc team: cloudkitty type: service repository-settings: