1bf550353a
This can take a long time now with doing the final release tag validation when all deliverables are included in one patch. Part of the delay appears to be that pbr was updated to build release notes if reno is present. We may look for other ways to optimize the validation jobs to speed things up, but for now we can just make sure we have a very large window. Change-Id: I248968bca9a90a7b06d4d6dd0644c50d926e5f45 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.