openstack/releases
Code Issues Proposed changes
Release requests and history tracking
21,694 Commits 1 Branch 0 Tags 129 MiB
Python 89.1%
Shell 10.9%
c01e19ca96
Go to file
Zuul c01e19ca96 Merge "[octavia] Transition Wallaby to EM"
2022-11-07 14:09:42 +00:00
data Remove or replace non-existent email addresses 2022-10-17 13:50:57 +02:00
deliverables Merge "[octavia] Transition Wallaby to EM" 2022-11-07 14:09:42 +00:00
doc Fix scheduled dates to Thursdays where needed 2022-10-17 16:35:26 +02:00
openstack_releases Merge "Fix base query for empty diff" 2022-10-17 11:26:02 +00: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 Uncap jsonschema 2022-07-26 12:24:11 +02: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 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 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

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.