587486903d
Minor version bump due to patch: * Ie904d1513b5cf76d6d5f6877545e8eb378dd5499 (Add a WA flag waiting for vif-plugged event during reboot) $ git log --oneline --no-merges 23.1.0..HEAD 5b7cb876ba skip test_tagged_attachment in nova-next 80572cef67 workarounds: Add libvirt_disable_apic dad566614c Migrate RequestSpec.numa_topology to use pcpuset b190c30f00 Reproduce bug 1952941 5f2f283a75 [rt] Apply migration context for incoming migrations 94f17be190 Extend the reproducer for 1953359 and 1952915 d8859e4f95 Reproduce bug 1953359 6c3d5de659 Ensure MAC addresses characters are in the same case 89c4ff5f7b Add a WA flag waiting for vif-plugged event during reboot f950cedf17 Clear rebalanced compute nodes from resource tracker c260e75d01 Add functional regression test for bug 1853009 c8b04d183f Store old_flavor already on source host during resize 140ae45d98 Reproduce bug 1944759 0cd4ef2dcd Parse alias from domain hostdev 2bee83b8a9 compute: Avoid duplicate BDMs during reserve_block_device_name 7a9e3dcd17 Add functional test for bug 1937375 Change-Id: I18daba992c54edeb46af92411e309c3cf57eaa56 |
||
---|---|---|
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.