
This picks up a number of features: Idac1b8f4610825ca7fdf62eec4f0453398e43346 Add application credential CRUD support Iac034b7d8afe22a57de9f1fa9b37f3b2bf5fa0da Add support for Node tainted field I860cf08712bd5869f448eaab06eb6a637e0708fd Add clustering update_action I6417735b0fb784d500f9d33adca4fcd92cdf7966 Add router add/remove route operations ...and at least a couple of bug fixes: I6f628787dcf458ff9149dbb3502e7beeded70d9e baremetal node: 'error' is a failed state Ie0cffc402747d070c1eae1d9b423a046936d917d Keep connection backrefs with weakref.proxy Change-Id: I9bd287974c52fd32102fd1c1c62f662f478f0d11
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.