7931c2ddaa
This release picks up new commits to blazar since the last release from stable/ussuri. This is being proposed as a convenience to help make sure stable changes are being released. If the team is good with this going out, please respond with a +1 to let the release team know it is OK to proceed. If it is not wanted at this time, or if there are more changes that would be good to get merged before doing a stable release, please leave a -1 with a comment with what the team would prefer. We can then either abandon this patch, or wait for an update with a new commit hash to use instead. $ git log --oneline --no-merges 5.0.0..aea56f5 aea56f5 docs: Update Freenode to OFTC 0d71758 Fix use of legacy Alembic API 6922665 Remove lower-constraints job on stable branches 9c5a583 Avoid double slash in Keystone auth_url cedf5fb Use the native Zuul v3 jobs from blazar-tempest-plugin fd652cb Fix up adding availability zone (AZ) to a host on creation 1eea940 Update TOX_CONSTRAINTS_FILE for stable/ussuri fd4b1e8 Update .gitreview for stable/ussuri Signed-off-by: Elod Illes <elod.illes@est.tech> Change-Id: Ib7464bacf664224caf45a57bbc370e6259ad79fa
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.