Release requests and history tracking
Go to file
Hervé Beraud 60f7b61406 fix nits
Change-Id: I7e543ad3265f81f51bd7edbcd1e780991b849c98
2021-03-05 17:32:09 +01:00
data Proposed release schedule for Xena (25w) 2021-01-29 07:01:24 -06:00
deliverables Merge "Release final os-vif for Wallaby" 2021-03-05 09:47:49 +00:00
doc fix nits 2021-03-05 17:32:09 +01:00
openstack_releases fix nits 2021-03-05 17:32:09 +01:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Merge "Adding a tool to catch projects that missed branching" 2021-03-05 14:20:39 +00:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:37:48 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml Switch to victoria job template 2020-06-02 14:28:30 -05:00
bindep.txt Cleanup bindep packages 2020-04-11 15:57:21 -05:00
CONTRIBUTING.rst Document tag pipeline jobs in contributor doc 2019-06-06 12:10:45 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst Update README.rst for better looks 2019-11-13 16:51:02 +01:00
requirements.txt add reno semver-next to the list-changes output 2020-09-03 08:34:49 -04:00
setup.cfg Adding a tool to catch projects that missed branching 2021-03-03 13:51:12 +01:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
tox.ini Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
watched_queries.yml Rename review.openstack.org to review.opendev.org 2019-05-12 04:33:25 +08:00
yamllint.yml add linter rules for vertical whitespace 2017-07-31 17:26:33 -04:00

OpenStack Releases

image

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.