> Nope, I haven't run smoke against 5.6.x for quite some time. I think > since 1.99_14 was released.
I think it is time we re-evaluated support for 5.6.x. I would suggest we drop support for the 5.6 branch entirely. here is why: - we spend lots of time on threads and require 5.8.x thread foo. saying "5.6.x for prefork and 5.8.x for threads" is really just setting us up for lots of problem reports for when people fiddle with the mpm post compilation. everyone knows it is possible to compile with both mpms and choose after the fact, right? - our resources are limited. with just the handful of us being active it is practically impossible to keep up with all the generations of httpd and perl. supporting just the 5.8.x tree alone is about to give us _5_ different versions of perl to accommodate internally with the impending release of 5.8.5. - we are still not at 2.0 yet, so now is the time to drop support for older versions, not after we move to 2.0 and find it is just a pain to support 5.6.x. personally, I am just fine with leaving 5.6.x behind. who among us even runs 5.6? by this I mean that, as developers, it is impractical to say we support a perl version that none of us even tests against on a semi-regular basis, especially one that is as old (both in age and in version) as 5.6.1 is. we are but a few, and we do our best to make everyone happy, but the reality is that we can't handle everything, and I would rather see resources go toward cool things like separating APR and integrating new httpd 2.2 features when it arrives over supporting older httpd or perl versions. --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
