b2e80725de
This release picks up new commits to ec2-api 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 12.0.0..0466881 0466881 Remove TripleO job 88f5a2b try to use neutron-vpnaas from plugin definition 76da371 remove lower-constraints job. it's buggy 7746b15 Run TripleO jobs on CentOS8 instead of CentOS7 5cfddf2 various fixes 67953e2 Update TOX_CONSTRAINTS_FILE for stable/wallaby 49ce2b3 Update .gitreview for stable/wallaby Signed-off-by: Elod Illes <elod.illes@est.tech> Change-Id: If274f149e139345c06d6140f08f57d307a1fbb59
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.