Olivier Dony (ODO)

Some of those changes are actually unnecessary for compatibility. Everything that has to do with newer DeprecationWarnings can be safely handled with an extra `filterwarnings()`. It's kind of the point:...

> override=ci/security > The code basically adapts existing use-cases for the new field types. @rco-odoo could we have a more extensive security review for sensitive changes like this? I see...

> Could be frustrating that the model you need is not listed for no good reason and you cannot do anything about that. I think that's fine, we'd just include...

> As it implies some code change and re-check about the functional usage I can implement that quick change if you like, so we don't end up leaving it as...

As this is an invasive core change, with a need for cross-team reviews, could we please have some more background info, purpose, rationale, design choices, etc? The current information in...

"No description provided" Anyway, there are tons of pricing details that aren't written down in contracts (starting with the prices!) and that's on purpose. Lots of things are standard practice...

> Hello @frfa1993 @odony :) I fixed the conflict in legal.rst (change to list-table), cleaned up a tiny bit the rst and fixed some headings anchors (ref links) > >...

I don't see any problem with the patch, but out of curiosity, have you been able to measure any kind of difference with this patch? How many open connections did...

Thanks!

> I'm guessing wildly, but what does `zpool get all [pool]` return for the pool(s) on one of those systems? One of the systems has this: ``` # zpool get...