This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: Idc9d27bded151a00b6388c780fb3ba5091916add
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>
This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag on the nova deliverables.
The hash used for the pike-em tag should match the last release on the
stable/pike branch.
Change-Id: I261b7116750bb678c5cc129d3e3e080efec3998f
These are the final releases for nova deliverables on the
stable/pike branch before the branch goes into extended
maintenance mode.
Co-Authored-By: Matt Riedemann <mriedem.os@gmail.com>
Change-Id: I64984811e5e3817ceaf053ad0ac8ae3c9e79d87d
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 is the first and so far only release for os-vif
in the queens series. Unless something major is needed
before the queens non-client library freeze, this will
also be the version we GA and branch for stable/queens.
This change also updates the release notes URL for the
pike deliverable.
Change-Id: Idd7f635295aff6e46391b82e45b89ef79d6d6c05
Except barbicanclient which is working on a critical fix and
neutronclient which had a late release request that we haven't
resolved.
Change-Id: Ib4866823c7f3477e09999106086a882d8f650b64
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
- This commit adds os-vif 1.7.0
- This release extends ovs hardware
offload support and fixes minor bugs
enabling multi vendor support.
Depends-on: I051fcc6fd136b389a6200076bd6fc3b73b626d5e
Change-Id: If8568e2a29b950e56e9bab8974c9c6ca80f63270
We no longer use the send-announcements-to field for anything.
Change-Id: Iec0b11ced00ea06ac459ad544b1cb2db20d2892d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Create the deliverable files for Pike based on the ones that were
released during Ocata. Leave out release and branch information, since
that will be filled in for the first release.
Change-Id: Idf3e9a3eadba86038f6b69527a109a0cad79bf8c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Elod Illes