5121f611cc
$ git log --oneline --no-merges 22.0.0..HEAD 059d53d4c3 Modify glance's copy_image permission for nova-ceph-multistore d8b8a8193b Update pci stat pools based on PCI device changes a06e27592f Fix the compute RPC 5.12 issue 239ffff2ab Add a regression test for 5.12 compute API issue a919cc0cbd [doc]: Fix glance image_metadata link 048a3337a8 libvirt: Only ask tpool.Proxy to autowrap vir* classes 115fe350ad Fix virsh domifstat to get vhostuser vif statistics 45a4110d20 Handle disabled CPU features to fix live migration failures fd7c66f61c libvirt: 'video.vram' property must be an integer f1e4f6b078 Follow up for cherry-pick check for merge patch 4819f694b2 libvirt: Increase incremental and max sleep time during device detach 7baca2b1d1 [stable-only] Update TOX_CONSTRAINTS_FILE for stable/victoria f74f6efb1a [stable-only] Update .gitreview for stable/victoria Change-Id: I5f912dd0b2ea5e45ea30a981ee86d9a6ca785671
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.