Commit Graph

15 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
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
Eric K 8fc7e8355d congress 6.0.2
Change-Id: I52e3926f466fbca19b41b4d46afabb1737d096e2
2019-04-09 23:44:36 +00:00
Sean McGinnis 8df28d81d9 Remove per-release highlights for Pike
We've been warning that these are deprecated for awhile now, and
we now have enforcement in place to make sure no new highlights
are added.

We also have some automation that rewrites the deliverable files
but does not always do a great job, resulting in poorly formatted
text that causes warnings in the validation job.

Since many folks new to the release process, and some that have
done it for awhile, look at existing files to see what to do for
new releases, they do assume highlights should be used and end up
adding them to their deliverable file. Since most of these also
do not know to run local validatation, this results in gate
resources being used to just now be rejected with the current
checks.

To help prevent this from happening, and to get rid of the warning
messages from poor reformatting, this just removes highlights
from the last few releases.

Change-Id: Ie0b0e241c38f84bbc7b1ef5b09e97dc8ec466b39
2018-02-21 16:22:49 -05:00
Eric K c10d95b4b9 Congress 6.0.1 maintenance release
Change-Id: I9bc88e53183fad9bfeae1a87876fca5c9a877a9d
2018-02-13 12:59:36 -08: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
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
Thierry Carrez 175eb304c5 Add Pike release notes links
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
2017-08-18 10:13:11 +02:00
Eric Kao 979394ae75 request congress Pike-RC1 release
Change-Id: Ic76b7af18e29145d5b6ed57d0438e11815cd5909
2017-08-10 21:30:15 +00:00
Eric Kao f92715a059 request congress pike-3 release
Change-Id: Ic4ec13cbd8c5f206c170de595e612ded0f859a95
2017-07-26 21:51:57 -07:00
Eric Kao eb293263c9 request P2 release of congress and dashboard
Change-Id: I016c35223672d9c2aa6665486ee8ae1eea42a062
2017-06-08 13:12:39 -07: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
Eric Kao a9357961c7 Release Congress Pike-1
Change-Id: Iacb67383976ce700937fd525e20f7e146e017802
2017-04-13 14:44:10 -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