Comment 4 for bug 1975399

Hi laszloj,

The server team discussed this bug today at our weekly meeting and considered between cherrypicking the specific fixes for this bug, vs. applying for a 'Micro-Release Exception' (MRE) for squid itself, which if accepted would allow backporting squid 5.5 itself, as Paride described. The trade-offs are that cherrypick type SRUs generally need a well-defined test case to reliably reproduce the bug. MRE SRUs don't require individual test cases for bugs, but the process to gain an MRE tends to take more time - and potentially a lot more time - but once accepted, subsequent micro-release updates go much more smoothly.

Since for this bug, we don't yet have a defined reproducer, and since it sounds like the fix involves multiple patches, the general consensus of the team was that we should probably focus our time towards getting the MRE application for squid. However, if you are able to figure out a reliable way to reproduce the bug synthetically, we can revisit that and try to get this specific fix SRU'd.

Some additional discussion about this: https://lists.ubuntu.com/archives/ubuntu-server/2022-June/009293.html