afc751b011
As discussed in the mail thread [1][2], this patch transition the Rocky branch to End of Life. The last patch of the branch will be tagged with rocky-eol tag. stable/rocky branch cannot be used anymore and will be deleted if this patch merges. This is needed as stable/rocky is not actively maintained in recent period, thus gates are mostly broken due to job failures. Besides, by removing these branches, infra resources will be freed up, too. Please try to identify any zuul job, that is defined outside of the repositories in this patch (for example in openstack-zuul-jobs, etc.) and won't be used anymore if stable/rocky is deleted. Propose a job removal patch for them. Please +1 if the team is ready for us to proceed with this transition, or -1 if there are still some activity on the branch and the team wants to continue to maintain it. [1] https://lists.openstack.org/pipermail/openstack-discuss/2023-January/031922.html [2] https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033386.html Change-Id: I6f6bdc2336f8e951318acaedf6b1417f6aaf4271 |
||
|---|---|---|
| data | ||
| deliverables | ||
| doc | ||
| openstack_releases | ||
| templates | ||
| tools | ||
| .gitignore | ||
| .gitreview | ||
| .stestr.conf | ||
| .zuul.yaml | ||
| bindep.txt | ||
| CONTRIBUTING.rst | ||
| LICENSE | ||
| README.rst | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
| test-requirements.txt | ||
| tox.ini | ||
| watched_queries.yml | ||
| yamllint.yml | ||
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.