My only gripe with the mp2
release candidates is that I would have liked to see a few production mp2 releases on CPAN before its mp1 indexing starts to disappear.
Sure, you can ask Andreas to not index mp2 and any other 3rd party modules. But why making mp2 users suffer?
I still can't understand the definition of 'a few production releases'. How will you know when it's OK to switch the direction of the blade and make the mp1 users suffer? Will you then go and notify the mp2 users: "we favor you now, please come back and use the CPAN tools" and notify the mp1 users: "excuse us, but mp1 was phased out, and we no longer support it via CPAN, so please find and download modules manually from now on"
Originally the _RC1 vs -RC1 was a slip, but I'm glad that it has happened earlier and not when 2.0.0 was released, since it has raised the problems earlier. And since we have mp2.0.0 scheduled for the beginning of January, that RC1 slip doesn't make much difference time-wise.
-- __________________________________________________________________ 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
-- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
