Hello As discussed during the TSC meeting of 7th July, I'd like to challenge the relevancy of branch locks during releases processes. In my opinion they have more cons than pros today. I agree they

Alright, so now we are in business, we have https://jenkins.opendaylight.org/releng/job/integration-distribution-test-chlorine/90/ going. It seems all tests are currently failing due to being run

Hello Guillaume and all, Ok I have already announced the code freeze for Sulfur SR2 but we can review the process at the next TSC meeting. BTW, I'm on vacation this week so I won't be able to attend

Hello TSC and all We are going to code freeze Sulfur for all Managed Projects ( cut and lock release branches ) on Monday August 15th 2022 at 10 am UTC Please remember that we only allow blocker bug

Hi Rohini, Sorry, got pulled into other things. For this issue, we were wondering if it's related to ODL deployed using Helm charts, considering that the problem is also reproducible when ODL is

Great initiative, Filip! It will certainly provide some initial indication of how the community is using ODL. We usually use SurveyMonkey to conduct such surveys. Cheers! Pano

Hi Daniel You are right. For the moment, I assume that we can still process as before once again. Bacuase we didn't close the debate about this point. I still have to send an email with more details

Done, managed distribution is out there and it shrunk by ~8MiB, which is good news. Done, we have AR working here:

Hello Guillaume and all, I just remembered that we wanted to shorten the code freeze for new releases, as it is documented in our TSC meeting minutes from July 7th. So based on this, when do we want

Hi TSC, (+ Pano on CC) as discussed on the last meeting, I would like to propose a survey for OpenDaylight users, in order to get a better angle on our community and users of OpenDaylight. Feel free

All this has been completed and the MSI projects have been updated. Unfortunately there are three more things blocking autorelease: - int/dist's master needs to be built with Java 17 - we need a

Hello OpenDaylight Community, The next TSC meeting is August 4, 2022 at 10 pm Pacific Time. As usual, the agenda proposal and the connection details for this meeting are available in the wiki at

Hello, Did you get a chance to look in to the configurations shared. Thanks & Regards, Rohini Cell: +91.9995241298 | VoIP: +91.471.3025332

+1 On Wed, Aug 3, 2022 at 1:43 AM Guillaume Lambert via lists.opendaylight.org <guillaume.lambert=orange.com@...> wrote:

Hi TSC, the beta version of the website transformation, from WordPress to Jekyll, is prepared for a wider demonstration towards you. Repository on GitHub with a README. It is missing some sort of

Hello all Gilles, I understand you need a formal approval of the TSC to proceed with LFIT. So I just created a poll at this URL https://wiki.opendaylight.org/x/MAGdAQ Please TSC members, can you

Dear TSC members, During the TSC meeting of June 30, Guillaume Lambert briefly presented to you our proposal to make TransportPCE project structure evolve. The purpose of this email is to

Hello Rahul, Please find the answers below: Official Helm chart @ODL Helm Chart . Attaching the values.yml for reference Fix was to restart the Owner Supervisor on failure . Check-in

Thanks. We have already tested CONTROLLER-2035 with Phosphorous SR2(created a patch with the fix) and the issue still persists when we do multiple restarts of the master node(approx. after 10th

Hi Anil, Thanks for the response. Please find the details below: 1. Is the Test deployment using our Helm charts (ODL Helm Chart)? – We have created our own helm chart for