84d18d5fce
As a courtesy for project teams, on RC1 week the release management team proposes a RC1 release for all cycle-with-rc deliverables, based on HEAD. That RC1 will double as the branch point for the stable/victoria branch for neutron-vpnaas-dashboard. Release liaison or PTL should +1 this proposal if they are happy with it, amend this proposal (for example with a more recent SHA) to match their needs, or -1 to block it until release-critical issues are all fixed. Change-Id: Icbda647e273044047b36af1131ece68c9dec026e Signed-off-by: Thierry Carrez <thierry@openstack.org> |
||
---|---|---|
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.