ca8fd89f22
This proposed a RC1 release for networking-bagpipe to get any merged changes out prior to the RC1 deadline for Antelope going into effect. If the team is ready to proceed, please leave a +1 to acknowledge this release and we will process right away. If the team is working on any final merges, leave a -1 with some detail on the status and update the patch with the new commit hash to use when ready. Patches with no response will be merged by early Friday, March 03. $ git log --oneline --no-merges 17.0.0..c061c4a c061c4a Change IPDB to NDB 0d094ba Tox4: add allowlist_externals where necessary af560a7 CI: Add openstack-tox-py39-with-oslo-master to periodic weekly queue 7a02ee3 Add required projects where necessary 61798ad Switch to 2023.1 Python3 unit tests and generic template name cb9efc1 Update master for stable/zed Signed-off-by: Hervé Beraud <hberaud@redhat.com> Change-Id: Ib0b89e2238565a7651dceeeaf0e5422ea61003d0
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 OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.