bd929b45b1
This creates the stable/yoga branch for all client and non-client libraries now that we are past the lib freeze on February 24th. If the team wants to wait for a specific patch to make it to the library, someone from the team can -1 the patch to have it held, or update that patch with a different commit SHA. Patches with no response will be merged by Friday, March 4th. Change-Id: Ie7057c50cee9092181eb6bb9ea8d7e2414ec53db |
||
---|---|---|
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 OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.