Yes, I think most of the issues are already fixed, but I am waiting for https://jira.linuxfoundation.org/plugins/servlet/theme/portal/2/IT-23826 to issue the corresponding releases. With the upgrade g

So looking at https://jenkins.opendaylight.org/releng/job/integration-distribution-test-sulfur/185/ we have plenty of badness. The core problem is that a ton of test suites are depending on OPERATIONA

Alright, everything has been merged up. int/dist and autorelease need to have their jobs updated to use maven-3.8, please review the patches here: https://git.opendaylight.org/gerrit/c/releng/builder/

This is now cleared, netconf-3.0.0 is out there. Most of the MSI update patches are done -- except openflowplugin. Upgraded spotbugs is finding some badness which was introduced in https://git.openday

Okay, so I am down to 3 call sites, which fall into two categories: 1. old RESTCONF's URI parser leafref support. I think I can perform sufficient surgery to make this work without having to rewrite t

A quick update here. We are on the home stretch now, with 31 callsites still being bad. About a third are duplicate (e.g. they are the same weirdness across bierman20/rfc8040). They will need some amo

So fixing RESTCONF here is going to require a yangtools-8.0.2 release. The problem is that we lost a DataSchemaContextTree capability which was provided indirectly via SchemaNode.getPath() -- the deta

Alright, anyway it's going to take a couple of days to sort out the RESTCONF stuff, so that (and the javadoc jobs) are the real blockers. Regards, Robert

bgpcep is ready for integration, but netconf is not -- as it turns the vast majority of patches dealing with SchemaNode.getPath() caller removal had to be reverted because ... let's say they were naiv

I am still working through netconf/bgpcep, plus the bump to MSI projects. I'll keep you posted. Regards, Robert

Alright, so MDSAL-731 is fixed and it makes MDSAL-735 more diagnosable -- I plan to squash that today. Regards, Robert

Hello Daniel, Yes, unfortunately and I am still struggling with the fix, it turns out to be more complicated than expected, but I am converging on a solution. Regards, Robert

No objections received up until now (~2 months after the dealine), this is the official plan of action. Regards, Robert

Ah, this is nice, but could you adjust the first column to contain links to Release Process requirements? that will make it easier for people unfamiliar with it to understand what means what. From a q

so a day has passed, I am up for an update: - there was a regression (YANGTOOLS-1407) detected in lispflow integration, that is taken care of - https://git.opendaylight.org/gerrit/q/topic:sulfur-mri i

From MRI perspective, we are ... 5? ... months behind the schedule. The good news is that MDSAL-696, which was blocking yangtools-8 -> mdsal-9 integration is done and dusted. Next steps are to integra

Congrats as well. Actually no ticket is needed -- just update this file: https://github.com/opendaylight/integration-test/blob/master/INFO.yaml and the rights should become effective pretty much immed

So it looks much better already: https://jenkins.opendaylight.org/releng/job/integration-distribution-test-phosphorus/315/ So this is failing across branches and the reason is that for some reason the

Hello Daniel, everyone, Right, that's because I finished updating stable/phosphorus a couple of minutes ago :) AR #360 and CSIT #315 should have these integrated. As for odltools -- it started failing

I think this fix is ready, I am rolling it out now. I think these are different, where CONTROLLER-2025 should help, but I am not sure to what extent. Regards, Robert