"Secretly, I'm hoping that Apache-Test becomes so popular that end-users start wrapping their bug reports up in little, self-contained, Apache-Test-based tarballs so anyone can reproduce the problem."
to that end, I've created a skeleton Apache-Test tarball (attached), complete with (very) basic instructions and pointers to additional documentation. just unzip and run, then tweak as necessary. lather, rinse, repeat.
Very nice! Though may I suggest to call it something different than bug? ;)
I was thinking that it could go in the utils/ directory in the mp2 distribution?
If it has to be bundled it should be bundled with Apache::Test, however since most people will get Apache::Test installed as rpm, it's probably the best to simply put it on CPAN.
I know we've discussed this before, buit I also think it's time to add a footer to the bottom of modperl@ with a link to bug reporting guidelines.
Good thinking Geoff! Sure, we can ask Ask to do that. However first we should probably make these links more intuitive, like:
http://perl.apache.org/bugs/
which will include a simple index.html pointing to the relevant mp1 and mp2 bug reporting instruction docs. I did add them to the ShortCuts menu, but personally I'd prefer to be able to quickly type them into the compose window, rather than going to perl.apache.org and copy-n-paste the long link.
From that page we could also link to perlbug and apache bug documents.
Now we could have a tail:
To report mod_perl bugs go to http://perl.apache.org/bugs/
__________________________________________________________________ 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]
