Release requests and history tracking
Go to file
Előd Illés 37a993c3cb Set Xena status to Extended Maintenance
Project's last releases in Xena have been tagged with xena-em.
Now indicate that Xena is in Extended Maintenance phase also at

Transition date is April 20th, 2023.

Change-Id: I346b0e1eaeda37381413da9abc11e2441f0fcce4
2023-04-21 19:36:07 +02:00
data Set Xena status to Extended Maintenance 2023-04-21 19:36:07 +02:00
deliverables Merge "[swift] Transition Xena to EM" 2023-04-21 13:37:33 +00:00
doc Merge "Add Oslo specific dates for Bobcat schedule" 2023-04-20 09:51:00 +00:00
openstack_releases Fix E275 error with latest flake8 2023-04-19 14:59:16 +02:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Add workaround for announce mail script 2023-03-30 19:25:00 +02: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 Uncap jsonschema 2022-07-26 12:24:11 +02: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 Uncap jsonschema 2022-07-26 12:24:11 +02:00
setup.cfg Remove virtualenv pinning 2023-03-23 20:08:34 +01:00 [Trivial] Remove executable privilege of 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 Remove virtualenv pinning 2023-03-23 20:08:34 +01:00
watched_queries.yml Rename to 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


This repository is used to drive release automation for OpenStack release deliverables, ultimately publishing them on the website.

Changes to this repository are proposed using Gerrit at 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 <>, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.