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: Ia12fbe9479a7f2556f0d1e58868643acf84748b7
This is a procedural review to tag a final release for each
deliverables.
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.
Depends-On: https://review.opendev.org/#/c/658877/
Change-Id: I9216306aef6974b9275efeebf32c31631ffa63a6
After this release no new references to Mitaka will be added to
tripleo-quickstart, and old ones can be removed.
Change-Id: If87ca67c776f34c2369747b5bddf9446b5544bee
We no longer use the send-announcements-to field for anything.
Change-Id: Iec0b11ced00ea06ac459ad544b1cb2db20d2892d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Create the deliverable files for Pike based on the ones that were
released during Ocata. Leave out release and branch information, since
that will be filled in for the first release.
Change-Id: Idf3e9a3eadba86038f6b69527a109a0cad79bf8c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Tony Breeds