8df28d81d9
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
30 lines
867 B
YAML
30 lines
867 B
YAML
---
|
|
launchpad: congress
|
|
release-model: cycle-with-milestones
|
|
team: congress
|
|
type: horizon-plugin
|
|
release-type: python-pypi
|
|
releases:
|
|
- version: 1.0.0.0b2
|
|
projects:
|
|
- repo: openstack/congress-dashboard
|
|
hash: 9ce12571a6cbe21fbe8ea862f7ab73385529f70f
|
|
- version: 1.0.0.0b3
|
|
projects:
|
|
- repo: openstack/congress-dashboard
|
|
hash: 491c96dfaa70fae9784815ceae28285cfa2efa17
|
|
- projects:
|
|
- hash: acc972d6563fb2b0a41cfa52f85088cbd9a23783
|
|
repo: openstack/congress-dashboard
|
|
version: 1.0.0.0rc1
|
|
- projects:
|
|
- hash: acc972d6563fb2b0a41cfa52f85088cbd9a23783
|
|
repo: openstack/congress-dashboard
|
|
version: 1.0.0
|
|
branches:
|
|
- location: 1.0.0.0rc1
|
|
name: stable/pike
|
|
release-notes: https://docs.openstack.org/releasenotes/congress-dashboard/pike.html
|
|
repository-settings:
|
|
openstack/congress-dashboard: {}
|