4cf2670c1f
Shamelessly steal^Wcopy some of the code from interactive-release so that after validating the release we list the changes that will be released. This gives us the ability to decide that the release contains no functional changes and elect to not create that release. NOTE: I chose not to use interactive-release as it seems not to correctly handle first releases in a series (because it doesn't load all release history. It also doesn't use some of the new features (like series_status). Adding --interactive to new-release gets us a long way to deprecating interactive-release but we aren't quire there yet. Change-Id: I25bbb4d7df9ae618500dd37f4b0cbc32c0bbd153
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.