a37aa9f962
This is a procedural review to transition pike into extended maintenance by creating the pike-em tag. It's possible that the release isn't needed (for example if there are no code changes sine the previous release, sadly that's non-trivial to detect en masse). If you are the PTL or release liaison for this team please +1 this review if it is ready or -1 and take over the review to correct mistakes. Change-Id: I727699d870c2c6544ebe9f463da8753eb39f46f1
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.