964b41f1f5
During the tag-releases job for the "Tag stable/ocata as extended maintenance" patch d57f810ad6555528a4af039b693453b551da4cf2, the job timed out processing all affected repos. There were just a few that need to have the job run again to push up the tag. This makes a noop change in those repos to get the tagging to complete. Change-Id: Iae06ecaca1059bf761d21b91eb5b7e5dd5d2519a 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.