Not really of my concern.
I want to give attention to
http://bahumbug.wordpress.com/2007/09/07/apache-226/
May be agood time to reconsider the depency for example with APR.
Steffen
----- Original Message -----
From: "Steffen" <[EMAIL PROTECTED]>
To: <dev@httpd.apache.org>
Sent: Wednesday, 26 September, 2007 21:05
Subject: Re: 2.2.7
There is the ASF statement/promise:
"Modules compiled for Apache 2.2 should continue to work for all 2.2.x
releases."
So I expect that modules have *not* to be new compiled. It is quite
confusing for our users en authors have to maintain in most
cases up to 4 versions. What about the Magic Number ?
Btw.
I guess (when I see the downloads) already a few thousands (production)
sites are running the 2.2.6 version from the ApacheLounge*. Not a single
problem report received, all running well including mod_perl and other
mods
which are failing with the ASF build.
So for this moment the Windows Community has no need to hurry a new 2.2.7.
We are also a little afraid that same things can happen as with the
unusually closely 2.2.5==>2.2.6 process, a broken build.
Steffen
www.apachelounge.com
*not affiliated with the Apache Software Foundation or with the Apache
HTTP
Server Project
----- Original Message -----
From: "William A. Rowe, Jr." <[EMAIL PROTECTED]>
To: <dev@httpd.apache.org>
Sent: Wednesday, 26 September, 2007 18:50
Subject: Re: 2.2.7
Jim Jagielski wrote:
I'd like for us to consider a release of 2.2.7 in October
to address the Windows file handle issues as well
some other fixes that would be useful to get out quickly...
How about 2 :)
I expect to have Windows fixes ready to backport next week after
the perlfolk confirm my suggested fixes for pseudo-standard I/O :)
So it was my hope to release APR 1.2.12 quite quickly (no apr-util
expected but that doesn't mean it wouldn't see some improvements
that merit a release), and httpd 2.2.7 promptly. I've been shrinking
patches to the minimum LoC to change/review/release and will commit
today.
I'd love to see another 2.2.8 with more bug fixes late in October
or very early November, so that it's the 'best version available'
and there would be very little push to make 2.2 better, but shift
a bunch of energy to getting somewhere towards 2.4.x or hacking on
the Amsterdam branch during our ApacheCon month.
Bill
