bricas / cpan-changes-web Goto Github PK

Currently the feed code uses the results from the full changelog parsing. If the changelog doesn't fully validate, instead of just showing an error message, we could do the following:

• Only use the latest changelog data. If valid, this would be useful in the feed
• Use a plain diff from the last copy of the changelog to get at least get some data

http://changes.cpanhq.org/author/BBYRD
https://metacpan.org/source/BBYRD/Dist-Zilla-PluginBundle-Author-BBYRD-0.93/CHANGES

A simple matter of uppercasing seems to foobar everything. I think most of the DZIL distros call the file "CHANGES".

Looking at http://changes.cpanhq.org/author/TOBYINK there are some random duplicate entries. See, for example:

• Module-Package-RDF
• RDF-Crypt
• RDF-RDFa-Parser
• Syntax-Collector
• Web-Magic

This is especially true for changelogs. Example:

http://changes.cpanhq.org/dist/Data-Dumper-GUI/0.005

http://changes.cpanhq.org/dist/Test-Aggregate/0.369

shows:

ERROR: Changelog release date (Not Released) does not look like a W3CDTF

When Test::CPAN::Changes passes:

$ perl -MTest::CPAN::Changes -e 'changes_ok'
1..4
ok 1 - Changes is loadable
ok 2 - Changes contains at least one release
ok 3 - Changes contains valid release dates
ok 4 - Changes contains valid version numbers

CPAN::Changes::Spec says:

    In order to satisfy release events not made to the public, or dates that
    are historically unknown, the following strings are also available:

    *   Unknown Release Date

    *   Unknown

    *   Not Released

So why does the site not allow the "Not Released" date?