I don't see stable/aluminum branches in the projects yet. I thought we were doing branch cutting now too? I'm not sure what branch was locked but if no projects have stable/aluminum branches I'm not s

No, autorelease jobs were designed to be independent of any merge jobs. Regards, Thanh

So 3 times in a row in the same spot: https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/autorelease-release-magnesium-mvn35-openjdk11/335/error.log.gz I don't think this is an intermittent is

I forced another build to go so let's see if it fails again. However the last 2 of the failures were the same Controller Toaster test maybe we're really unlucky with an intermittent test failure in th

I took care of the RELENG and Documentation project landing pages. Many of the old links from these landing pages are out of date and up-to-date info is in docs.opendaylight.org so I didn't migrate an

I can't speak to the netvirt jobs however ... We've removed all the centos7-autorelease-* VMs, they used to be a special VM that had special packages on them to work with autorelease builds, however w

When I drill down to the jszip violation in Nexus IQ and then choose the "POLICY" tab. I am able to click "Waive" as an option. After filling out all the details though it rejects saying I do not have

I had not opened one yet as I was still investigating the specifics. Since my last email though I have resolved the build failures with the distribution project (fail was due to building against Java

There is a way we can get pretty close to a release report by using the relevant release branch CLM report from the distribution project as that is a scan that includes all projects that participated

Thought I'd note that the Docs project has officially branched stable/magnesium at this point so please submit release notes to the stable/magnesium branch. Master branch has been bumped to aluminum.

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 for

The concerning thing here for me is LF deployed a new release process requiring someone or group of people to analyse and provide a security waiver to projects before allowing the project to be releas

Hi All, They will need to bump and release 0.4.3. There is no way to back out of a release. Especially considering that it's been deployed to Maven Central at this point: https://mvnrepository.com/art

Sorry I dropped the ball on helping out with this one. As of this morning it looks like Sodium has converged and I believe master as well. Are we all set at this point? I did not catch any patches for

Hi Eric, I recall the old sonar system has the "ODL Sonar Way" or something profile. Can we not redo that profile in SonarCloud? I believe that profile was crafted by the community over the years of u

+1 I think this makes a lot of sense. +1 +1 Agreed. Thanh

Congrats everyone! Cheers, Thanh

+1 Thanh

+1 Thanh

+1 for Option 1 Regards, Thanh