2ea5afe2ce
This is largely to clean up any pending doc and test changes in the Oslo projects. Normally those don't require a release, but because stable branches are created based on the latest release hash, we need to release these changes so they will be present on the stable branches. Otherwise we end up having to backport changes unnecessarily. Change-Id: I4f3b9ea53f61b869bcc329ea18990795f40a4769
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.