Release requests and history tracking
Go to file
Elod Illes 70fac38b44 Release heat for stable/victoria
This release picks up new commits to heat since
the last release from stable/victoria.

This is being proposed as a convenience to help make sure stable
changes are being released. If the team is good with this going out,
please respond with a +1 to let the release team know it is OK to
proceed.

If it is not wanted at this time, or if there are more changes that
would be good to get merged before doing a stable release, please
leave a -1 with a comment with what the team would prefer. We can
then either abandon this patch, or wait for an update with a new
commit hash to use instead.

$ git log --oneline --no-merges 15.0.0..cbe9be5e7
cbe9be5e7 Provide install_command to pip install with upper-constraints
c062de4f2 Fallback to upstream for Fedora image
f52feef69 Revert "Make grenade job voting again"
7ef31c2be Make grenade job voting again
86354c2d7 Don't create deployment when changing transport
40a3494c8 Update get_hosts to use available API
c881da8b8 Use Block Storage API v3 instead of API v2
98fade887 Detect EL8 platform-python
0833daa3f Preserve order in list_concat_unique
652f872e4 Resume testing grenade jobs in Victoria
59328b254 Assume interface detach called for port not found
8bdf6b984 Don't update status for replaced resource
546bc2391 Net attr: Sort segments without name attribute first
d8027e65c Fix args for initializing trove client
915da60e8 Fix multiple gate issues
7e03502a6 Align lower-constraints for new pip
779b39c97 Replace Fedora test image with F32
3cf3a68a4 Add SOURCE_IP_PORT to LB_ALGORITHM allowed values
996884da6 Delete the default value of domain in role creation
3f98fd9b1 As of nova microversion 2.57, personality is deprecated
e30ea0af5 Configure swap as before
5f1ab43bb Update TOX_CONSTRAINTS_FILE for stable/victoria
dc6602079 Update .gitreview for stable/victoria

Signed-off-by: Elod Illes <elod.illes@est.tech>
Change-Id: I0070cff25fd6f77ea488dc5837e2d769cb03618e
2022-02-03 12:59:00 +01:00
data Set Ussuri status to Extended Maintenance 2021-12-03 16:47:03 +01:00
deliverables Release heat for stable/victoria 2022-02-03 12:59:00 +01:00
doc Update Yoga Cycle key with my signature 2021-10-28 19:52:56 +00:00
openstack_releases Fix validation when tags are missing and a branch is requested 2021-12-02 09:46:12 +01:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Merge "List cycle's releases with process_auto_release" 2021-11-12 15:18:45 +00:00
.gitignore Switch to stestr 2018-07-10 10:38:33 +07:00
.gitreview OpenDev Migration Patch 2019-04-19 19:37:48 +00:00
.stestr.conf Switch to stestr 2018-07-10 10:38:33 +07:00
.zuul.yaml Switch to victoria job template 2020-06-02 14:28:30 -05:00
bindep.txt Cleanup bindep packages 2020-04-11 15:57:21 -05:00
CONTRIBUTING.rst Move release team ladder & infra into proper page 2021-07-22 15:31:25 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst moving to OFTC 2021-05-27 13:53:16 +02:00
requirements.txt Stop depending on git version of governance 2021-11-25 15:08:00 +01:00
setup.cfg List cycle's releases with process_auto_release 2021-09-17 11:56:37 +02:00
setup.py [Trivial] Remove executable privilege of setup.py 2016-05-09 16:38:37 +00:00
test-requirements.txt Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05:00
tox.ini Fix gate 2021-09-17 11:19:46 +00:00
watched_queries.yml Rename review.openstack.org to review.opendev.org 2019-05-12 04:33:25 +08:00
yamllint.yml add linter rules for vertical whitespace 2017-07-31 17:26:33 -04:00

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.