6efa9b911d
Since tricircle was only released once last cycle (and the cycle before) AND it has not yet been released this cycle yet either, we propose to change it to the cycle-with-rc model which is better for deliverables that do a single release per cycle. There are three options for responding: 1) If you know you will only do one release this cycle, +1. 2) If you know you will do more than one, please release now and -1 this change. 3) If you have no idea when you will release, please please please propose one BEFORE rc1 and -1 this change. Change-Id: I8b822f2b9c173fd72bc6015f69a3703a963f1c4c |
||
|---|---|---|
| data | ||
| deliverables | ||
| doc | ||
| openstack_releases | ||
| templates | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| watched_queries.yml | ||
| yamllint.yml | ||
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.