e458b48e10
With the new resolution '2023-07-24 Unmaintained status replaces Extended Maintenance' [1] non-SLURP releases (starting with 2023.2 Bobcat) are not eligible to move to Unmaintained after their maintained phase. Hence, with this patch 2023.2 Bobcat moves to End of Life. Teams had time to prepare final 2023.2 Bobcat stable releases already, but in case any of the deliverables needs another release (for example to fix a regression) before the transition, then please add a -1 for this patch and propose a release patch. If the team is OK with the transition then please do add a +1. The deadline is (for non-trailing projects) April 30th, 2025. [1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html Change-Id: I5bc866ce5f7fa1e5dfda357738cdda6ddf62987f
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.