Hello, everyone. The self-nomination period for the 2021 TSC Election of Active Community Members. If you are interested in self-nominated to serve the community as a member of the Technicael

Hi everyone, FYI I started this doodle to see which time suits best for a weekly/bi-weekly docs meeting: https://doodle.com/poll/dqk2pxn594f5cby8 BR/Luis

Hello TSC and all Gentle reminder Thanks

Hello OpenDaylight Community, Next TSC meeting is February 18, 2021 at 10 pm Pacific Time. The zoom session for the meeting is: https://zoom.us/j/657152618?pwd=cU9MR3daMkU5dnhaektTMkxXWEErUT09

Hi, In addition to the classical river names, Functest Kubernetes now delivers Docker tags per Kubernetes release. (Thank you for all the feedbacks, especially the last one from OOM PTL which

Hello TSC and all We are going to code freeze Silicon for all Managed Projects ( cut and lock release branches ) on Monday February 22nd Please remember that we only allow blocker bug fixes in

Hello TSC and all I have picked AR #270 so we can release Aluminium

Hi All, Just clarifying that if adding a date/number to the release name, that we would keep the periodic table element as well, e.g. "21.03 Silicon" or "Silicon 21.03". From a branding/marketing

Hello OpenDaylight Community, Next TSC meeting is February 11, 2021 at 9 am Pacific Time. The zoom session for the meeting is: https://zoom.us/j/219174946?pwd=aW9uSXl0KzJpcjRXY3l1bWIwdG9KZz09

Hi Luis Yes this means changing silicon to 21.03 but of course, we cans still use the silicon codename aside. There were talks on whether or not we should stick with the months for the second

Sorry I missed the discussion, what does it mean to move to Ubuntu style? changing silicon to 21.03? and what is the impact of changing this? BR/Luis

Hello OpenDaylight Community, Following our developper forum last week, the question of the release name has been raised by Robert. I've set up for a small confluence survey to get TSC opinion on

Hello again, sorry, for self-reply, but as it happens ... [snip] ... we just got hit by this. [snip] A case in

Hello, everyone. Prior to the recent TSC Election, the community elected to reform the TSC number of seats. The TSC voted to initiate an election to add Active Community Members to the TSC. The TSC

[+kernel-dev] Hey Venkat, Yeah... I wondered about that... see below. I suspected as much :) In that vein I went ahead and released both controller-3.0.6 and aaa-0.13.1. Given we are before branch

Ok :) So i can start with Aluminium SR3 ahead of schedule, if that's what's needed here...

Hello Anil, Understood. At the end of the day, though, we have only a few classes of jobs and there is a ton of commonalities between them. I do not believe this is the case for OpenDaylight jobs.

Greetings Robert: lf-env.sh: Creates a virtual env and sets up the environment, while the python-tools-install.sh Installs the python tools/utils during Job runtime. Since releng/global-jjb is a repo

We are not. We are picking candidates for SR3 -- and https://jenkins.opendaylight.org/releng/job/autorelease-release-aluminium-mvn35-openjdk11/360/ is good as any :) Regards, Robert

Thanks Luis. So we are not updating the downloads page for Aluminium SR2 right? we have release notes though