Thanks – I just subscribed to the TSC mailing list From: Abhijit Kumbhare <abhijitkoss@...> Date: Thursday, January 16, 2020 at 2:05 AM To: Luis Gomez <ecelgp@...> Cc: Robert Varga <nite@...>,

Approved. However I have requested Brian and Dan to subscribe to the TSC mailing list to avoid the need to manually approve each message.

Brian, all: We really don't have the resources to accommodate an OpenDaylight upgrade in Frankfurt. As Brian notes, we have definitely seen breaking changes in SRs before, and we simply did not have

Dan's the one in charge but we have seen breaking changes in SR's before - sometimes it happens when you have to up rev so we dont do it lightly. Neon SR3 simply came out after we had to commit to

Its too late for Frankfurt to switch to Sodium SR1 Brian

Does seem like Release to EOL is rather short (1 year) and doesn’t factor in the SR’s but I think this is more about bug fixes and patches not whether a client can use it. I’m sure this isnt

Thank you all whoever voted for me. Thanks & Regards, Karthikeyan.

FYI it looks like folks are not getting the messages in this thread, so if anyone is moderator for TSC channel please approve pending messages.

Understood. I am by no means implying that we do not break things, because we do and sometimes we do not even know. Sorry for the wall of text that follows. Given that both projects are on a 6-month

Well, ONAP's release-to-EOL is even more aggressive, with no support overlap between releases at all (https://wiki.onap.org/display/DW/Long+Term+Roadmap) :) Don't get me wrong, I am not pushing for

Dan Timoney has been working with Luis including using meetings for the ODL distribution. We can figure out any version issues in the next meeting with ONAP. Dan had mentioned that they were planning

Quoting the minutes: One thing re: releases, fresh off the ONAP DDF: ONAP Frankfurt is currently targeting the use of Neon SR1 (or perhaps SR3), which puts that release

Greetings Robert: Trying to catch up on where we are with the sonarcloud migrations. I think another issue has been identified with 0% coverage, that is caused by an update on the Java analyzer. With

LFN Communities, As we embark on 2020, we invite you to join us for a look back at 2019 -- a significant year for LF Networking. The LF Networking 2019 Year in Review has now been published to the

Hi TSC, Please find & review the TSC meeting minutes below: TSC Meeting minutes Jan 9, 2020 If you find something that needs to be amended, please let me know - we can update it on the confluence page

Hi Robert, et al, Hope you are doing well. From the last TWS there was an action to review the lighty proposal at the start of the year (06-Jan). Since you could not make it today and last week for

Hi all, Just a reminder of the TWS scheduled today at 9:00 AM PST to further on "Micro-distribution for ODL". Zoom - https://zoom.us/j/522266747 As per the last minutes

Thanks Luis.. just a small correction to make this more accurate... after Magnesium GA, we will be releasing Sodium SR3 Magnesium GA -> Sodium SR3 -> Magnesium SR1 -> Aluminum GA -> Magnesium SR2 ->

I think the 6 months after Magnesium release will conflict with Aluminum release. If we really want to have 1 effective release every ~2 months, we have to space the SRs ~4 months: Magnesium GA ->

Hello TSC members, here is my current proposal, basically a Magnesium SR every 3 months. Let's review this on today's meeting or over email MagnesiumMagnesium