Commit Graph

6 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
71d8083627 [blazar] 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: Id204b5d1aa085bbde5aa7c94c85d221eb1ee0329
2019-05-09 16:31:21 -04: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
Masahito Muroi
8d75f0311d Release python-blazarclient 0.3.1
This release fixes the backward compatibility issue in 0.3.0.

Change-Id: I444a69a045292c88f700437a2ba9bcb2ec9773a3
2017-12-21 15:38:42 -06:00
Pierre Riteau
8a556a3da4 Release python-blazarclient 0.3.0
Change-Id: I57fd52da3dd86a8f442d9ab785a694923d3b9d52
2017-12-21 22:06:43 +01:00