Jon Atack

This PR doesn't affect anything yet; leaving it unmerged would only be blocking progress as it is needed for testing the next steps in the parent PR (and the parent...

> (I am not saying that we will or want to rename it, but will loose the option to do so in case we decide we want). If we release...

Updated per review feedback by @vasild and @mzumsande (make `-loglevel` a help-debug option, drop the release note, update the `-debug` and `-debugexclude` helps, reorganize commits logically). Verified that each commit...

One final push per `git range-diff a5d5569 ce3c4c9 9580480` (should be trivial to re-ACK) to ensure this pull changes no default behavior in any way for users or the tests/CI...

@vasild, @dunxen, @brunoerg, @w0xlt, @jarolrod, @mzumsande, @klementtan mind having a last look here?

> Given that this is primarily for devs, is there a reason to ship this in 24.0 this late before the feature freeze? (Sorry if this has been discussed before,...

15 accumulated ACKs but maintainers not in favor. Up for grabs.

Pushing this back needlessly only serves to stop momentum and discourage people from investing further time working on it or reviewing it. A lot of time and effort went into...

> which has been massaged to not actually change any behaviour. I think that was a needlessly negative comment. The changes were improvements, which is why I iterated on it,...

Work began on this on March 2 with #24464 and the goal was to have it done for v24. After an initial flurry, progress has been blocked at this step...