5ecb80c82e
As discussed on the ML many oslo projects are now stable enough to be adopt the independent release model. It will help us o reduce the amount of efforts needed to backport fixes to stable branches. oslo.upgradecheck, tooz, stevedore, and osprofiler are finally ignored as they needs some releases for Wallaby. They was originally planed to be transitioned too. http://lists.openstack.org/pipermail/openstack-discuss/2020-November/018905.html Change-Id: I6ac8b52349d631171647c89c8ef18cd6a9b16808
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.