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: I8b58a6feac1a2d17a3ab6ac1d3daf7e6f25c1c3c
This is a procedural review to tag a final release for each deliverables ; and
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: Ic0f41662bb9c891c9dd468ac4ea36248301c8d19
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>