477d64b8f1
Some deliverables never released the patches related to the `TOX_CONSTRAINTS_FILE` switch for Wallaby. Not landing this switch downstream (to distros) became problematic as tox target executed downstream refered to master's requirements constraints and so validations started to fail with downstream usage of Wallaby (OSP17 by example). So even if deliverables does not provides functional changes I prefer release them as a bugfix version to fix this kind of problems for distros. NOTE: oslo.cache is already at the version 2.8.0 on Xena so I can't release a minor version even if functional changes are landed. Change-Id: I920ee7bcca3cbf3e4051b3a3098beed53b1c969d
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.