If you were on the docs-dev list, you'd see that the cron reports any problems, in case the committer didn't validate the docs before committing the change.ok, but what mod_perl functionality are we testing here?
only that the docs are up to snuff. I guess that there could be issues with pod2man if there is something awry. a derivitave of this test is something I now add to all my distributions :)
the docs are already tested by the perl.apache.org site's build tool.ok, I didn't know that.
OK, so how about making it optional. e.g. only if MOD_PERL_CHECK_PODS env var is turned on?I guess it could be more strict... we don't want the test suite report < 100% because some pod is imperfect.
we do, but end users probably don't :) that's why adding a pod tester is a good idea - it ensures that (if you follow good procedures and always make test before you release) that your pod isn't broken in a release.
Another drawback for having it on by default, is that it'll slowdown the test suite. Eventually there are going to be many pods!
__________________________________________________________________
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]
