We discussed all this when 2.0 was first released- we should track the httpd API as faithfully as possible, and perhaps bump to 2.4.x when we need to break back-compat with the 2.0.x line.
CPAN can't support both lines so we're stuck going with thelatest version whenever we drop stuff on CPAN. IOW we don't need to rush to support 2.4 as it will introduce pain for existing users. Aim for another 3-6 months min before we start targetting that platform is what I suggest. ----- Original Message ----- > From: Torsten Förtsch <torsten.foert...@gmx.net> > To: dev@perl.apache.org > Cc: Fred Moyer <f...@redhotpenguin.com> > Sent: Tuesday, April 10, 2012 2:37 PM > Subject: Re: [RELEASE CANDIDATE]: mod_perl-2.0.6 RC3 > > On Tuesday, 10 April 2012 10:28:53 Fred Moyer wrote: >> Guessing this is a 2.0.7 fix? Or would it need to be 2.4.0? > > What are the requirements for one or the other? I think a modperl that > supports httpd 2.4 will not be completely backwards compatible. > > However, this is a subject for discussion. Should it be as backwards > compatible as possible? I don't think so. Modperl is a layer that exposes > the > httpd API more or less for Perl users. If that API changes we should adopt > these changes. But perhaps we should have a modperl for httpd 2.2 and another > one for 2.4. > > A minor question is should we bind our version numbering to that of httpd? > > Torsten Förtsch > > -- > Need professional modperl support? Hire me! (http://foertsch.name) > > Like fantasy? http://kabatinte.net > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org > For additional commands, e-mail: dev-h...@perl.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@perl.apache.org For additional commands, e-mail: dev-h...@perl.apache.org
