cec56b4c6d
During the Stein cycle we introduced three process changes: - no longer forcing releases around milestones for cycle-with-milestones deliverables, and autogenerating RC1 release requests [0] - triggering releases for libraries at every milestone if they had changes that were not otherwise released since the previous milestone [1] - switching cycle-with-intermediary services to cycle-with-rc if they did not do any intermediary release by milestone-2 [2] We failed to update process accordingly. These changes add a couple of steps in the release process, and makes a few other irrelevant. [0] http://lists.openstack.org/pipermail/openstack-dev/2018-September/135088.html [1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135689.html [2] http://lists.openstack.org/pipermail/openstack-discuss/2018-December/000465.html Change-Id: Id53275e73bc19418307d7197d7c2f29c09b0233c
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.