releases/deliverables/ocata/os-brick.yaml
Sean McGinnis 9d3a3eae66 Remove per-release highlights for Ocata
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: I5753436c7fb99240eb7a6f691c81e580ef8e7ac9
2018-02-21 16:22:49 -05:00

38 lines
1.0 KiB
YAML

---
launchpad: os-brick
team: cinder
type: library
release-model: cycle-with-intermediary
include-pypi-link: yes
release-notes: https://docs.openstack.org/releasenotes/os-brick/ocata.html
branches:
- name: stable/ocata
location: 1.11.0
releases:
- version: 1.7.0
projects:
- repo: openstack/os-brick
hash: 9bfb727565c343716f1f1f1f12a40c9493e84952
- version: 1.8.0
projects:
- repo: openstack/os-brick
hash: e016afb78cfd44cdc1fb77012814ca4cf8a8b9d3
- version: 1.9.0
projects:
- repo: openstack/os-brick
hash: 871cd1a6f271fdd2f0037f0b88a45dad97301a05
- version: 1.10.0
projects:
- repo: openstack/os-brick
hash: 1a9b90b02956e682f842c1105e5e5dd4f5a7fe7d
- version: 1.11.0
projects:
- repo: openstack/os-brick
hash: 6a180265560d5e0bab80e47ac25c15906d1165fb
- projects:
- hash: fc21f4f02026d2993bb7a7bb5f2324dbbece091b
repo: openstack/os-brick
version: 1.11.1
repository-settings:
openstack/os-brick: {}