openstack/releases
Code Issues Proposed changes

Remove per-release highlights for Pike

Browse Source 
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
This commit is contained in:
Sean McGinnis
2018-02-20 10:14:43 -06:00
committed by Doug Hellmann
parent c2df096338
commit 8df28d81d9
27 changed files with 19 additions and 239 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
deliverables/pike/congress.yaml
View File

@@ -20,9 +20,6 @@ releases:
- hash: 4a9566adf6c1bb19981aee6973f5f677be5a9d7b
repo: openstack/congress
version: 6.0.0.0rc1
highlights: |-
- 'New library of useful, importable policies greatly reduces barrier to use.'
- 'Congress Horizon-plugin separated into congress-dashboard project, with improved usability and helpful new features such as a policy monitoring panel.'
- diff-start: 5.0.0.0rc1
projects:
- hash: 4a9566adf6c1bb19981aee6973f5f677be5a9d7b