Takashi Kajinami b4970b2a59 Puppet OpenStack: Transition wallaby to EOL
The wallaby branch of some modules were already transitioned to EOL.
Current puppet CI does not allow partial retirement and CI is broken
once any of the modules is retired.

Because we haven't seen any interest to maintain specific modules,
I'd propose retiring the wallaby branch completely.

Change-Id: I875a5c62803ea352048a1ce418ed5d3526b34bb9
2024-12-14 13:16:28 +09:00
2024-12-10 11:02:13 +01:00
2019-09-23 18:04:44 +02:00
2018-07-10 10:38:33 +07:00
2019-04-19 19:37:48 +00:00
2018-07-10 10:38:33 +07:00
2018-10-17 10:36:04 +11:00
2021-05-27 13:53:16 +02:00
2024-03-15 08:14:24 +01: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.

Description
Release requests and history tracking
Readme 131 MiB
Languages
Python 89.1%
Shell 10.9%