Commit Graph

11 Commits

Author SHA1 Message Date
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
7553c4738f congress-dashboard 1.0.1
Change-Id: I451476eaa721648e5c8b1592f97bfd014b6d3a40
2019-04-05 14:11:22 -07: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
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
Sean McGinnis
030907fcc9 Add release-type directives for pike
Some projects have updated their release-type for horizon
plugins in queens, but a similar change has not been done
in pike. Rather than waiting for their first stable release
request to fail, adding these changes to those deliverables
to account for these changes.

Change-Id: Ifd51d3dd1d04b1bb11d311fc46f6faf642d432c4
2018-02-02 16:06:14 -06: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
Eric Kao
009fe14490 Request congress-dashboard Pike-RC1
Change-Id: I48e995897781edf92fb1aca633c1ef2d708157c4
2017-08-08 15:32:34 -07:00
Eric Kao
cd61f9ca68 request congress-dashboard pike-3 release
Change-Id: I58fc9d4fa0ee6cfcf42dd793427b117b350f88fa
2017-07-26 21:54:18 -07:00
Eric Kao
eb293263c9 request P2 release of congress and dashboard
Change-Id: I016c35223672d9c2aa6665486ee8ae1eea42a062
2017-06-08 13:12:39 -07:00