Release requests and history tracking
Go to file
Hervé Beraud 0ec9ceb019 Release neutron-tempest-plugin for wallaby
This is the automatic release for neutron-tempest-plugin.
Please +1 if this is ready to go, or -1 if the team needs a little more
time. If so, please update with the new commit hash to use when ready.

$ git log --oneline --no-merges 1.3.0..5ad4e82
11b6892 New test, extends test_subport_connectivity
862cbeb Set proper OVS_SYSCONFDIR for the job wher OVS is compiled
305ded3 Revert "Mark test_floatingip_port_details test as unstable"
08f3c61 ovn: Collect OVN logs
6b65967 Fix multicast scenario test
e6e0ccf Add a scenario test for remote address group
b1c7a3d Add tempest API tests for address groups RBAC
24ad1f3 Enable l3_ha in neutron config for scenario jobs
f5a40d9 Add update QoS rule test step to fip-qos scenario
9877291 Delete qos policies created during scenario tests
e6b1004 Add skip funtion for checking enabled extensions in the l3 agent
743c3b2 Explicitly set jobs to ML2/OVS
d89e7e3 Limit execution of the neutron CI jobs on some irrelevant file
83c8fd6 Move designate scenario job to the experimental queue temporary
b667ac3 Delete router test - API scenario
85472b6 test_metadata_routed: save console log
088707b Add first VLAN Transparency tests
363b13b Remove stein jobs from the project's queues
8ebc061 Create security groups with the same name
20a3211 Unmark port_forwarding tests as unstable (cont.)
2903040 Add doc/requirements
45d8761 Move fwaas jobs to the experimental queue
dd96e9a Use tempest's ServiceClients rather than Manager

Signed-off-by: Hervé Beraud <hberaud@redhat.com>
Change-Id: Idca4ca424ff91fa11dacbe6937915f36fc824e61
2021-03-26 17:07:48 +01:00
data Adding a new email for release liaison to hberaud 2021-03-09 08:58:06 +01:00
deliverables Release neutron-tempest-plugin for wallaby 2021-03-26 17:07:48 +01:00
doc Merge "Standardize topics to use during series" 2021-03-25 08:57:41 +00:00
openstack_releases Merge "fix nits" 2021-03-16 09:18:29 +00:00
templates Remove unused RC templates 2019-09-23 18:04:44 +02:00
tools Merge "Add delete option to list_eol_stale_branches.sh" 2021-03-08 11:25:40 +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 Document tag pipeline jobs in contributor doc 2019-06-06 12:10:45 +02:00
LICENSE Add top level LICENSE file 2018-10-17 10:36:04 +11:00
README.rst Update README.rst for better looks 2019-11-13 16:51:02 +01:00
requirements.txt add reno semver-next to the list-changes output 2020-09-03 08:34:49 -04:00
setup.cfg Adding a tool to catch projects that missed branching 2021-03-03 13:51:12 +01: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 Update to latest hacking for pep8 checks 2020-07-27 16:33:03 -05: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 Freenode IRC, or by sending an email with '[release]' as a subject prefix to the openstack-discuss mailing-list.