openstack
/
releases
Code Issues Proposed changes

[kuryr] 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: Ib9f68ea30977ba5c9129e6aa08b5d1fb18ec1f85
This commit is contained in:
Tony Breeds 2019-04-16 15:53:18 +10:00
parent b3fd83441e
commit f7dbffd2f8
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
deliverables/pike/kuryr-kubernetes.yaml
View File

@ -19,5 +19,9 @@ releases:
- hash: a6e2009589beb73673a1d9d7ecfa8a246c613911
repo: openstack/kuryr-kubernetes
version: 0.2.1
- projects:
- hash: a6e2009589beb73673a1d9d7ecfa8a246c613911
repo: openstack/kuryr-kubernetes
version: pike-em
repository-settings:
openstack/kuryr-kubernetes: {}