324ceffbdb
This is the Wallaby milestone-2 release for python-cyborgclient. Clients and libraries following the cycle-with-intermediary release model are encouraged to release each milestone to make sure updates are made available. If you are happy with the current release hash, please +1 this patch and we will process a release. If you need to get some important changes merged first, leave a -1 and update the patch with a new commit hash to use once it is ready. If a release is definitely not wanted at this time, please -1 and leave a comment explaining that and we can abandon the patch. Any patches with no response will be assumed to be OK and will be processed by January 21. Signed-off-by: Hervé Beraud <hberaud@redhat.com> Change-Id: Ibc97661927fefc0deab2c4a7b2739493051b92d7 |
||
---|---|---|
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.