9b01867153
Ussuri and Victoria branches are in Extended Maintenance[1]. Once any stable branch is moved to EM state then, Tempest and its plugins needs to be released[2] so that we have the compatible tags to test the EM stable branches[3]. We taged ussuri-last & victoria-last for tempest[4] but forgot to do it for the tempest plugins. Using 1.6.0 tag which is what is used for neutron ussuir and victoria testing. -3ff8300038/zuul.d/ussuri_jobs.yaml (L9)-3ff8300038/zuul.d/victoria_jobs.yaml (L8)[1] https://docs.openstack.org/tempest/latest/stable_branch_support_policy.html [2] https://docs.openstack.org/tempest/latest/tempest_and_plugins_compatible_version_policy.html [3] https://review.opendev.org/c/openstack/releases/+/843039 Change-Id: Ie7f0b626d8d4a23490a2b244d7c5ba5d5b3bdca4
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.