Pike branch for networking projects has many issues in the last cycles
and few actual backports on them.
Some projects' (bgpvpn and bagpipe) pike is already EOL-d, so it is
time to do the same for the remaining projects also as for the
announcement mail (see [1]) there was no answer and desire to keep the
pike branch open.
[1]: http://lists.openstack.org/pipermail/openstack-discuss/2022-April/028126.html
Change-Id: Iad31204a859d87009640b79b4eb59efe81ad18b5
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
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: Ifc2212664deb968906423fe7d289a109e4375afa
This is a procedural review to tag a final release for each deliverables ; and
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: I380dde919d18b48549e91fa46b05803955dee108
This patch releases the following project stable branches:
stable/queens:
openstack/octavia 2.0.1
openstack/octavia-dashboard 1.0.1
stable/pike:
openstack/octavia 1.0.2
openstack/neutron-lbaas 11.0.3
openstack/neutron-lbaas-dashboard 3.0.2
These include backported bug fixes and translation updates.
Change-Id: I237f3391f4dc756531fdeaf3509962eda46686e7
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
The Pike release script had a typo that caused the release emails to
have incorrect diff output.
This patch causes the validate test to catch more typos for releases
and branches. It also fixes the typos in the existing deliverables
files so they will pass future validation.
Change-Id: If173ba0b3d8c427f0bf5f3e4972dd0848459c951
Due to a mistake, the Pike release for the octavia projects was missing
some patches merged to stable/pike. This release sets these projects up
for pike properly.
Change-Id: I71e91f1fd20c7ecce6f45a3b646f47c5b818c086
We no longer use the send-announcements-to field for anything.
Change-Id: Iec0b11ced00ea06ac459ad544b1cb2db20d2892d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Proposing to switch neutron-lbaas-dashboard from independent release
to cycle-with-milestones to better support translation timing.
This patch will also create a Pike-1 release.
Change-Id: Icba3df8927a9be480d47030910ca2a034be7a3cf
elajkat