Re: Module Change Log

[Tux]

Some links:

• Advice on Changes
• CPAN::Changes
• CPAN::Changes::Spec
• Test::CPAN::Changes

And I fully support the previous answers: release a new version with an updated Changes/ChangeLog file. I *do* read it (if I use a modules/distribution).

FWIW my own release procedure checks if the ChangeLog has an entry less than 4 days ago. If not, it is most likely I forgot to add an entry.

[Bod]

Thanks for the links Tux - very helpful

How do you implement checking the age of the Change Log without manually copying a test file over which could also be forgotten?