https://git.opendaylight.org/gerrit/c/netconf/+/93366 is in, good to go. Should be in tonight's autorelease. Manually tested okay, UTs are forthcoming. Regards, Robert

No worries, thanks for the update! We will wait until that NETCONF-736 is resolved.. @Anil Belur please let us know if you are getting these emails

Eh, sorry, I have one critical patch to NETCONF, will merge it as soon it verifies. It is a blocking issue going as far as Sodium SR4, so we definitely want it in SR1. Details are at

Hi folks, The next week TWS session will be on Nov 2, 2020 at 9 am Pacific Time. The zoom session for the meeting is: https://zoom.us/j/522266747?pwd=ek1mZHpXY1FzTms5Z1FYRjlZQkZBUT09. The meeting page

Manoj, We have decided to move the topic to next week. I will send out a separate email for the topic. -Abhijit

Hi All, Are we having this meeting today? Best Regards, Manoj

Thanks Robert. @Anil Belur please proceed with Aluminium code freeze as requested

This activity is now done, the branch is back to normal as of https://jenkins.opendaylight.org/releng/job/distribution-merge-managed-aluminium/2580/. Regards, Robert

The patches are being merged now, expect some usual disruption while they are being merged. Regards, Robert

Hmm, weird, why is this even needed? It does look like ConfigProperties.getProperty() requires OSGi runtime to execute -- which your UT is not. We typically reserve this to the runtime, where

The MRI update for this release is staged here: https://git.opendaylight.org/gerrit/q/topic:mri-aluminium-sr1 Multipatch build passed

FYI, here are the patches to move netvirt project to SM: https://git.opendaylight.org/gerrit/q/topic:netvirt-sm We might need to expedite these patches if netvirt project keeps blocking the

Hi Robert, I had spent some time today on looking at netvirt patch[0] and fixed a few of errors and still not able to identify the root cause of the below jenkins ERRORs. Please let us know if

I do not have objections to this proposal. Also starting the first elections right away seems better than waiting.

As a reminder, we will proceed with Aluminium code freeze for SR1... I'll pick a RC then and hopefully we can have the community to help with this release. Thanks

With 6 votes, the vote passes - so Robert is now a committer on the OpenFlow Plugin project. Please follow the standard process (yaml, etc.) to get the committer rights assigned.

Why not do the following? Declare we will have 2 elections - one main election immediately and another one 3 months after the main election to give new members a chance to establish

Hi TSC members, Please vote to formalize the developer best practices document

Fair enough, what if we just start an "open" thread before the official nomination period to see who has intention to self-nominate? although this is not final, it can give us a faster feedback than

Hi all Following today TSC call, here is my feedback on the topic. Today we do not have any certainty on the number of people who are interested to present themselves to joint the TSC, and moreover on