releases/deliverables/pike/cloudkitty.yaml
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

18 lines
428 B
YAML

---
include-pypi-link: yes
launchpad: cloudkitty
release-model: cycle-with-intermediary
team: cloudkitty
type: service
branches:
- name: stable/pike
location: 6.0.0
releases:
- version: 6.0.0
projects:
- repo: openstack/cloudkitty
hash: 069ea4ea237a1abbb1a0fe5d81263b69c733ff11
repository-settings:
openstack/cloudkitty: {}
release-notes: https://docs.openstack.org/releasenotes/cloudkitty/pike.html