[octavia] create pike-em tag against final releases

This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag

It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.

If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.

Change-Id: Ifc2212664deb968906423fe7d289a109e4375afa
This commit is contained in:
Tony Breeds 2019-04-16 15:53:19 +10:00
parent c2b3044800
commit 375a238744
4 changed files with 16 additions and 0 deletions

View File

@ -39,6 +39,10 @@ releases:
- hash: cea4e2c5904e3b2e32070afcec37db1f36668a67
repo: openstack/neutron-lbaas-dashboard
version: 3.0.3
- projects:
- hash: cea4e2c5904e3b2e32070afcec37db1f36668a67
repo: openstack/neutron-lbaas-dashboard
version: pike-em
branches:
- location: 3.0.0.0rc1
name: stable/pike

View File

@ -43,6 +43,10 @@ releases:
- hash: ecd495b7bfabcfe30f0b17a2510ac91b1d60b7b7
repo: openstack/neutron-lbaas
version: 11.0.4
- projects:
- hash: ecd495b7bfabcfe30f0b17a2510ac91b1d60b7b7
repo: openstack/neutron-lbaas
version: pike-em
branches:
- location: 11.0.0.0rc1
name: stable/pike

View File

@ -51,6 +51,10 @@ releases:
- hash: d8707f9a74636995edb3eb9a5db3ce4adc265af9
repo: openstack/octavia
version: 1.0.5
- projects:
- hash: d8707f9a74636995edb3eb9a5db3ce4adc265af9
repo: openstack/octavia
version: pike-em
branches:
- location: 1.0.0.0rc1
name: stable/pike

View File

@ -25,6 +25,10 @@ releases:
- hash: 2b532d92be3dd0631283ebc6f3b7b401d0c557ca
repo: openstack/python-octaviaclient
version: 1.2.1
- projects:
- hash: 2b532d92be3dd0631283ebc6f3b7b401d0c557ca
repo: openstack/python-octaviaclient
version: pike-em
branches:
- name: stable/pike
location: 1.1.0