12 Commits

Author SHA1 Message Date
Tony Breeds
fad431ba2a [senlin] 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: I0a70fe411552ed28ae1c7b9bc9eec0ef46bf602f
2019-04-16 15:53:19 +10:00
Tony Breeds
78e6bfc6eb [senlin] 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: Ie913b0efbb48512a447ac15d1bbe5384b564913e
2019-04-16 15:53:15 +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
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
tengqm
5f8e876a4a Pike RC for Senlin
Change-Id: I3ffb34dc1e03c77ab92f199fd81d8a7af1bb11fe
2017-08-10 09:55:12 -04:00
tengqm
f9f80f0861 Release senlin pike-3
Change-Id: I97835f8e0676880e7099fd7fc8fd05a2ae23fe16
2017-07-26 09:12:47 -04:00
tengqm
155e64f8a6 Senlin pike-2 milestone
Change-Id: Iff5386cf8ff41c5e2a932b3505d956c5ec934e51
2017-06-08 08:35:18 -04: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
tengqm
b0f5bcc3c1 Release senlin pike-1
Change-Id: I921e5d20795e598bd70da3cc37d038a94d053855
2017-04-13 05:26:55 -04: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