bcc551f0f3
This picks up unreleased changes in osc-lib. The cycle-with-intermediary deliverables are good to release frequently whenever there are functional changes to be released. Feel free to -1 this patch if there are additional changes that should be included in this release or if it is not a good time to do it. Change-Id: I639aa13d9de4f0fd7b1023dc860934fb3429ad13 Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com> |
||
---|---|---|
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 |
OpenStack Releases
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.
More information
You can reach the Release Management team on the #openstack-release channel on Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.