10c344971f
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 13.0.0..a7e99a6 a7e99a6 Use TOX_CONSTRAINTS_FILE 05f1453 Imported Translations from Zanata 4e22ba5 Make lower-constraints job non-voting 2722d5a Imported Translations from Zanata af40bc6 Rename jobs from the experimental queue abbc9ae bump py37 to py38 in tox.ini 49cc940 Bump hacking min version to 3.0.1 8149001 Add Python3 wallaby unit tests 9cb1b2b Update master for stable/victoria Signed-off-by: Hervé Beraud <hberaud@redhat.com> Change-Id: Id977b5973020dd1d1133ed835721ec0f40eabf5b
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.