Release requests and history tracking
Go to file
Jeremy Stanley 1e89cf59ac Publish the 2024.1/Caracal key for future use
This adds a listing for the 2024.1/Caracal Cycle key fingerprint
with Monday 2023-10-09 (the week after the 2023.2/Bobcat release) as
its start date, and links to an export of the corresponding public
key with initial attestation signature from the 2023.2/Bobcat Cycle
key as well as the change author.

Change-Id: Ia80b2e739959b96fe26214868178727bf1883988
2023-09-29 14:15:13 +00:00
data Merge "Add SLURP marker to Caracal" 2023-09-28 10:15:43 +00:00
deliverables Merge "Final RC patch for skyline-console" 2023-09-29 13:00:36 +00:00
doc Publish the 2024.1/Caracal key for future use 2023-09-29 14:15:13 +00:00
openstack_releases Merge "Fix release id fetch for validate_series_open" 2023-09-20 09:02:14 +00:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Update list_weeks to use the release yamlutils 2023-07-04 21:24:28 +10:00
.gitignore
.gitreview OpenDev Migration Patch 2019-04-19 19:37:48 +00:00
.stestr.conf
.zuul.yaml Use the new openstack-python3-jobs template 2023-03-23 16:49:09 +01:00
CONTRIBUTING.rst Move release team ladder & infra into proper page 2021-07-22 15:31:25 +02:00
LICENSE
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
setup.py
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

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.