e9adf7cb50
TripleO is not going to make a stable/yoga for its repos so as we did for X [1] lets tag current master as 'Y' release. RDO will use this for the Yoga RDO release. The tag is on commits from the last master centos9 rdo promotion (current-tripleo) [2], except puppet-tripleo and puppet-pacemaker where we are tagging the relevant commits from [3] and [4] from the needed metadata bump. Relevant mailing list thread @ [5]. [1] https://review.opendev.org/c/openstack/releases/+/813852 [2] https://trunk.rdoproject.org/centos9-master/current-tripleo/7c/35/7c3595fcdce0ec20189de8d5b99dec16/versions.csv [3] https://review.opendev.org/c/openstack/puppet-tripleo/+/836617 [4] https://review.opendev.org/c/openstack/puppet-pacemaker/+/836767 [5] http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028029.html Change-Id: I8f55b4f4011ee351b0f2eedff8e5d484a9592182
OpenStack Releases
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.