ac195abccb
Train branch is in Extended Maintenance now[1]. Tempest and tempest plugins are branchless which means master version of Tempest and its plugins is used to test the supported stable branches. Once any stable branch is moved to EM state then, Tempest and its plugins compatible tag[2] needs to be released so that we can keep testing the EM stable branches with that tag once master Tempest and its plugins are not compatible[3]. Tagging 'train-last'[4] as well as a new version also with same hash. [1] https://releases.openstack.org/train/index.html [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 [4] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance Change-Id: Ib0de1dfb95a29264828c8315e1b6eb212eb8db9d
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.