<div dir="ltr"><div style="text-align:left">Hi,</div><div style="text-align:left"><br></div><div style="text-align:left">From the upgrades/updates point of view it should be ok dropping the Ocata jobs. <br></div><div style="text-align:left">The only one covering Ocata to Pike upgrade in upstream CI is running in RDO cloud as a non voting one,</div><div style="text-align:left">and it is failing at the moment.</div><div style="text-align:left"><br></div><div style="text-align:left">Thanks,</div><div style="text-align:left"><br></div><div style="text-align:left">Jose Luis<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 14, 2018 at 6:33 PM Alex Schultz <<a href="mailto:aschultz@redhat.com">aschultz@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, Sep 14, 2018 at 10:20 AM, Elõd Illés <<a href="mailto:elod.illes@ericsson.com" target="_blank">elod.illes@ericsson.com</a>> wrote:<br>
> Hi,<br>
><br>
> just a comment: Ocata release is not EOL [1][2] rather in Extended<br>
> Maintenance. Do you really want to EOL TripleO stable/ocata?<br>
><br>
<br>
Yes unless there are any objections.  We've already been keeping this<br>
branch alive on life support but CI has started to fail and we've just<br>
been turning it off jobs as they fail.  We had not planned on extended<br>
maintenance for Ocata (or Pike).  We'll likely consider that starting<br>
with Queens.  We could switch it to extended maintenance but without<br>
the promotion jobs we won't have packages to run CI so it would be<br>
better to just EOL it.<br>
<br>
Thanks,<br>
-Alex<br>
<br>
> [1] <a href="https://releases.openstack.org/" rel="noreferrer" target="_blank">https://releases.openstack.org/</a><br>
> [2]<br>
> <a href="https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html" rel="noreferrer" target="_blank">https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html</a><br>
><br>
> Cheers,<br>
><br>
> Előd<br>
><br>
><br>
><br>
> On 2018-09-14 09:20, Juan Antonio Osorio Robles wrote:<br>
>><br>
>><br>
>> On 09/14/2018 09:01 AM, Alex Schultz wrote:<br>
>>><br>
>>> On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar <<a href="mailto:chkumar246@gmail.com" target="_blank">chkumar246@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> Hello,<br>
>>>><br>
>>>> As Ocata release is already EOL on 27-08-2018 [1].<br>
>>>> In TripleO, we are running Ocata jobs in TripleO CI and in promotion<br>
>>>> pipelines.<br>
>>>> Can we drop it all the jobs related to Ocata or do we need to keep some<br>
>>>> jobs<br>
>>>> to support upgrades in CI?<br>
>>>><br>
>>> I think unless there are any objections around upgrades, we can drop<br>
>>> the promotion pipelines. It's likely that we'll also want to<br>
>>> officially EOL the tripleo ocata branches.<br>
>><br>
>> sounds good to me.<br>
>>><br>
>>> Thanks,<br>
>>> -Alex<br>
>>><br>
>>>> Links:<br>
>>>> [1.] <a href="https://releases.openstack.org/" rel="noreferrer" target="_blank">https://releases.openstack.org/</a><br>
>>>><br>
>>>> Thanks,<br>
>>>><br>
>>>> Chandan Kumar<br>
>>>><br>
>>>><br>
>>>> __________________________________________________________________________<br>
>>>> OpenStack Development Mailing List (not for usage questions)<br>
>>>> Unsubscribe:<br>
>>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>>><br>
>>><br>
>>> __________________________________________________________________________<br>
>>> OpenStack Development Mailing List (not for usage questions)<br>
>>> Unsubscribe:<br>
>>> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>><br>
>> __________________________________________________________________________<br>
>> OpenStack Development Mailing List (not for usage questions)<br>
>> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div>