|Zuul a716920a4e Merge "TripleO train ml3 release"||3 hours ago|
|data||7 hours ago|
|deliverables||3 hours ago|
|doc||3 weeks ago|
|openstack_releases||1 week ago|
|templates||9 months ago|
|tools||2 months ago|
|.gitignore||1 year ago|
|.gitreview||5 months ago|
|.stestr.conf||1 year ago|
|.zuul.yaml||2 months ago|
|CONTRIBUTING.rst||3 months ago|
|LICENSE||11 months ago|
|README.rst||10 months ago|
|bindep.txt||1 year ago|
|requirements.txt||2 months ago|
|setup.cfg||1 month ago|
|setup.py||4 years ago|
|test-requirements.txt||1 year ago|
|tox.ini||1 month ago|
|watched_queries.yml||4 months ago|
|yamllint.yml||2 years ago|
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.