[kolla] 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: I574f83af80fe4d6bd3166caa8936b4836f6a8370
This commit is contained in:
Tony Breeds 2019-04-16 15:53:19 +10:00
parent 53ef2cab30
commit 447f4933b3
2 changed files with 8 additions and 0 deletions

View File

@ -52,6 +52,10 @@ releases:
- hash: 858790a358d052344536395bec18571e7dcd9a23
repo: openstack/kolla-ansible
version: 5.0.6
- projects:
- hash: 858790a358d052344536395bec18571e7dcd9a23
repo: openstack/kolla-ansible
version: pike-em
release-notes: https://docs.openstack.org/releasenotes/kolla-ansible/pike.html
repository-settings:
openstack/kolla-ansible: {}

View File

@ -48,6 +48,10 @@ releases:
projects:
- repo: openstack/kolla
hash: 35aa36054231c14968ebe4c7a521fa33de27ead8
- projects:
- hash: 35aa36054231c14968ebe4c7a521fa33de27ead8
repo: openstack/kolla
version: pike-em
release-notes: https://docs.openstack.org/releasenotes/kolla/pike.html
repository-settings:
openstack/kolla: {}