Re: [release] Sulfur code freeze

Daniel de la Rosa

On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@...> wrote:
On 21/03/2022 14:24, Robert Varga wrote:
> 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.

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 details are in

I expect to have that fixed today and finish the RESTCONF integration
tomorrow, so that the MRI bump should (fingers crossed) over the weekend.

It is way later than planned, expected or hoped, but unfortunately it is
what it is. There is silver lining here, though: this effort found two
bugs that have been squashed after lurking around for 7 years.

That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release 

I'll keep you posted,
Daniel de la Rosa
ODL Release Manager

Join to automatically receive all group messages.