Okay guys, here's the status. In about three hours, I have to head toward
BWI to catch a plane to Austin, TX. I'll be there attending NVIDIA-U for
the next 48 hours. [For those who didn't know, my research interest
focuses on 3D graphics.] I'm taking my notebook with me, but I don't know
how good my connectivity will be, if I even manage to get online at all.
Anyhow, that means I'm essentially going to have to put a 48-hour hold on
the release of 2.0.22-beta. (Frankly, I never expected you guys to +1 it
as fast as you did. =-) That's just as well, seeing as my message to
current-testers has not even gone out yet. (Can whoever is the moderator
of that list please see to it that my message gets approved ASAP?
Thanks.) I'd like to give the current-testers that 48 hours to bang on
the tarball in case there's something very important that we've missed.
I doubt there is anything--we've heard from just about all corners of the
world OS-wise and seem to be doing pretty well on everything except
Darwin. But if we're gonna do it we might as well get it right.
There are currently two problems with 2.0.22 that I kind of wish were
fixed but aren't: (1) there are build problems that could be easily fixed
to make Mac OS X/Darwin users' lives easier, (2) there are threaded MPM
problems still remaining, which we knew, though it now appears that the
worst of them could be easily fixed. Is the gethostbyname_r problem that
just got fixed in APR going to cause us headaches on the beta? If so,
make that (3). There are other issues that have already been fixed in CVS
since 2.0.22 as well, like exec cgi on Win32, though the ones above are
probably the highest up on the importance scale.
So here's what I propose: When I return in the wee hours of the morning
on Thursday, I'll get to work and catch up on my email if in fact I'm cut
off from the world for the next two days. If we haven't heard anything
bad from the current-testers and nobody on this list speaks up to the
contrary between now and then, I'll release 2.0.22 as beta first thing
Thursday morning. On the other hand, if we do hear about other problems
from the current-testers or fixes for any of the above mentioned problems
get committed and tested between now and Thursday [hint, hint], then I'll
scratch 2.0.22 and roll 2.0.23 and we'll try to expedite getting 2.0.23
out the door ASAP.
Does that sound like a plan?
--Cliff
--------------------------------------------------------------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
