aaae4f42c4
Updates puppet-manila for last three stable branches Depends-On: I18c4a2f02179554aa5240ef5e5e6d4b3c3c26e57 Depends-On: I311c9f437b796b6cb11d8346af5d0e1d06ecb5a4 Depends-On: I52117cda4bb5d816371f6e083e6d4a0af3e8a4ee Change-Id: I358ac7b17a456e0f56142286be48b7bd61b3fc82 |
||
---|---|---|
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.