fd872d2048
There were several deliverables set as cycle-with-intermediary that have not been doing intermediary releases. That release model is intended for deliverables that will be releases multiple times throughout the development cycle. With the newer cycle-with-rc release model, teams have the option of not requiring releases during the cycle and just making sure they are done near the end of the cycle. See [1] for more details. This proposes to change this cycle-with-intermediary deliverable to be cycle-with-rc. Please confirm this is acceptable for the team and feel free to ask any questions about this change. [1] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000465.html Change-Id: Iee8d9dfc34b3a3e9cbbd8ca749a538172aa1bb2a Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Using This Repository
All official OpenStack software should go through the Release Management team team to produce releases. Exceptions to this rule are granted by the Technical Committee and documented in the openstack/governance repository ('release-management' key in reference/projects.yaml).
This repository is used to track release requests. Releases are managed using groups of "deliverables", made up of individual project repositories sharing a Launchpad group and a version number history. Many deliverables will only have one constituent project repository.
The repository is managed by the Release Management team.
Refer to the reference documentation for more details
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.