On 06/20/2017 10:55 AM, Jim Jagielski wrote:
It's already in the wild.
We do not guarantee bug compatibility. That's our judgment call based on
adoption, expected user disruption, time in the wild, etc.
The purpose of my Showstopper was to revert to known-good behavior. That
didn't happen, not least because I didn't catch this bug in the
backport, I wanted to keep things moving, and I +1'd it despite the
presence of the rider patch that I tried unsuccessfully to keep out [1].
So that's on me (and that's why I'm grinding this particular axe). I
want to fix the mistake I started last year, and not punish our users
with yet another unusable default for the third release in a row.
--Jacob
[1]
https://lists.apache.org/thread.html/539645ba41021f85a87ad397861cb8d09fb057f7fb7e9ed768781e85@%3Cdev.httpd.apache.org%3E
