We need the actual content delivered in Magnesium release to be also updated in those JIRA tickets for Magnesium. This can be then used by the marketing folks to come up with a press release for the

Hello TSC and PTL ( bcc) Please submit your Aluminum release plans ( as jira TSC tickets) by 03/16/2020. Here is an example from BGPCEP Magnesium https://jira.opendaylight.org/browse/TSC-247 Here is

Thanks for letting us know.

Hello TSC members: Daniel has agreed to be my proxy for today's TSC call (Mar 12th), I would not be able to join the call tonight. Regards, Anil

Next TSC meeting is March 12, 2020 at 9 am Pacific Time. The zoom session for the meeting is: https://zoom.us/j/219174946. Agenda for this meeting is

Dear all, The problem has been identified and report in the documentation: bgpcep/docs/pcep/pcep-user-guide-path-computation.rst "Known Bug^^^^^^^^^When using BGP-LS for

Yes - I referred to only the technical meetings co-located at the ONES in April. Good to know there is a separate TAC meeting to discuss the June event.

Just to clarify.The TAC meeting will be discussing possible alternatives for the Unconference sessions and Technical Meetings that were to take place at ONES. Not the Developer & Testing Forum

Hi ODL folks, If you remember, ODL had decided to have our DDF in June along with rest of the LFN developer event. In addition, we had been looking into a possibility of some ODL developers attending

Thanks Casey & Thanh.

Hi Casey, Thanks for promptly and moving this issue forward. I can confirm that after a rebuild the new plastic-1007 staging repo was successfully able to close. Allan, You should be clear to move

Thanks for letting us know.

Hi all, A new regression was discovered in BGPCEP CSIT that is now blocking the release: https://jira.opendaylight.org/browse/BGPCEP-898 Once we get a handle on that, we will probably have some

Hi, everyone. I would like to share what information we have at this time. Plastic 2.1.6 was able to release on Jan 29th. After that time, the staging repository has seemed to be reporting at least

Hi all, I have updated the project proposal for Guice on Friday and incorporated Robert's review comments too - https://wiki.lfnetworking.org/display/ODL/ODL+Guice+Project Please feel free to add more

FYI, I have found this in the ODL charter [1], it is about License violations rather than security vulnerabilities (I believe Nexus IQ detects both): Paragraph c and d in section 7. Intellectual

I think there is a mismatch between this and what Casey communicated last Thursday, I wish you were there. My understanding of ODL project governance is exactly what you described in your email,

I am sorry, but I just cannot agree with this point. Each normal[0] OpenDaylight project is created sovereign. That means that each project is completely and ultimately responsible for defining and

Hi, everyone. Some of our IT/RE management team are out of the office today so we have not yet completed a proper investigation. Please give us until end of day Monday to respond. Sorry for the

Well, that is what LF is investigating now per my understanding but this should not block Allan to use the security team avenue. BR/Luis