Release Vitrage using release candidates
For several releases now, vitrage and vitrage-dashboard have been released only once per cycle, toward the end of the cycle. As explained in the project team guide[1], the cycle-with-rc release model is more adapted to deliverables that are only released once per cycle, by targeting a single release (with one or more release candidates) at the end of the cycle. This change proposes to switch vitrage and its dashboard to this model. [1] https://docs.openstack.org/project-team-guide/release-management.html#choosing-a-release-model Change-Id: I5d84f6eb784a7065078961b136cf6bd2c597b5ab
This commit is contained in:
parent
65d6e6cdc6
commit
08ea4b3ef5
@ -1,6 +1,6 @@
|
||||
---
|
||||
storyboard: openstack/vitrage-dashboard
|
||||
release-model: cycle-with-intermediary
|
||||
release-model: cycle-with-rc
|
||||
team: vitrage
|
||||
type: horizon-plugin
|
||||
repository-settings:
|
||||
|
@ -2,6 +2,6 @@
|
||||
team: vitrage
|
||||
type: service
|
||||
storyboard: openstack/vitrage
|
||||
release-model: cycle-with-intermediary
|
||||
release-model: cycle-with-rc
|
||||
repository-settings:
|
||||
openstack/vitrage: {}
|
||||
|
Loading…
x
Reference in New Issue
Block a user