Am 15.03.2018 um 18:09 schrieb Eric Covener:
On Thu, Mar 15, 2018 at 12:54 PM, Jan Ehrhardt <[email protected]> wrote:
Eric Covener in gmane.comp.apache.devel (Thu, 15 Mar 2018 12:35:38
-0400):
+1, probably the least confusing, and Windows users aren't
quickly/casually picking up source releases.
Hmm. 2.4.32 coincided with the monthly Windows Update and with a curl
release. I upgraded everything yesterday...
Sorry -- I should have said "most/typical" Windows users.
The question now is about the pro/con of completely finalizing the
2.4.32 release or not -- either way even your upgrade already
happened.
Of course not catching the regression ahead of time is unfortunate.
The artefacts are on the mirrors and out in the wild, so we can not get
them back. Best is to soon proceed with the release and document the
mod_proxy_balancer on Windows regression in the announcement. At least
the symptoms described here are failure during start, so the bug does
not produce vague or rare symptoms. Any one updating and being hit by
the bug will notice immediately.
We can also add the patch to
http://www.apache.org/dist/httpd/patches/apply_to_2.4.32/ once it is
done, just in case a 2.4.33 takes a little longer for reasons not yet known.
About "not catching ahead of time": it would be great, if at least one
of us had a Windows system with the ability to run the test suite.
Regards,
Rainer
