Release requests and history tracking
Go to file
Gregory Thiemonge e68465a4a5 Release octavia 7.1.2 for victoria
Included commits:
de20868a Fix LB set in ERROR too early in MapLoadbalancerToAmphora
17f2c674 Fix LB set in ERROR too early in the revert flow
e3026d35 Fix failover of az-specific loadbalancers
4703bebd Fix management network selection when calculating deltas
061ca287 Fix using host_routes in VIP subnet with amphorav2
c0ad3b34 Disable conntrack for TCP flows in the amphora
f7dde919 Fix duplicate SG creation for listener peer port
b94493eb Fix MAX_TIMEOUT value for listener
80ff90e3 Fix periodic image builder jobs
bf012c2c Fix PlugVIPAmphora revert function in amphorav2
c177987f Update nr_open limit value in the amphora
18413fab Add caps for pip-extra-reqs/pip-missing-reqs
739be788 Fix race conditions between API and worker DB calls
74c0ff2a Enable lo interface in the amphora-haproxy netns
ee7b2621 Add amphora_id in store params for failover_amphora
d69d0666 Fix comment for the ca_certificates_file opt
37b15da4 Optimize CountPoolChildrenForQuota task in amphorav2
bbb203a2 Fix task_flow.max_workers with persistence in amphorav2
2195a45a Fix rsyslog configuration when disabling logs
93ec146a Fix jobboard_enabled setting in devstack
5d49484e Fix devstack cleanup when using amphorav2
a139d2f9 Fix using subnets with host_routes in amphorav2 driver
582b4bab Make /healthcheck cache results
7ab43edc Cap hacking
1cb53e14 Fix empty Batch Member Update to unlock objects
c7640b90 Fix weighted round-robin about UDP listener
e3b68219 Fix LB failover for amphorav2: set security group
8b210bb5 Fix incorrect ERROR status with IPv6 UDP members
0a8254e0 Fix provider driver quota handling

Change-Id: Ifaeac58b3f2a37fd0647e4f98868166ca1f9d599
2022-01-11 09:18:28 +01:00
data Update EM transition date of Victoria and Xena 2021-10-08 18:19:55 +02:00
deliverables Release octavia 7.1.2 for victoria 2022-01-11 09:18:28 +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.