aba3d8adbd
This branch reached the end of its official stable maintained period, hence this patch transition stable/zed branch to Unmaintained. (For details about Unmaintained state please see: [1][2]) The transitions is as follows: - tip of the stable/zed branch is tagged with zed-eom tag - unmaintained/zed branch will be cut from zed-eom tag - stable/zed branch will be deleted Note: - there will no longer be official releases off of zed branch after this transition - backports can be pushed to unmaintained/yoga branch - openstack-unmaintained-core (or <project>-unmaintained-core groups if such exists) have the rights to merge patches Important: please +1 if the team is ready for us to proceed with this transition, or -1 if there are any final Zed stable release with backports currently in flight that we should wait for. For the latter case, please propose a final Zed stable release patch, and rebase this patch on top of that, with the latest commit hash of stable/zed. The transition deadline is May 2nd, 2024. [3] [1] https://docs.openstack.org/project-team-guide/stable-branches.html#unmaintained [2] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branches.html [3] https://releases.openstack.org Change-Id: I967bce9be73e0320b2ec1b4b840c969a549c41c7 |
||
|---|---|---|
| data | ||
| deliverables | ||
| doc | ||
| openstack_releases | ||
| playbooks | ||
| 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.