Commit Graph

9 Commits

Author SHA1 Message Date
Elod Illes 924fd19fbe [congress] Transition Pike to End of Life
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: I29a4addb54778340a092b9ee713b75778f1695ac
2022-07-29 17:54:19 +02:00
Sean McGinnis 1704aa624a
Raise YAML compliance to 1.2
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>
2019-07-31 09:34:38 -05:00
Tony Breeds 9d4df9fab1 [congress] 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: Iea97c3534df7d73d2666c4765dfc50eb4c99f306
2019-04-19 00:36:14 +00:00
Tony Breeds 4c5b3ac22a [congress] final releases for pike
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: Idaf4a92fb17162c75006fec19385d9985fea5126
2019-04-16 15:53:11 +10:00
Doug Hellmann 99b201ac88 add repo names to repository-settings for pike
Change-Id: I438a18e94b0de492d92587bca76ca0900c5534dc
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-02-07 18:21:37 -05:00
Doug Hellmann dfdb54e10b create stable/pike branches for all of our libraries
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>
2017-07-28 16:02:51 -04:00
Eric Kao 7a8694b46d request congess client release
Change-Id: Icab0af7de6bc05773e70e7a793ab6c1dbe9150a6
2017-07-26 11:43:07 -07:00
Eric Kao 64814d8bef request congress client release
Change-Id: Ie624a0e618f9e461952e0d4def0897b10b279b4a
2017-06-09 13:15:38 -07:00
Doug Hellmann 8d5d768876 create stub files for pike deliverables
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>
2017-02-22 08:54:18 -05:00