Hi,
>From the upgrades/updates point of view it should be ok dropping the Ocata
jobs.
The only one covering Ocata to Pike upgrade in upstream CI is running in
RDO cloud as a non voting one,
and it is failing at the moment.
Thanks,
Jose Luis
On Fri, Sep 14, 2018 at 6:33 PM Alex Schultz wrote:
On Fri, Sep 14, 2018 at 10:20 AM, Elõd Illés wrote:
> Hi,
>
> just a comment: Ocata release is not EOL [1][2] rather in Extended
> Maintenance. Do you really want to EOL TripleO stable/ocata?
>
Yes unless there are any objections. We've already been keeping this
branch alive on life support but
Hi,
just a comment: Ocata release is not EOL [1][2] rather in Extended
Maintenance. Do you really want to EOL TripleO stable/ocata?
[1] https://releases.openstack.org/
[2]
https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.html
Cheers,
Előd
On 2018-09-14 09:20,
On 09/14/2018 09:01 AM, Alex Schultz wrote:
> On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar wrote:
>> Hello,
>>
>> As Ocata release is already EOL on 27-08-2018 [1].
>> In TripleO, we are running Ocata jobs in TripleO CI and in promotion
>> pipelines.
>> Can we drop it all the jobs related to
On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar wrote:
> Hello,
>
> As Ocata release is already EOL on 27-08-2018 [1].
> In TripleO, we are running Ocata jobs in TripleO CI and in promotion
> pipelines.
> Can we drop it all the jobs related to Ocata or do we need to keep some jobs
> to support
Hello,
As Ocata release is already EOL on 27-08-2018 [1].
In TripleO, we are running Ocata jobs in TripleO CI and in promotion pipelines.
Can we drop it all the jobs related to Ocata or do we need to keep some jobs
to support upgrades in CI?
Links:
[1.] https://releases.openstack.org/
Thanks,
