if you're thinking about doing this, a mod_perl 2.0 CPAN release might also be nice
What do you mean? It's been released every time a new version was announced. It's just invisible through indexer, because of the _09 segment. You can still get it from doug's CPAN dir.
sorry, I meant a new version of the 2.0 tree - meaning 1.99_09 or whatever it ends up being.
- that way you can have a PREREQ_PM mod_perl version that corresponds to an Apache::Test CPAN release, thus making third party modules (or said article :) that support mod_perl 1.99_09 capable of being used as examples of how Apache::Test works for both 2.0 and (if you want to get it from CPAN) 1.0. I don't mean to say that this will be required for each release, but we've come pretty far on third party module support recently so it would be nice to have them in sync once we settle down.
I plan to keep Apache::Test, distributed with mod_perl 2.0 as well as separately. I'm not sure what are asking for. Can you please explain?
what I meant is that when you release Apache::Test to CPAN as a separate module, that we also tag a new mod_perl 2.0 (well, 1.99) release candidate.
that way we can say "to use $x feature you need mod_perl 1.99_9 or Apache::Test 1.0." basically, 2.0 modules could then PREREQ_PM 1.99_09 and 1.0 modules could PREREQ_PM Apache::Test 1.0 but both would get the same feature support.
without a synchronous release (just this once, since third party module support has progressed very far) I fear that we'll be left saying "to use $x feature you need mod_perl from CVS or Apache::Test 1.0 from CPAN" or, perhaps worse, the other way around.
I understand that each mod_perl release will have the most current Apache::Test, but with recent changes (such as TEST_FILES support) it would be nice to have the two releases in sync.
besides, mod_perl 2.0 is ripe for a new release anyway :)
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
