Stas Bekman wrote:
Geoffrey Young wrote:
FYI...
I guess we need to consider how to handle 2.0 versus 2.2 stuff. things like auth providers bring with them new constants, header files, etc - stuff we will be expected to support going forward.
Frankly, I think we shouldn't spend a single moment on it at this point. For the same reason as we can't support 2.1 now.
well, I certainly wouldn't go that far. the moment the annoucement for 2.2 runs as
>> we'd recommend that 2.0 users migrate to 2.2 because it's >> 'stable' and has more feature, blah, blah, blah.
apache 2.0 will quickly become less significant.
in this case it's entirely possible that we simply drop support for 2.0 and move to support only 2.2, just like we dropped support for httpd < 2.0.46. If you think of 2.2 as of 2.0.50 or so, this makes total sense, given users are given enough time to do the transition to Apache 2.2.
Since this is an open source project you can certainly go ahead and start working on supporting 2.1 and 2.2 now. This unfortunately won't help making mp2.0 complete sooner for users that need it.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
