Commit Graph

16 Commits

Author SHA1 Message Date
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
01072817cc
[mistral] 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: Ia2f17d020bb925e3c9e365baa3cf6e22d4f2ba58
2019-05-10 13:30:43 -05:00
Tony Breeds
05ecdb0242
[mistral] 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: Ibddf1180f5687bf5c8d24198aff3dbfdaf1c7813
2019-05-09 16:13:32 -05: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
Lingxian Kong
461473b173 Release python-mistralclient 3.1.4 for Pike
Change-Id: Ibfb1d7c4ca0f3ea8a7f0c91a37a54147a550fa19
2017-10-30 16:02:18 +13:00
Lingxian Kong
b7838df125 Release python-mistralclient 3.1.3 for Pike
Change-Id: I4c37d596940ea0a665fbfc4bda32df7325ddb93b
2017-09-06 15:08:52 +12: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
Lingxian Kong
b40b8f7fab Release python-mistralclient 3.1.2 for Pike
Change-Id: I04a4457359f12f1c0d6e24d4853bc8a11ede255b
2017-08-07 10:20:57 +12:00
Doug Hellmann
c085ac7568 add release-notes URLs for some pike deliverables
Update the deliverable files that have pike release notes
already. Some of the changes are normalization from rewriting the
files. The only differences should be the order of items and the value
of the 'release-notes' key.

Change-Id: I9bd7ec180eee007d80297735688e7702a137153f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-08-01 10:29:04 -04: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
Lingxian Kong
66ca7194fb Release python-mistralclient 3.1.1
Change-Id: I501b57a4966231e8227113ae1a777c98b5ce0ac6
2017-07-25 16:05:00 +12: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
Lingxian Kong
df8a93f3af Release python-mistralclient 3.1.0
Change-Id: I4b13649dee6cfdc7af44003b772783352e235d47
2017-04-21 21:49:41 +12: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