Re: [release] Sulfur code freeze
Robert Varga
On 28/03/2022 00:10, Robert Varga wrote:
1. old RESTCONF's URI parser leafref support. I think I can perform sufficient surgery to make this work without having to rewrite that thing (as was done for new RESTCONF, where this is a breeze)
2. two instances of a weird interaction with XML codec. It is not that weird, I understand what is going on, it just needs a bit of more work.
I will need another day to deal with them and, fingers crossed, UTs should agree.
Regards,
Robert
On 24/03/2022 01:24, Daniel de la Rosa wrote:Okay, so I am down to 3 call sites, which fall into two categories: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 amount of TLC, which I am not in position to give right now, sorry :(
On Wed, Mar 23, 2022 at 3:47 PM Robert Varga <nite@... <mailto:nite@...>> wrote:
That’s impressive. Ok thanks and it is all good. We will have a very solid sulfur release
1. old RESTCONF's URI parser leafref support. I think I can perform sufficient surgery to make this work without having to rewrite that thing (as was done for new RESTCONF, where this is a breeze)
2. two instances of a weird interaction with XML codec. It is not that weird, I understand what is going on, it just needs a bit of more work.
I will need another day to deal with them and, fingers crossed, UTs should agree.
Regards,
Robert