6b2e5831e9
These are the final release taggings for all cycle-with-rc projects. While not required, having PTLs ack this patch would be nice to include that record in the merged metadata. Release activity should now be frozen until this is processed on May 13. Any bugfixes merged to stable/ussuri can be queued up and ready to go as a follow on stable release after the coordinated release date. Since it always comes up - yes, the diff-start is right. That's the calculated starting point where the last stable branch was created. Change-Id: I66602ca7a6ab1af35bf33d4d82fe34191f2e3865 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
OpenStack Releases
This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the https://releases.openstack.org/ website.
Changes to this repository are proposed using Gerrit at https://review.opendev.org. This repository is managed by the OpenStack Release Management team.
For more information on how to use this repository, please read our reference documentation.
Who should use this repository
All official OpenStack software should go through the OpenStack 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).
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.
More information
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.