fde014c987
That was a constant paper cut for me: every time someone uses edit-deliverables it may result in release highlights being reformatted to create lines over 80 char. You can see that happening at: https://review.openstack.org/#/c/650911/1/deliverables/rocky/cloudkitty.yaml where it messes up perfectly-good yaml and turns it into 88-char-long lines. I experimented with various settings (you would think width=80 would do, but no). Forcing dump width at 66 characters seems to produce the desired results. Change-Id: I83934a0f7d6eeaec47b5dcb1a6bfb8c53ed65799 |
||
|---|---|---|
| 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.