This transition the Ocata branch to End of Life. The last patch of the
branch will be tagged with ocata-eol tag. The ocata branch cannot be
used anymore and will be deleted if this patch merges.
This is needed as stable/ocata is not actively maintained in the recent
period and thus gate is broken due to job failures. 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/ocata 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: I17f452f4802ebaa4d8afc1f85647a3a7ab0ee51b
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>
According to our extended maintenance documentation [0], we stated at
the start of the extended maintenance phase the "HEAD of the
appropriate branch will be tagged as $series-em", however, we did not
apply these tags to stable/ocata at the time. This adds ocata-em tags to
the ocata deliverables.
[0] https://docs.openstack.org/project-team-guide/stable-branches.html#extended-maintenance
Change-Id: Ibac7f787950bf23e9a75fce37a6b82ec45d7df89
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
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
Update the links for Ocata release notes to use HTTPS and to point to
the series-specific page.
Change-Id: Ib65c70f2760b8fa3cd94ede3ee7b74f9eaecf1d5
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This patch was prepared mechanically using
tools/add_release_note_links.sh
Change-Id: I4a7818f47f33a96d54d60713b73545bdaaff777f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a major version bump as there are several changes
involved which dropped deprecated functionality.
Change-Id: I1459bba8f16945d23ca2c16eb6714669b8215c15
Bring in empty deliverable files for things released in newton to
populate the data in ocata.
Depends-On: I7039b8344caaa053ae29913699fa8467283722ba
Change-Id: I9b9c776aad8acbdbb002a8e6615e3bf90095b2ca
Signed-off-by: Doug Hellmann <doug@doughellmann.com>