Goutham Pacha Ravi
3af5dd9560
Manila's maintainers would like to create the eol release tag with the latest code from these branches on the manila repository and delete these release branches from git once these tags have been created. See the discussion on the OpenStack Mailing list [1] for the announcement. [1] http://lists.openstack.org/pipermail/openstack-discuss/2021-July/023702.html Change-Id: I98b368c03a864943ae82b416f90def7b91316e59
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.