<html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hi,</p>
<p>First of all, sorry for the late response. I've checked what is
the current state of Octavia according to <b>openstack/releases</b>
repository and it seems even Ocata is not yet EOL'd. As far as I
see from the discussion, the Team wants to move Queens and Pike to
EOL. I suggest to do it branch by branch, so as a first step
please EOL Ocata with the steps described in Stable Branches page
[1]. If that is ready, then do the same for Pike, and then Queens.
If you have any question feel free to ping me on IRC (elod @
#openstack-stable or #openstack-releases) and I'll try to help
you.</p>
<p>Note: Extended Maintenance helps operators / interested parties
with having a common place where they can cooperate and push
(backport) bugfixes to ease everyone's work. As long as there are
someone (in best case: more people) who comes and fixes bugs and
maintains the CI, the "EM" branches can be kept open. (To keep the
CI functional, it is usually easier if it is done regularly with
small fixes, when something failure comes in). Of course, if there
are no volunteer, who fixes the gate failures and a branch becomes
"Unmaintained" for ~6 months, then it should be EOL'd. Sorry if
this was obvious, just wanted to have it here :)<br>
</p>
<p>Thanks,<br>
</p>
<p>Előd</p>
<p>[1]
<a class="moz-txt-link-freetext" href="https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life">https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life</a></p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2020. 04. 05. 13:19, Carlos
Goncalves wrote:<br>
</div>
<blockquote type="cite" cite="mid:CAM7b86hugDWGLBwQi+RSsD8FABrczzqWNbe3BMWJ_xJj9Aag5A@mail.gmail.com">
<div dir="ltr">Hey folks,
<div><br>
</div>
<div>Apologies for my late response in this thread.</div>
<div><br>
</div>
<div>This topic was also discussed on IRC #openstack-lbaas on
March 19 [1]. I had some initial reservations that were
clarified as we discussed the topic further. I am supportive
now of declaring the Queens release EOL.</div>
<div><br>
</div>
<div>Carlos</div>
<div><br>
</div>
<div>[1] <a href="http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack-lbaas.2020-03-19.log.html" moz-do-not-send="true">http://eavesdrop.openstack.org/irclogs/%23openstack-lbaas/%23openstack-lbaas.2020-03-19.log.html</a></div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 20, 2020 at 2:44
AM Michael Johnson <<a href="mailto:johnsomor@gmail.com" moz-do-not-send="true">johnsomor@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
Erik,<br>
<br>
The Queens branch entered Extended Maintenance (EM) on August
25th,<br>
2019 (later extended to October 25th, 2019 to accommodate
release team<br>
resources[1]) and was tagged EM on November 6th, 2019.<br>
<br>
This proposal is to exit Extended Maintenance and mark the
Queens<br>
release as End-of-Life(EOL). This is following the guidelines
for<br>
stable branch releases[2].<br>
<br>
Currently the Octavia team is maintaining five branches and
supporting<br>
queens is becoming more difficult as the test jobs are still
based on<br>
the Ubuntu Xenial release (released April 21. 2016). The
python 2.7<br>
end-of-life combined with the older OS version has made it
hard to<br>
keep reliable test jobs[3]. Backporting patches is also
becoming more<br>
difficult as the Octavia code base has rapidly evolved in the
two<br>
years since it was released.<br>
<br>
If you or others are willing to help us with fixing the queens
jobs<br>
and backporting patches, that would be great and we may be
able to<br>
leave the queens branch in Extended Maintenance. If not, Adam
is<br>
proposing we move it into EOL.<br>
<br>
Personally, I agree with Adam that it is time to mark the
Queens<br>
release as EOL. Since you can run newer releases of Octavia on
older<br>
clouds (as many do), the branch cannot release under EM, and
patches<br>
on that branch are few.<br>
<br>
Michael<br>
<br>
[1] <a href="https://github.com/openstack/releases/commit/be797b61677b1eafc0162bd664f09db54287ac81#diff-8fa0a5ef8165646609d2f3d50646c597" rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/openstack/releases/commit/be797b61677b1eafc0162bd664f09db54287ac81#diff-8fa0a5ef8165646609d2f3d50646c597</a><br>
[2] <a href="https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life" rel="noreferrer" target="_blank" moz-do-not-send="true">https://docs.openstack.org/project-team-guide/stable-branches.html#end-of-life</a><br>
[3] <a href="https://zuul.openstack.org/builds?project=openstack%2Foctavia&branch=stable%2Fqueens&pipeline=check&job_name=octavia-v2-dsvm-scenario" rel="noreferrer" target="_blank" moz-do-not-send="true">https://zuul.openstack.org/builds?project=openstack%2Foctavia&branch=stable%2Fqueens&pipeline=check&job_name=octavia-v2-dsvm-scenario</a><br>
<br>
On Thu, Mar 19, 2020 at 11:40 AM Erik McCormick<br>
<<a href="mailto:emccormick@cirrusseven.com" target="_blank" moz-do-not-send="true">emccormick@cirrusseven.com</a>>
wrote:<br>
><br>
><br>
> On Thu, Mar 19, 2020, 11:57 AM Adam Harwell <<a href="mailto:flux.adam@gmail.com" target="_blank" moz-do-not-send="true">flux.adam@gmail.com</a>> wrote:<br>
>><br>
>> I'm officially proposing dropping support for the
queens stable branch of Octavia.<br>
>> Given a quorum of cores, we will move forward with
marking it EOL and all that entails.<br>
><br>
><br>
> Adam,<br>
><br>
> Why can't it go into EM Instead of EOL?<br>
><br>
> Thanks<br>
> Erik<br>
><br>
>><br>
>> Thanks,<br>
>> --Adam<br>
<br>
</blockquote>
</div>
</blockquote>
</body>
</html>