Release requests and history tracking
Go to file
Pierre Riteau bec5547635 Final Victoria release for blazar
Change-Id: I60c9e65d96bf703d04949796b9efa530ca7d9c9e
2022-04-25 14:06:24 +02:00
data Merge "Sync mistral team release liaisons" 2022-04-11 12:52:35 +00:00
deliverables Final Victoria release for blazar 2022-04-25 14:06:24 +02:00
doc [manila][zed] Add project tracking schedule 2022-04-21 20:21:58 +05:30
openstack_releases Remove six 2022-04-19 10:19:15 +08:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Remove tag argument usage from helper scripts 2022-03-16 20:27:22 +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 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 Move release team ladder & infra into proper page 2021-07-22 15:31:25 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst moving to OFTC 2021-05-27 13:53:16 +02:00
requirements.txt Remove stable:follows-policy tag banner 2022-03-16 20:30:07 +01:00
setup.cfg List cycle's releases with process_auto_release 2021-09-17 11:56:37 +02: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 Pin setuptools for Yoga release 2022-03-28 15:36:29 +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 OFTC IRC <https://www.oftc.net/>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.