afe857035a
Since we merged the fixes for CVE-2023-2088, we need to use a minor version for the new release. $ git log --oneline --no-merges 27.0.0..f361ce2ab1 09f85a8a92 CI: fix backport validator for new branch naming 6eab57952e Bump nova-ceph-multstore timeout a02f966873 Revert "Debug Nova APIs call failures" eb3fe4ddc6 Have host look for CPU controller of cgroupsv2 location. 1f781423ee Enable use of service user token with admin context efb01985db Use force=True for os-brick disconnect during delete fa2ba3ab2c Handle zero pinned CPU in a cell with mixed policy 2cf835be82 Reproduce asym NUMA mixed CPU policy bug acb511652c Save cell socket correctly when updating host NUMA topology 29e3f2f2ab Reproduce bug 1995153 47b6850bb1 (gerrit/stable/2023.1) [stable-only] Update TOX_CONSTRAINTS_FILE for stable/2023.1 d081938e22 [stable-only] Update .gitreview for stable/2023.1 Change-Id: I3454f91a07545779776a016e97cb716c536aa9df |
||
---|---|---|
data | ||
deliverables | ||
doc | ||
openstack_releases | ||
templates | ||
tools | ||
.gitignore | ||
.gitreview | ||
.stestr.conf | ||
.zuul.yaml | ||
bindep.txt | ||
CONTRIBUTING.rst | ||
LICENSE | ||
README.rst | ||
requirements.txt | ||
setup.cfg | ||
setup.py | ||
test-requirements.txt | ||
tox.ini | ||
watched_queries.yml | ||
yamllint.yml |
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.