openstack/releases
Code Issues Proposed changes
Release requests and history tracking
21,842 Commits 1 Branch 0 Tags 130 MiB
Python 89.1%
Shell 10.9%
ebd743ed71
Go to file
Douglas Mendizábal ebd743ed71 [barbican] Transition Queens, Rocky & Stein to EOL 
The barbican team is no longer maintaing branches older than Train.

Change-Id: I30631c82945715f08dc6f59e282f96676d36e5e7
2022-12-01 09:33:07 +01:00
data Merge "Set Wallaby status to Extended Maintenance" 2022-11-25 16:36:15 +00:00
deliverables [barbican] Transition Queens, Rocky & Stein to EOL 2022-12-01 09:33:07 +01:00
doc Add cinder specific dates for 2023.1 Antelope Schedule 2022-11-03 09:45:22 +00:00
openstack_releases Update _CLOSED_SERIES set with Wallaby 2022-10-21 20:01:34 +02:00
templates
tools Remove tag argument usage from helper scripts 2022-03-16 20:27:22 +01:00
.gitignore
.gitreview
.stestr.conf
.zuul.yaml Uncap jsonschema 2022-07-26 12:24:11 +02:00
bindep.txt
CONTRIBUTING.rst
LICENSE
README.rst
requirements.txt Uncap jsonschema 2022-07-26 12:24:11 +02:00
setup.cfg Update python testing as per zed cycle testing runtime 2022-05-13 17:33:21 +08:00
setup.py
test-requirements.txt
tox.ini Pin setuptools for Yoga release 2022-03-28 15:36:29 +02:00
watched_queries.yml
yamllint.yml

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.