Commit Graph

12 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
Sean McGinnis
03dc045a45 Add repo settings and remove highlights for Mitaka
We've deprecated per-release highlights and are now removing them.
We also now require repository-settings for deliverables. This adds
the one and removes the other.

Change-Id: I91e5d5b1ce0ca78c242d65a6f4aa90473b28ce79
2018-02-23 08:45:02 -06:00
Doug Hellmann
2ff9a62a94 remove send-announcements-to from mitaka projects
We no longer use the send-announcements-to field for anything.

Change-Id: I3ed3f7f43048871a52a88d92331ee73bbf4d501d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-06-06 10:17:00 -04:00
Doug Hellmann
14b1c312ce add release model and deliverable type (m)
Change-Id: Ia60873d6ecfc693ea0404d8dce7490fdd6e567cc
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2016-11-09 17:09:02 -05:00
Doug Hellmann
448a1852a0 add team field for mitaka deliverables
Change-Id: I1df165573e64685130dbd88aff997483718fdd3f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2016-06-09 14:34:15 -04:00
Amrith Kumar
ddaec334e5 Release Trove, dashboard and client
These are changes for the Mitaka branch.

Significant bug fixes in Trove as well as capping requirements in
Trove client for keystoneclient <3.0.0, and the dashboard to address
significant bugfixes.

Change-Id: I1292211cde4434e617019c367a34c36e88df6c02
2016-05-18 15:43:03 -04:00
Amrith Kumar
888eafdfa7 Update python-troveclient deliverable for mitaka
Version 2.1.0 of the python-troveclient included a change that broke
compatibility. This change is to request that 2.1.1 (which has the fix
for the compatibility) be released with Mitaka.

This however is subject to the fact that Trove has a change that was
granted an FFE, and that change has a client side component. That
change (https://review.openstack.org/#/c/290177/) will land and then I
will request 2.2.0 be tagged.

Change-Id: I5f113c7e4a3af50b34c1cceb542ffc5a71d9395c
Related-Bug: #1538506
2016-03-10 08:20:47 -05:00
Amrith Kumar
8facc0cb26 Release python-troveclient version 2.1.0
Change-Id: I26f37e5d64e09e7357cf3c52af7a209cf4ec1c6a
2016-03-03 19:47:08 -05:00
Doug Hellmann
3c42c08ffc add a flag for whether to report the PyPI link for releases
The release script will copy this flag into the tag message so the
announce script can read it and adjust its output accordingly.

Change-Id: I491fb9e6edd57a3ec1c0b85c8dd9e22d5f09e6b2
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2016-02-08 12:30:34 -05:00
Craig Vyvial
6bb50ef01c Release python-troveclient 2.0.0
Requirements update: If9a71eaf9215f24a9dc6aba454be9205c0c8435a

Change-Id: I879aea7ea027331b4e3358c7bdfb30b9f601b362
2016-01-21 12:46:39 -06:00
Doug Hellmann
df0ea3ffed add send-announcements-to field
For each deliverable, we need to know where to send release
announcements. Rather than building a rule set based on the project type
from the governance repository, just ask for email addresses here in the
deliverable files.

This change also removes a malformed release entry to pass more recent
validation checks.

Change-Id: I41f3f4874464b37ff95ec1e41a0b6993b62dcf1d
2016-01-07 18:56:58 +00:00
Craig Vyvial
c563ea6383 python-troveclient 1.4.0
Change-Id: Ic025b66d3ed19179a2719dff01018f68e6676c22
2015-11-03 13:06:11 -06:00