You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Yann Ylavic <yl...@gmail.com> on 2018/03/15 16:34:02 UTC
Re: [RESULT] [VOTE] Release httpd-2.4.32
On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <DR...@primary.net> wrote:
>
> Personally, I would like to see *another* T&R (again, I volunteer and will
> see it through quickly) and no mention of this release be made public via
> ANNOUNCE.
> Thoughts?
I think we should complete this release, with a warning somewhere for
mod_proxy_lb users on Windows. It's mirrored already.
Then we can provide 2.4.33 shortly.
Regards,
Yann.
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Thu, Mar 15, 2018 at 4:43 PM, Yann Ylavic <yl...@gmail.com> wrote:
> On Thu, Mar 15, 2018 at 10:39 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote:
>> On Thu, Mar 15, 2018 at 4:28 PM, Eric Covener <co...@gmail.com> wrote:
>>>> This looks sensible, or do we say that users of mod_proxy_balancer
>>>> on Windows should defer their upgrade? A more limited audience?
>>>
>>> +1
>>
>> Should we also mention the regression against mod_security on Windows?
>> (Nobody can reproduce on Unix, correct?)
>
> This is not a regression, always been there (or almost) in 2.4.x.
Thanks for clarifying (not worthy of mention then)
>> What about the mod_md pegged infinite retry problem that was raised
>> a month or two back, particularly evident on Windows? Is the fact that
>> the module is experimental enough to evade mention in Announcement?
>
> We don't have much details on it yet, configuration issue?
I think we were waiting on json data, or Stefan has an inkling of how
we received negative delta now.
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Mar 15, 2018 at 10:39 PM, William A Rowe Jr <wr...@rowe-clan.net> wrote:
> On Thu, Mar 15, 2018 at 4:28 PM, Eric Covener <co...@gmail.com> wrote:
>>> This looks sensible, or do we say that users of mod_proxy_balancer
>>> on Windows should defer their upgrade? A more limited audience?
>>
>> +1
>
> Should we also mention the regression against mod_security on Windows?
> (Nobody can reproduce on Unix, correct?)
This is not a regression, always been there (or almost) in 2.4.x.
>
> What about the mod_md pegged infinite retry problem that was raised
> a month or two back, particularly evident on Windows? Is the fact that
> the module is experimental enough to evade mention in Announcement?
We don't have much details on it yet, configuration issue?
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Thu, Mar 15, 2018 at 4:28 PM, Eric Covener <co...@gmail.com> wrote:
>> This looks sensible, or do we say that users of mod_proxy_balancer
>> on Windows should defer their upgrade? A more limited audience?
>
> +1
Should we also mention the regression against mod_security on Windows?
(Nobody can reproduce on Unix, correct?)
What about the mod_md pegged infinite retry problem that was raised
a month or two back, particularly evident on Windows? Is the fact that
the module is experimental enough to evade mention in Announcement?
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Eric Covener <co...@gmail.com>.
> This looks sensible, or do we say that users of mod_proxy_balancer
> on Windows should defer their upgrade? A more limited audience?
+1
RE: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Daniel Ruggeri <DR...@primary.net>.
> -----Original Message-----
> From: William A Rowe Jr <wr...@rowe-clan.net>
> Sent: Thursday, March 15, 2018 4:28 PM
> To: httpd <de...@httpd.apache.org>
> Subject: Re: [RESULT] [VOTE] Release httpd-2.4.32
>
> On Thu, Mar 15, 2018 at 4:19 PM, Daniel Ruggeri <DR...@primary.net>
> wrote:
> >
> > *** Changes here
> > We consider this release to be the best version of Apache available for
> > non-Windows platforms, and encourage users of all prior versions to
> upgrade.
> >
> > Please note, a bug after shipping this release was discovered that
> prevents
> > the server from starting on Windows when mod_proxy_balancer is used.
> > This manifests in error message "AH01179: balancer slotmem_create
> failed."
> > Windows users are encouraged to postpone upgrades until the soon-to-
> be-available
> > 2.4.33+ release is made.
> > *** End Changes
>
> This looks sensible, or do we say that users of mod_proxy_balancer
> on Windows should defer their upgrade? A more limited audience?
>
Yes, definitely. Thanks for the pointer.
> > Please note that while the Apache HTTP Server Project may publish some
> > security patches to the 2.2.x flavor through at least December of 2017,
> > no further maintenance patches of 2.2.x will be considered and no further
> > releases will be distributed. The 2.2.x branch has now reached the end of
> > its maintenance, and users are strongly encouraged to promptly complete
> > their transitions to this 2.4.x flavor of httpd to benefit from security
> > and bug fixes, as well as new features.
>
> This is not current, see /repos/dist/dev/httpd/ for the current
> Announcement
> text draft, please.
Right. I'll use that one.
--
Daniel Ruggeri
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Thu, Mar 15, 2018 at 4:19 PM, Daniel Ruggeri <DR...@primary.net> wrote:
>
> *** Changes here
> We consider this release to be the best version of Apache available for
> non-Windows platforms, and encourage users of all prior versions to upgrade.
>
> Please note, a bug after shipping this release was discovered that prevents
> the server from starting on Windows when mod_proxy_balancer is used.
> This manifests in error message "AH01179: balancer slotmem_create failed."
> Windows users are encouraged to postpone upgrades until the soon-to-be-available
> 2.4.33+ release is made.
> *** End Changes
This looks sensible, or do we say that users of mod_proxy_balancer
on Windows should defer their upgrade? A more limited audience?
> Please note that while the Apache HTTP Server Project may publish some
> security patches to the 2.2.x flavor through at least December of 2017,
> no further maintenance patches of 2.2.x will be considered and no further
> releases will be distributed. The 2.2.x branch has now reached the end of
> its maintenance, and users are strongly encouraged to promptly complete
> their transitions to this 2.4.x flavor of httpd to benefit from security
> and bug fixes, as well as new features.
This is not current, see /repos/dist/dev/httpd/ for the current Announcement
text draft, please.
RE: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Daniel Ruggeri <DR...@primary.net>.
> -----Original Message-----
> From: Rainer Jung <ra...@kippdata.de>
> Sent: Thursday, March 15, 2018 12:09 PM
> To: dev@httpd.apache.org
> Subject: Re: [RESULT] [VOTE] Release httpd-2.4.32
>
> Am 15.03.2018 um 17:34 schrieb Yann Ylavic:
> > On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <DR...@primary.net>
> wrote:
> >>
> >> Personally, I would like to see *another* T&R (again, I volunteer and will
> >> see it through quickly) and no mention of this release be made public via
> >> ANNOUNCE.
> >> Thoughts?
> >
> > I think we should complete this release, with a warning somewhere for
> > mod_proxy_lb users on Windows. It's mirrored already.
> > Then we can provide 2.4.33 shortly.
>
> +1 and s/mod_proxy_lb/mod_proxy_balancer/
>
> Rainer
Agreed - once the mirrors have it... it's in the wild. I've been occupied the past few hours and have been mulling over this. WDYT about this verbiage? I'm poised and ready to send this and will do so in the next few hours if no additional feedback is given.
Apache HTTP Server 2.4.32 Released
March 15, 2018
The Apache Software Foundation and the Apache HTTP Server Project
are pleased to announce the release of version 2.4.32 of the Apache
HTTP Server ("Apache"). This version of Apache is our latest GA
release of the new generation 2.4.x branch of Apache HTTPD and
represents fifteen years of innovation by the project, and is
recommended over all previous releases. This release of Apache is
a security, feature, and bug fix release.
*** Changes here
We consider this release to be the best version of Apache available for
non-Windows platforms, and encourage users of all prior versions to upgrade.
Please note, a bug after shipping this release was discovered that prevents
the server from starting on Windows when mod_proxy_balancer is used.
This manifests in error message "AH01179: balancer slotmem_create failed."
Windows users are encouraged to postpone upgrades until the soon-to-be-available
2.4.33+ release is made.
*** End Changes
Apache HTTP Server 2.4.32 is available for download from:
http://httpd.apache.org/download.cgi
Apache 2.4 offers numerous enhancements, improvements, and performance
boosts over the 2.2 codebase. For an overview of new features
introduced since 2.4 please see:
http://httpd.apache.org/docs/trunk/new_features_2_4.html
Please see the CHANGES_2.4 file, linked from the download page, for a
full list of changes. A condensed list, CHANGES_2.4.32 includes only
those changes introduced since the prior 2.4 release. A summary of all
of the security vulnerabilities addressed in this and earlier releases
is available:
http://httpd.apache.org/security/vulnerabilities_24.html
This release requires the Apache Portable Runtime (APR), minimum
version 1.5.x, and APR-Util, minimum version 1.5.x. Some features may
require the 1.6.x version of both APR and APR-Util. The APR libraries
must be upgraded for all features of httpd to operate correctly.
This release builds on and extends the Apache 2.2 API. Modules written
for Apache 2.2 will need to be recompiled in order to run with Apache
2.4, and require minimal or no source code changes.
http://svn.apache.org/repos/asf/httpd/httpd/trunk/VERSIONING
When upgrading or installing this version of Apache, please bear in mind
that if you intend to use Apache with one of the threaded MPMs (other
than the Prefork MPM), you must ensure that any modules you will be
using (and the libraries they depend on) are thread-safe.
Please note that while the Apache HTTP Server Project may publish some
security patches to the 2.2.x flavor through at least December of 2017,
no further maintenance patches of 2.2.x will be considered and no further
releases will be distributed. The 2.2.x branch has now reached the end of
its maintenance, and users are strongly encouraged to promptly complete
their transitions to this 2.4.x flavor of httpd to benefit from security
and bug fixes, as well as new features.
--
Daniel Ruggeri
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Rainer Jung <ra...@kippdata.de>.
Am 15.03.2018 um 17:34 schrieb Yann Ylavic:
> On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <DR...@primary.net> wrote:
>>
>> Personally, I would like to see *another* T&R (again, I volunteer and will
>> see it through quickly) and no mention of this release be made public via
>> ANNOUNCE.
>> Thoughts?
>
> I think we should complete this release, with a warning somewhere for
> mod_proxy_lb users on Windows. It's mirrored already.
> Then we can provide 2.4.33 shortly.
+1 and s/mod_proxy_lb/mod_proxy_balancer/
Rainer
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
Reading backwards... +1 - deferring the announcement would be fine.
We simply can't make 2.4.32 "disappear" as unreleased.
On Fri, Mar 16, 2018 at 8:03 AM, Jim Jagielski <ji...@jagunet.com> wrote:
> Just because it is released, doesn't mean we need to announce it. We
> can easily release a quick 2.4.33 and announce *that*. 2.4.32 was/is
> just an un-announced release.
>
>> On Mar 15, 2018, at 2:51 PM, Christophe Jaillet <ch...@wanadoo.fr> wrote:
>>
>> Le 15/03/2018 à 17:34, Yann Ylavic a écrit :
>>> On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <DR...@primary.net> wrote:
>>>>
>>>> Personally, I would like to see *another* T&R (again, I volunteer and will
>>>> see it through quickly) and no mention of this release be made public via
>>>> ANNOUNCE.
>>>> Thoughts?
>>> I think we should complete this release, with a warning somewhere for
>>> mod_proxy_lb users on Windows. It's mirrored already.
>>> Then we can provide 2.4.33 shortly.
>>> Regards,
>>> Yann.
>>
>> +1 as well for me.
>> It's unfortunate but the release has been voted and is in the wild now.
>> The best is to mitigate the announce as proposed by Yann and release a 2.4.n+1 ASAP.
>>
>> CJ
>>
>
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Daniel Ruggeri <dr...@primary.net>.
On 2018-03-16 08:03, Jim Jagielski wrote:
> Just because it is released, doesn't mean we need to announce it. We
> can easily release a quick 2.4.33 and announce *that*. 2.4.32 was/is
> just an un-announced release.
>
Personally, I prefer this approach. I've been holding off on sending the
announcement as noted on private@, but I think I'd sooner T&R 2.4.33 and
get ready for that one to go out.
Again, I volunteer... assuming y'all haven't come to the opinion that
I'm cursed as an RM.
--
Daniel Ruggeri
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Jim Jagielski <ji...@jaguNET.com>.
Just because it is released, doesn't mean we need to announce it. We
can easily release a quick 2.4.33 and announce *that*. 2.4.32 was/is
just an un-announced release.
> On Mar 15, 2018, at 2:51 PM, Christophe Jaillet <ch...@wanadoo.fr> wrote:
>
> Le 15/03/2018 à 17:34, Yann Ylavic a écrit :
>> On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <DR...@primary.net> wrote:
>>>
>>> Personally, I would like to see *another* T&R (again, I volunteer and will
>>> see it through quickly) and no mention of this release be made public via
>>> ANNOUNCE.
>>> Thoughts?
>> I think we should complete this release, with a warning somewhere for
>> mod_proxy_lb users on Windows. It's mirrored already.
>> Then we can provide 2.4.33 shortly.
>> Regards,
>> Yann.
>
> +1 as well for me.
> It's unfortunate but the release has been voted and is in the wild now.
> The best is to mitigate the announce as proposed by Yann and release a 2.4.n+1 ASAP.
>
> CJ
>
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Christophe Jaillet <ch...@wanadoo.fr>.
Le 15/03/2018 à 17:34, Yann Ylavic a écrit :
> On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <DR...@primary.net> wrote:
>>
>> Personally, I would like to see *another* T&R (again, I volunteer and will
>> see it through quickly) and no mention of this release be made public via
>> ANNOUNCE.
>> Thoughts?
>
> I think we should complete this release, with a warning somewhere for
> mod_proxy_lb users on Windows. It's mirrored already.
> Then we can provide 2.4.33 shortly.
>
>
> Regards,
> Yann.
>
+1 as well for me.
It's unfortunate but the release has been voted and is in the wild now.
The best is to mitigate the announce as proposed by Yann and release a
2.4.n+1 ASAP.
CJ
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Jan Ehrhardt <ph...@ehrhardt.nl>.
William A Rowe Jr in gmane.comp.apache.devel (Fri, 16 Mar 2018 00:17:45
-0500):
>That still leaves the headache of fallback-to-release when a candidate on
>these many projects isn't present (actually, the smart election between
>candidate and release if both exist!) But great pointer, TY!
The list of pre-installed software on Appveyor images is impressive:
https://www.appveyor.com/docs/build-environment/#pre-installed-software
At first sight omly nasm, awk and unxutils are missing. You could make
appveyor download them or just make them part of your github repo (like
https://github.com/mgreter/libsass-msi-installer/tree/master/tools )
--
Jan
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
That still leaves the headache of fallback-to-release when a candidate on
these many projects isn't present (actually, the smart election between
candidate and release if both exist!) But great pointer, TY!
On Mar 15, 2018 21:46, "Jan Ehrhardt" <ph...@ehrhardt.nl> wrote:
> William A Rowe Jr in gmane.comp.apache.devel (Thu, 15 Mar 2018 16:11:10
> -0500):
> >https://github.com/appsuite/oss-httpd-build is where this all lives, and
> is
> >where the localized PERL5LIB schema for all the components will land.
> >This can be further streamlined, and the really big caveat is that the
> gather
> >phase requires bash on Windows (SFU makes this trivial.)
>
> bash is standard installed on Appveyor images, as part of Windows GIT.
> See
> https://github.com/ImageMagick/ImageMagick-Windows/blob/master/
> CloneRepositories.cmd#L12
>
> This just executes
> https://github.com/ImageMagick/ImageMagick-Windows/blob/master/
> CloneRepositories.sh
> --
> Jan
>
>
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Jan Ehrhardt <ph...@ehrhardt.nl>.
William A Rowe Jr in gmane.comp.apache.devel (Thu, 15 Mar 2018 16:11:10
-0500):
>https://github.com/appsuite/oss-httpd-build is where this all lives, and is
>where the localized PERL5LIB schema for all the components will land.
>This can be further streamlined, and the really big caveat is that the gather
>phase requires bash on Windows (SFU makes this trivial.)
bash is standard installed on Appveyor images, as part of Windows GIT.
See
https://github.com/ImageMagick/ImageMagick-Windows/blob/master/CloneRepositories.cmd#L12
This just executes
https://github.com/ImageMagick/ImageMagick-Windows/blob/master/CloneRepositories.sh
--
Jan
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Thu, Mar 15, 2018 at 3:59 PM, Jan Ehrhardt <ph...@ehrhardt.nl> wrote:
> William A Rowe Jr in gmane.comp.apache.devel (Thu, 15 Mar 2018 13:52:48
> -0500):
>>The largest headache is provisioning the entire suite of non-default perl
>>modules required. Running the framework is trivial. I've been working on
>>some workaround to this for unix and windows for "stock" test boxes.
>
> Any chance to make this publicly available? To give you an idea,
> ImageMagick does a fairly standard Perl install on Appveyor:
> https://github.com/ImageMagick/ImageMagick-Windows/blob/master/AppVeyor/Install.cmd#L37
> They are downloading
> https://github.com/ImageMagick/ImageMagick-Windows/releases/download/20160630/strawberry-perl-5.20.1.1-64bit.msi
Yes, but the perl logic isn't done yet. Even the OpenSSL project refused
to support RedHat/CentOS without perl-core extensions installed (or alert
to their absence.) Seems perl test logic authors are traditionally and
continuously obtuse to their test suites' pain points.
https://github.com/appsuite/oss-httpd-build is where this all lives, and is
where the localized PERL5LIB schema for all the components will land.
This can be further streamlined, and the really big caveat is that the gather
phase requires bash on Windows (SFU makes this trivial.) I've given up on
extending makefile syntax, and looking at a python (or perl) script to deal
with both the Windows native checkout, and conditional BLD=candidate
flavor, because various bits will or will not have a pending release when
combining those packages, and that's something nmake, and even gmake
won't support trivially.
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Jan Ehrhardt <ph...@ehrhardt.nl>.
William A Rowe Jr in gmane.comp.apache.devel (Thu, 15 Mar 2018 13:52:48
-0500):
>The largest headache is provisioning the entire suite of non-default perl
>modules required. Running the framework is trivial. I've been working on
>some workaround to this for unix and windows for "stock" test boxes.
Any chance to make this publicly available? To give you an idea,
ImageMagick does a fairly standard Perl install on Appveyor:
https://github.com/ImageMagick/ImageMagick-Windows/blob/master/AppVeyor/Install.cmd#L37
They are downloading
https://github.com/ImageMagick/ImageMagick-Windows/releases/download/20160630/strawberry-perl-5.20.1.1-64bit.msi
And install it, using chocolatey
https://github.com/ImageMagick/ImageMagick-Windows/blob/master/AppVeyor/Install-StrawberryPerl-x64.ps1#L1
Could something like this be extended to install the non-standard
modules as well? If this is not possible using the msi-installer, would
a self-extracting exe be another way?
>With that resolved, just about anyone in the windows community should
>easily build and test when they will, against release, candidate, snapshot
>or bleed.
--
Jan
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Jan Ehrhardt <ph...@ehrhardt.nl>.
Rainer Jung in gmane.comp.apache.devel (Thu, 15 Mar 2018 18:15:13
+0100):
>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.
+1
>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.
Something that crosses my mind from time to time: appveyor.com is free
for open source projects. PHP uses it for running the test suite:
https://ci.appveyor.com/project/php/php-src/build/master.build.6478/job/ios1a5p0vjuqkmik#L5609
Libexpat does the same:
https://ci.appveyor.com/project/libexpat/libexpat/build/libexpat-131
In these test they are building Debug\expatd.dll and running the tests
in Debug mode, but with some adjustments a static release\expat.lib can
also be built:
https://ci.appveyor.com/project/Jan-E/libexpat/build/libexpat-10/job/e98ai0uf5wu5vmde#L269
Complex projects with a lot of dependencies are no problem as well. See
for instance the build log of ImageMagick for Windows:
https://ci.appveyor.com/project/Jan-E/imagemagick-windows/build/job/ef3gvikn64m6ddoo?fullLog=true
In theory, httpd and all of its dependencies could be built as well on a
Appveyor virtual Windows machine. I do not have the time to do that
right now, but if anyone feels inclined...
--
Jan
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by William A Rowe Jr <wr...@rowe-clan.net>.
On Thu, Mar 15, 2018 at 12:15 PM, Rainer Jung <ra...@kippdata.de> wrote:
> Am 15.03.2018 um 18:09 schrieb Eric Covener:
>>
>> On Thu, Mar 15, 2018 at 12:54 PM, Jan Ehrhardt <ph...@ehrhardt.nl> 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.
+1 (actually, no choice to continue to "publish"; the announcement could be
held back if we were rolling and voting up a 2.4.33 release right now, but we
do not "withdraw" a published (mirrored) release.
> 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.
+1
> 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.
The largest headache is provisioning the entire suite of non-default perl
modules required. Running the framework is trivial. I've been working on
some workaround to this for unix and windows for "stock" test boxes.
With that resolved, just about anyone in the windows community should
easily build and test when they will, against release, candidate, snapshot
or bleed.
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Rainer Jung <ra...@kippdata.de>.
Am 15.03.2018 um 18:09 schrieb Eric Covener:
> On Thu, Mar 15, 2018 at 12:54 PM, Jan Ehrhardt <ph...@ehrhardt.nl> 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
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Eric Covener <co...@gmail.com>.
On Thu, Mar 15, 2018 at 12:54 PM, Jan Ehrhardt <ph...@ehrhardt.nl> 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.
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Yann Ylavic <yl...@gmail.com>.
On Thu, Mar 15, 2018 at 5:54 PM, Jan Ehrhardt <ph...@ehrhardt.nl> 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...
There is no (known) issue if mod_proxy_loadbalancer is not involved, is it?
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Jan Ehrhardt <ph...@ehrhardt.nl>.
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...
--
Jan
Re: [RESULT] [VOTE] Release httpd-2.4.32
Posted by Eric Covener <co...@gmail.com>.
On Thu, Mar 15, 2018 at 12:34 PM, Yann Ylavic <yl...@gmail.com> wrote:
> On Thu, Mar 15, 2018 at 5:20 PM, Daniel Ruggeri <DR...@primary.net> wrote:
>>
>> Personally, I would like to see *another* T&R (again, I volunteer and will
>> see it through quickly) and no mention of this release be made public via
>> ANNOUNCE.
>> Thoughts?
>
> I think we should complete this release, with a warning somewhere for
> mod_proxy_lb users on Windows. It's mirrored already.
> Then we can provide 2.4.33 shortly.
+1, probably the least confusing, and Windows users aren't
quickly/casually picking up source releases.