961f3a99ad
This release picks up new commits to blazar since the last release from stable/wallaby. 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 7.0.0..60622bc cba58e0 Fix references to start and end dates 61daf2d Fix list_allocations for multi-host reservations 6549ab0 Handle AggregateNotFound when deleting aggregate dd844f0 Fix lease update when resource_type parameter is missing 80a7539 Use built-in oslo context de/serialization 7a0fef2 Update Nova scheduler filter configuration 23c7ed9 Skip blazar install in docs and pep8 jobs 5b6c51d Switch to stestr da70772 Remove six again 43587aa docs: Update Freenode to OFTC d3737b5 Update TOX_CONSTRAINTS_FILE for stable/wallaby dbdb059 Update .gitreview for stable/wallaby Signed-off-by: Elod Illes <elod.illes@est.tech> Change-Id: I594705baa9e8318565e1bb402fcd2ce45537c85d
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.