af26e0d9dd
Patrole is branchless with "cycle-with-intermediary" model and does not create the stable branch with same reason as Tempest. Below commit added the stable/stein for Patrole which is not correct- https://review.opendev.org/#/c/650173 This commit removes the branching from stein patrole release. As next step, we will add some type(as proposed by ttx[1]) or tag to make it clear that Patrole does not need branch. [1] https://review.opendev.org/#/c/670808/ Change-Id: Ib11838bc87e4fe0a350d107184be68e837233891 |
||
|---|---|---|
| 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.