Re: [release] Sulfur code freeze


Robert Varga
 

On 20/03/2022 19:50, Robert Varga wrote:
On 19/03/2022 16:37, Daniel de la Rosa wrote:

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


It looks like all issues have been resolved. So are we ready to pick the next AR as RC?
I am still working through netconf/bgpcep, plus the bump to MSI projects. I'll keep you posted.
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 naive.

serviceutils is also ready to integrate, but there's a problem needing action in global-jjb: javadocs jobs are using mvn35 and thus end up exploding like here: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/32/

Even when we tell the job to use mvn38, it will unpack the correct maven, but will attempt to use mvn35: https://jenkins.opendaylight.org/releng/job/serviceutils-maven-javadoc-verify-sulfur-openjdk11/33/console

Regards,
Robert

Join TSC@lists.opendaylight.org to automatically receive all group messages.