12203373fa
This release picks up new commits to metalsmith 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 1.4.3..1ba2507 8da3eff Do a precise node lookup for unprovision c62ee4e Add linters job 1ba2507 metalsmith_instances module, unprovision by hostname 5873507 metalsmith_instances module, pass hostname in reserve 66743a2 metalsmith list handle missing port e207b29 Add a workaround to fix the CI cc00215 Ensure tox.ini is ASCII ad2be35 Avoid non-Stream CentOS 8, it is EOL; make one job non-voting Signed-off-by: Elod Illes <elod.illes@est.tech> Change-Id: Iac2a18a15a0babad0cd0d62b1dca73d531c62a62
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.