Since every project transitioned to End of Life already, requirements should have tagged with EOL, too. This patch tags latest patch on stable/ocata with ocata-eol and the branch can be deleted afterwards. Change-Id: I197457d2160a1668013854bd390779dc3c2c9002
|1 year ago|
|data||1 year ago|
|deliverables||1 year ago|
|doc||1 year ago|
|openstack_releases||1 year ago|
|templates||4 years ago|
|tools||1 year ago|
|.gitignore||5 years ago|
|.gitreview||4 years ago|
|.stestr.conf||5 years ago|
|.zuul.yaml||3 years ago|
|CONTRIBUTING.rst||2 years ago|
|LICENSE||5 years ago|
|README.rst||2 years ago|
|bindep.txt||3 years ago|
|requirements.txt||1 year ago|
|setup.cfg||2 years ago|
|setup.py||7 years ago|
|test-requirements.txt||3 years ago|
|tox.ini||1 year ago|
|watched_queries.yml||4 years ago|
|yamllint.yml||6 years ago|
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.
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.