e24c1dd735
2023.1 branch is moving to unmaintained state now[1]. Tempest and tempest plugins are branchless which means master version of Tempest and its plugins are not guaranteed to support unmaintained branched. To continue testing the unmaintained branches, Tempest and its plugins compatible tag[2][3] needs to be released for their testing. Tagging '2023.1-last' with the latest hash used in the 0.17.0 version. [1] https://review.opendev.org/q/topic:%22zed-unmaintained%22 [2] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html [3] https://docs.openstack.org/tempest/latest/tempest_and_plugins_compatible_version_policy.html Change-Id: I4cef08c6225d994eb90ea0770face57498d22a9c
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.