If Luis and Jamo are fine with, it's +1 from me as well. Regards, Robert

Hi Komer, You have added my name as NETCONF PTL, but I am not 😊 And I am PTL for ServiceUtils project, not Jakub. I think both of these got swapped. Thanks, Faseela

Hi PTLs, This is Komer Poodari at Aarna Networks. We are working on the Sodium Release outbound messaging activity. Please ensure current information on the salient additions getting delivered in the

Hi, Casey Can I get a free ticket for ONS by submitting a topic to this ODL DDF? 发件人: TSC [mailto:tsc-bounces@...] 代表 Casey Cain 发送时间: 2019年8月20日 1:08 收件人: TSC

Thank you, sir, for creating the subpage place holder. I fill in the table to start with and also reach out to the PTLs. Best regards, Komer -- Komer Poodari Aarna Networks, Inc. (408)316-3587

Added the Release & TSC mailing lists. For creating a wiki – you can just create a new wiki page for the Sodium Info. Since the main releases information was a bit messed up, I created a main

Historically, we have not wanted to let regressions in to the release between SRs. Because of that I vote to get the fix in and respin +1 I think the bug was known since

TPCE is self-managed but they have found an issue in netconf project: https://jira.opendaylight.org/browse/NETCONF-637 https://git.opendaylight.org/gerrit/#/c/netconf/+/83679/ If the issue is not

Thanks Robert for pointing that out. Neon SR2 was originally scheduled for 8/8 but as suggested by Abhijit, we should release it since Transport PCE is self managed. We just need to for all projects

I agree we should release it - and thanks for the link. Per the link the Neon SR3 is December 5 - I think we should keep that schedule (even though there has been a delay on SR2). Since the

You are looking at the wrong release, it is clearly listed here: https://docs.opendaylight.org/en/stable-neon/release-process/release-schedule.html as: Service Release 2 2019-08-08 i.e. we are

Luis, Is your suggestion to pick up the TRNSPRTPCE-126 patch in Neon SR3? BTW I do not see the schedule for Neon SR3 at https://docs.opendaylight.org/en/latest/release-process/release-schedule.html -

OK, lets not wait more time, here is my +1, other TSC members can add to this mail. BR/Luis

Hello, based on the previous, I do not see when the MD-SAL wiring bits will land (but it is on my radar). At some point, this patch (or something equivalent) will have to land in neutron, lest it is

Greetings Robert; I believe any change after the branch is locked requires the TSC vote before anyone from releng can submit/merge the change. Thanks, Anil

Hello, everyone. If you are a developer within the OpenDaylight Project or would like to become one soon, please join us at our next OpenDaylight Developer Forum. This event is by developers for

Thanks. If/when the decision is made on doing a re-spin of Neon SR2, can someone from RelEng just 'Submit' the patch? Regards, Robert

TRNSPRTPCE-126 was only medium priority so it never showed up on our release dashboard when reviewing status of Neon. I just changed it to highest priority. JamO

Hi all TransportPCE has a blocking issue with Neon SR2 that is linked to a bug in our Netconf/restconf upstream dependency and is described in Jira

We still need to move the Mg AR job to jdk11. Please merge https://git.opendaylight.org/gerrit/#/c/releng/builder/+/83642/