f8e0ad1771
If you wants to wait for a specific patch to make it to the release, someone from your team can -1 the patch to have it held, or update that patch with a different commit SHA. Patches with no response will be merged by Friday March 26. $ git log --oneline --no-merges 2.0.0..fc97cee Signed-off-by: Hervé Beraud <hberaud@redhat.com> Change-Id: I2f3c87f044a96330d0dbe95c80570b50e7ef87d7
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.