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: Id38ffe10afb38fcf0f6fe1de00014d5002280d85
There have been a good number of bug fixes that have come in
since we released /stable/pike 11.1.0. Doing a Pike
release now to roll up all the bug fixes.
Change-Id: I4ed9f24456149da5b537fda73f59b5a1fd59bee4
This is a mostly a bugfix release for stable/pike. It includes
a number of bug fixes that have been backported since
early December 2017. It is being incremented as a feature
release due to the threading changes made in the backup
service.
Change-Id: I3f7a6ac0727995c4b269b0aced7f38ec537288bd
The Pike release script had a typo that caused the release emails to
have incorrect diff output.
This patch causes the validate test to catch more typos for releases
and branches. It also fixes the typos in the existing deliverables
files so they will pass future validation.
Change-Id: If173ba0b3d8c427f0bf5f3e4972dd0848459c951
A number of changes have come into Cinder since we
cut RC1. The flow of changes has now slowed so we
think we are ready to cut RC2.
Change-Id: I33b5b35daff90570c49fb2a68cfe922fd67f45a9
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>
Brian Rosmaita