This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: If71fbdd1cbc2d5c1d2a3d60d44cb69d70ddb6542
The YAML 1.2 spec was released in 2009. It's probably been enough time
that it's safe to move to it.
The only issue for out YAML usage was 1.2 dropped the use of Yes, No, On,
and Off as valid boolean values.
Change-Id: I608e09d219379e00cca15c5ff165bb63aecfe9f2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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: I1256efb1059029ae2e901a1d18ea445a91bd1a3a
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: Ifcb051db33bffbfe7c183b726e7c54c310c488e1
Following the release process[1], all projects that are publishing
release notes have the notes link included in their deliverable
file.
Extra changes (like true -> yes) are included due to the use of
edit-deliverables YAML linter.
Change-Id: Ibd63f0f8bf1d406039c0196560768beb9f6650ce
Except barbicanclient which is working on a critical fix and
neutronclient which had a late release request that we haven't
resolved.
Change-Id: Ib4866823c7f3477e09999106086a882d8f650b64
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This commit bump each library's minor version due to the final release
for Pike.
Note: this commit doesn't include releases for pylockfile and tooz
Change-Id: I8bea7bf3bea2f048a13ed1e714f87835dfbcb265
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>