>> Given that this is so close to 5.6 release, we're not giving CPAN
>> authors time to clean up their POD before thousands of installations
>> start bitching about the warnings. I propose: make the warning
>> optional in 5.6; asking CPAN testers to test POD too; attempting to
>> make this POD change known to CPAN authors (through the modules list,
>> etc); and then make the warning mandatory in 5.7.
No matter what happens there, it seem to me that it would be a
useful thing for some makemakerish rule to *also* do this kind of
testing. The main problem is that it has to happen during development
by the author not after uploading or installation, and I don't know
how to go about sorting that. I suppose a 'make podlint' directive
might help, but I don't know how to get authors to run it, or
to tell the difference between an author and a user.
--tom
