Release requests and history tracking
Go to file
Maysa Macedo c73283db04 Propose to EOL Kuryr stable branches
The are multiple stable branches in all Kuryr
related projects that didn't receive any backports
for a while. This patch proposes to create eol tags
for all Kuryr projects for the branches pike, queens,
rocky and stein.

Change-Id: I91924fab713ecb7c082b7cdb14318200ffe37ec2
2021-12-02 11:08:30 +00:00
data Update EM transition date of Victoria and Xena 2021-10-08 18:19:55 +02:00
deliverables Propose to EOL Kuryr stable branches 2021-12-02 11:08:30 +00:00
doc Update Yoga Cycle key with my signature 2021-10-28 19:52:56 +00:00
openstack_releases Merge "List cycle's releases with process_auto_release" 2021-11-12 15:18:45 +00:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Merge "List cycle's releases with process_auto_release" 2021-11-12 15:18:45 +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
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
bindep.txt Cleanup bindep packages 2020-04-11 15:57:21 -05:00
requirements.txt Stop depending on git version of governance 2021-11-25 15:08:00 +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 Fix gate 2021-09-17 11:19:46 +00: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

README.rst

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.