[trove] 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: I40cdfc99882f9a35b61e70df3c3de120fc81ebab
This commit is contained in:
Tony Breeds 2019-04-16 15:53:18 +10:00 committed by Sean McGinnis
parent 3813b476ed
commit f908a184ce
No known key found for this signature in database
GPG Key ID: CE7EE4BFAF8D70C8
3 changed files with 12 additions and 0 deletions

View File

@ -25,6 +25,10 @@ releases:
- hash: b10b8170cd21f9fd40a4a85fc26075a2737fbe31
repo: openstack/python-troveclient
version: 2.12.1
- projects:
- hash: b10b8170cd21f9fd40a4a85fc26075a2737fbe31
repo: openstack/python-troveclient
version: pike-em
branches:
- name: stable/pike
location: 2.12.0

View File

@ -32,6 +32,10 @@ releases:
- hash: d198007df597604bfc14fd4a6862f4184661c540
repo: openstack/trove-dashboard
version: 9.0.1
- projects:
- hash: d198007df597604bfc14fd4a6862f4184661c540
repo: openstack/trove-dashboard
version: pike-em
release-notes: https://docs.openstack.org/releasenotes/trove-dashboard/pike.html
repository-settings:
openstack/trove-dashboard: {}

View File

@ -32,6 +32,10 @@ releases:
- hash: 7695661c2fd3be262f3879174fd3645106bfd3c7
repo: openstack/trove
version: 8.0.1
- projects:
- hash: 7695661c2fd3be262f3879174fd3645106bfd3c7
repo: openstack/trove
version: pike-em
release-notes: https://docs.openstack.org/releasenotes/trove/pike.html
repository-settings:
openstack/trove: {}