Commit Graph

15 Commits

Author SHA1 Message Date
Elod Illes 0657b029b4 [designate] 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: If585b0961569a1b8291070752049683deac7270c
2022-07-29 17:54:17 +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 079f9315d2 [designate] 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: I2510245f91ed83b6ebfed6b9501c1d87426fc5a7
2019-04-16 15:53:18 +10:00
Tony Breeds bb2832ec53 [designate] 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: I018387a0dcf76ecebbc7e6497e24e01d6c86181d
2019-04-16 15:53:09 +10:00
Graham Hayes bd8e9b5fb9
Release Designate 5.0.2 (pike)
Change-Id: Idfe3fe090fa07e00b8bd1b88d88533af2f282718
Signed-off-by: Graham Hayes <graham@hayes.ie>
2018-05-31 15:27:42 -07: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
Sean McGinnis 3291999ef4 Add or update pike release notes links
Depends-on: https://review.openstack.org/540536
Change-Id: Ie42658df2aebd2563d693ff207abec5916cb1d52
2018-02-02 16:08:10 -06:00
Graham Hayes ec047c3791
Release Designate 5.0.1
Change-Id: I3307d1cb8bfb2390cb47b934546241aa3ab2e4d8
2017-10-24 19:02:28 +01:00
Michael Johnson b6f3045e5e Update schema.yaml to catch more typos
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
2017-09-01 11:11:04 -07:00
Doug Hellmann 245d1fa1a7 pike final releases for cycle-with-milestones projects
Change-Id: If0036bc7b600dbbda59151e00235fed07fa3fbff
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-08-28 12:00:47 -04:00
Graham Hayes 611507d7bb
Release Designate 5.0.0.0rc1
Change-Id: I0a0664d40ed7e0d00f8f7fa96185b27c8dfbf314
2017-08-14 17:34:55 +01:00
Tim Simmons 147878e92a Designate Pike-3 deliverables
Designate and designate-dashboard releases for pike milestone 3

Change-Id: I688023656b3a65a53f69566554eb251845648d30
2017-07-26 12:11:51 -05:00
Doug Hellmann a7f22abb10 remove send-announcements-to from pike projects
We no longer use the send-announcements-to field for anything.

Change-Id: Iec0b11ced00ea06ac459ad544b1cb2db20d2892d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-06-06 16:01:06 -04:00
Tim Simmons c839081ba2 Tag pike-1 designate deliverables
Change-Id: I905de031608a51297e6e5ab66e5075235cc80731
2017-04-13 12:05:47 -05: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