0ddbf48a96
This tags the final release for all cycle-with-rc projects for Wallaby. 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 Apr 14. Any bugfixes merged to stable/wallaby can be queued up and ready to go as a follow on stable release after the coordinated release date. There are different diff-start values for each project. This is used when generating release notes to denote the point where the stable/victoria branch started to diverge from what is included on stable/wallaby. For some, this will be the final Victoria major version, but if multiple RCs were done, this may show the initial RC1 release version. This is normal. Change-Id: Ia6d79df224a792915976864857fe2271e031b54d
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.