5801fbdc77
Currently constraint redirectiones that point to EOL releases don't work as expected due to gitea needed to differentiate between tags and branches. Rather than fix, and rely on multiple redirects lets just craft 301's that point to the correct gitea url. This means we now need to know when a target is a branch or tag but that's pretty simple to intuit given our deliverable structure. Change-Id: Ife030f8ee7b5d204b054f99e920a675f7d92da69
Using This Repository
All official OpenStack software should go through the 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).
This repository is used to track release requests. Releases are managed using groups of "deliverables", made up of individual project repositories sharing a Launchpad group and a version number history. Many deliverables will only have one constituent project repository.
The repository is managed by the Release Management team.
Refer to the reference documentation for more details
Deliverables managed by teams not under OpenStack governance should follow the tagging instructions in the infra manual.