On Mon, 16 Sep 2019, 18:33 Abhijit Kumbhare, <[email protected]> wrote:
> Yes - that (removing in SR1) sounds a good idea to me. > +1 On Mon, Sep 16, 2019 at 9:22 AM Luis Gomez <[email protected]> wrote: > >> If it is too late to remove SFC now I would advocate to remove it in >> Sodium SR1 (we did this in the past with other projects that suddenly >> became abandoned). The only way I can see SFC during Sodium support cycle >> is if someone steps up to do the basic project maintenance, but I do not >> think this is going to happen. >> >> BR/Luis >> >> On Sep 16, 2019, at 9:11 AM, Abhijit Kumbhare <[email protected]> >> wrote: >> >> Thanks for your thoughts Thanh and Anil - very good points. I agree with >> Thanh that we do not want to delay the release further. So the best course >> of action as Thanh suggested seems to be to release note that SFC test >> failure for Sodium and say that SFC is marked for removal as a managed >> project in Magnesium. We may want to add that SFC may not have any further >> fixes during the Sodium SRs as they are transitioning to a self managed >> project for Magnesium. >> >> Let us conclude this vote as not passed. I will respond on Luis' thread >> about overall release status. >> >> On Mon, Sep 16, 2019 at 7:09 AM Anil Vishnoi <[email protected]> >> wrote: >> >>> I believe it's not a matter of few test failing. It's pretty much dead >>> code in my opinion and i have a doubt that even it's basic usecase is >>> working anymore. >>> Now do we want to keep shipping this dead code and support it for next 1 >>> year (6 month stable support, 6 month security support)? I am not sure if >>> there is anyone to support this code even in self-managed mode. If removing >>> this code from managed project delays the relase by a week (nothing new in >>> ODL history, we did it many times, many reasons ), in my person opinion, we >>> should just do it. >>> >>> On Mon, Sep 16, 2019 at 6:42 AM Thanh ha <[email protected]> wrote: >>> >>>> I agree here. It seems wrong to me to remove it from Sodium this late >>>> into the release cycle unless we really want to delay the release some >>>> more. In the initial email thread this list Stephen's patch >>>> https://git.opendaylight.org/gerrit/c/netvirt/+/84369 will remove it >>>> from netvirt but this would require that to be merged and then we need to >>>> respin everything. >>>> >>>> Could we maybe release note the SFC test failure for Sodium and mention >>>> that it is marked for removal as a managed project in Magnesium? >>>> >>>> That would at least flag to the users that SFC has known issues and we >>>> can likely proceed with the release. >>>> >>>> Regards, >>>> Thanh >>>> >>>> On Mon, 16 Sep 2019 at 07:40, Abhijit Kumbhare <[email protected]> >>>> wrote: >>>> >>>>> Thanks for the feedback Robert and Daniel. We do need to disable SFC >>>>> from NetVirt, right? Isn't there an engineering effort required for that? >>>>> Or is it OK to ship with those tests failing? >>>>> >>>>> On Sun, Sep 15, 2019 at 10:41 PM Daniel De La Rosa < >>>>> [email protected]> wrote: >>>>> >>>>>> >>>>>> >>>>>> On Sun, Sep 15, 2019 at 10:28 PM Robert Varga <[email protected]> wrote: >>>>>> >>>>>>> On 16/09/2019 06:34, Abhijit Kumbhare wrote: >>>>>>> > Hello TSC, >>>>>>> > >>>>>>> > There was a discussion in the TSC meeting to move SFC project to >>>>>>> be a >>>>>>> > self managed project for Sodium as SFC members have mostly moved >>>>>>> on and >>>>>>> > have also not attended any TSC meetings. Subsequently we also sent >>>>>>> an >>>>>>> > email to the SFC project titled "SFC and Sodium". Since there was >>>>>>> no >>>>>>> > response, it is time for the TSC to vote on whether SFC should be >>>>>>> > removed from the Sodium release. >>>>>>> > >>>>>>> > *Hence please vote either -1, 0 or +1 for the following question:* >>>>>>> > * >>>>>>> > * >>>>>>> > *Shall SFC be removed from Sodium as a managed project and be >>>>>>> considered >>>>>>> > as a self managed project? Note - this will likely need us to >>>>>>> remove it >>>>>>> > from the Sodium distribution.* >>>>>>> >>>>>>> -1. >>>>>>> >>>>>>> The release is ready, this would require a re-spin and re-signoff >>>>>>> for a >>>>>>> release that is already 11 days late. >>>>>>> >>>>>>> What is the (very strong) reason to even be considering this? >>>>>>> >>>>>> >>>>>> I don't think there is one and I thought that we talked about doing >>>>>> this ( and other) projects to self managed for magnesium in the TSC >>>>>> meeting. I think is better to keep Sodium release date on time but start >>>>>> working on this ASAP for Magnesium >>>>>> >>>>>> my two pesos >>>>>> >>>>>> >>>>>>> >>>>>>> FTR: I strongly believe this pruning should have happened at the >>>>>>> Final >>>>>>> Checkpoint at the latest -- i.e. a month ago. >>>>>>> >>>>>>> Regards, >>>>>>> Robert >>>>>>> >>>>>>> -=-=-=-=-=-=-=-=-=-=-=- >>>>>>> Links: You receive all messages sent to this group. >>>>>>> >>>>>>> View/Reply Online (#18011): >>>>>>> https://lists.opendaylight.org/g/release/message/18011 >>>>>>> Mute This Topic: https://lists.opendaylight.org/mt/34161125/1964961 >>>>>>> Group Owner: [email protected] >>>>>>> Unsubscribe: https://lists.opendaylight.org/g/release/unsub [ >>>>>>> [email protected]] >>>>>>> -=-=-=-=-=-=-=-=-=-=-=- >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Daniel de la Rosa >>>>>> Customer Support Manager >>>>>> Lumina Networks Inc. >>>>>> e: [email protected] >>>>>> m: +1 408 7728120 >>>>>> >>>>> -=-=-=-=-=-=-=-=-=-=-=- >>>>> Links: You receive all messages sent to this group. >>>>> >>>>> View/Reply Online (#11900): >>>>> https://lists.opendaylight.org/g/TSC/message/11900 >>>>> Mute This Topic: https://lists.opendaylight.org/mt/34161393/1869318 >>>>> Group Owner: [email protected] >>>>> Unsubscribe: https://lists.opendaylight.org/g/TSC/unsub [ >>>>> [email protected]] >>>>> -=-=-=-=-=-=-=-=-=-=-=- >>>>> >>>> -=-=-=-=-=-=-=-=-=-=-=- >>>> Links: You receive all messages sent to this group. >>>> >>>> View/Reply Online (#18017): >>>> https://lists.opendaylight.org/g/release/message/18017 >>>> Mute This Topic: https://lists.opendaylight.org/mt/34164484/1199232 >>>> Group Owner: [email protected] >>>> Unsubscribe: https://lists.opendaylight.org/g/release/unsub [ >>>> [email protected]] >>>> -=-=-=-=-=-=-=-=-=-=-=- >>>> >>> >>> >>> -- >>> Thanks >>> Anil >>> >> -=-=-=-=-=-=-=-=-=-=-=- >> Links: You receive all messages sent to this group. >> >> View/Reply Online (#11903): >> https://lists.opendaylight.org/g/TSC/message/11903 >> Mute This Topic: https://lists.opendaylight.org/mt/34161393/1217165 >> Group Owner: [email protected] >> Unsubscribe: https://lists.opendaylight.org/g/TSC/unsub [ >> [email protected]] >> -=-=-=-=-=-=-=-=-=-=-=- >> >> >> -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group. > > View/Reply Online (#11905): > https://lists.opendaylight.org/g/TSC/message/11905 > Mute This Topic: https://lists.opendaylight.org/mt/34161393/1963340 > Group Owner: [email protected] > Unsubscribe: https://lists.opendaylight.org/g/TSC/unsub [ > [email protected]] > -=-=-=-=-=-=-=-=-=-=-=- >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4778): https://lists.opendaylight.org/g/sfc-dev/message/4778 Mute This Topic: https://lists.opendaylight.org/mt/34166269/21656 Group Owner: [email protected] Unsubscribe: https://lists.opendaylight.org/g/sfc-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
