Release requests and history tracking
Go to file
2024-09-06 13:59:30 +00:00
data Merge "Update 2023.1 Antelope Unmaintained transition date" 2024-08-05 10:48:21 +00:00
deliverables Merge "[swift] Create 2024.2 branch for client and non-client libs" 2024-09-06 13:59:30 +00:00
doc Proposed 2025.1 Epoxy release schedule 2024-07-26 09:57:33 +00:00
openstack_releases Mark 2024.1 Caracal as released 2024-04-02 12:47:59 +02:00
playbooks [CI] Return tox-validate job log as zuul artifact 2024-03-20 16:21:14 +01:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Sort output for tools/governance_consistency.py 2024-06-21 14:04:27 +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 Add irrelevant-files for openstack-tox-py312 2024-07-15 13:41:57 +02:00
bindep.txt Add libpcre3-dev to bindep 2024-08-21 15:26:10 -07: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 Update for Unmaintained transition 2024-03-15 08:14:24 +01:00
setup.cfg Update for Unmaintained transition 2024-03-15 08:14:24 +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 Remove virtualenv pinning 2023-03-23 20:08:34 +01: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.