On Fri, Sep 14, 2018 at 10:20 AM, Elõd Illés <elod.il...@ericsson.com> 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 CI has started to fail and we've just been turning it off jobs as they fail. We had not planned on extended maintenance for Ocata (or Pike). We'll likely consider that starting with Queens. We could switch it to extended maintenance but without the promotion jobs we won't have packages to run CI so it would be better to just EOL it. Thanks, -Alex > [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, Juan Antonio Osorio Robles wrote: >> >> >> On 09/14/2018 09:01 AM, Alex Schultz wrote: >>> >>> On Fri, Sep 14, 2018 at 6:37 AM, Chandan kumar <chkumar...@gmail.com> >>> 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 upgrades in CI? >>>> >>> I think unless there are any objections around upgrades, we can drop >>> the promotion pipelines. It's likely that we'll also want to >>> officially EOL the tripleo ocata branches. >> >> sounds good to me. >>> >>> Thanks, >>> -Alex >>> >>>> Links: >>>> [1.] https://releases.openstack.org/ >>>> >>>> Thanks, >>>> >>>> Chandan Kumar >>>> >>>> >>>> __________________________________________________________________________ >>>> OpenStack Development Mailing List (not for usage questions) >>>> Unsubscribe: >>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >>> >>> >>> __________________________________________________________________________ >>> OpenStack Development Mailing List (not for usage questions) >>> Unsubscribe: >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
