Release requests and history tracking
Go to file
Eyal b3d35ceb08 Bump vitrage-dashboard version to 3.1.0
Change-Id: I5c47e3f26b58e907ad84dcee0cb2628d5ab8c052
2020-04-24 15:44:26 +03:00
data Merge "Set Rocky status to Extended Maintenance" 2020-04-02 18:05:53 +00:00
deliverables Bump vitrage-dashboard version to 3.1.0 2020-04-24 15:44:26 +03:00
doc Merge "Add details to unreleased lib check" 2020-04-16 09:06:37 +00:00
openstack_releases Update docs building, Python 3 cleanup 2020-04-20 11:16:46 +02:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools trivial - fix nits in script 2020-02-20 17:40:09 +01: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 Update docs publishing job 2020-02-20 18:01:34 +01: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 Unpin keyring to unbork twine validate check 2019-11-19 10:11:52 +01:00
setup.cfg Update docs building, Python 3 cleanup 2020-04-20 11:16:46 +02:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Update docs building, Python 3 cleanup 2020-04-20 11:16:46 +02:00
tox.ini Update docs building, Python 3 cleanup 2020-04-20 11:16:46 +02: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.