openstack/releases
Code Issues Proposed changes
Release requests and history tracking
21,966 Commits 1 Branch 0 Tags 129 MiB
Python 89.7%
Shell 10.3%
cf9961d73e
Go to file
Ghanshyam Mann cf9961d73e [magnum-tempest-plugin] Tag wallaby-last 
Wallaby 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 'wallaby-last' as well as a new version also with same hash.

[1] https://releases.openstack.org/wallaby/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

Change-Id: I7b0aac783ef0b6e08a22d34a99b89bc0b82d9ab6
2022-12-25 23:00:16 -06:00
data Add SLURP mark for Releases page template 2022-12-02 11:46:43 +01:00
deliverables [magnum-tempest-plugin] Tag wallaby-last 2022-12-25 23:00:16 -06:00
doc Add Election details to the schedule/ICS 2022-12-07 19:20:31 +11:00
openstack_releases Merge "Fix stable branch naming validation" 2022-12-02 14:37:04 +00:00
templates
tools Remove tag argument usage from helper scripts 2022-03-16 20:27:22 +01:00
.gitignore
.gitreview
.stestr.conf
.zuul.yaml Uncap jsonschema 2022-07-26 12:24:11 +02:00
bindep.txt
CONTRIBUTING.rst Move release team ladder & infra into proper page 2021-07-22 15:31:25 +02:00
LICENSE
README.rst moving to OFTC 2021-05-27 13:53:16 +02:00
requirements.txt Uncap jsonschema 2022-07-26 12:24:11 +02:00
setup.cfg Update python testing as per zed cycle testing runtime 2022-05-13 17:33:21 +08:00
setup.py
test-requirements.txt
tox.ini Pin setuptools for Yoga release 2022-03-28 15:36:29 +02:00
watched_queries.yml
yamllint.yml

README.rst

OpenStack Releases

image

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.