XML-Config 0.2 Latest
Provide a short description in the NAME section of the pod (after the module name followed by a hyphen) at least for the main module of this distribution.
Add a Changelog (best named 'Changes') to the distribution. It should list at least major changes implemented in newer versions.
Add a META.yml to the distribution. Your buildtool should be able to autogenerate it.
Run a proper command ("make manifest" or "./Build manifest", maybe with a force option), or use a distribution builder to generate the MANIFEST. Or update MANIFEST manually.
- MANIFEST (8) does not match dist (9):
- Missing in MANIFEST: Makefile.old
Remove the POD errors. You can check for POD errors automatically by including Test::Pod to your test suite.
Error: XML-Config-0.2/Config.pm-- Around line 115: =pod directives shouldn't be over one line long! Ignoring all 4 lines of content
List all used modules in META.yml requires
Add 'use strict' (or its equivalents) to all modules, or convince us that your favorite module is well-known enough and people can easily see the modules are strictly written.
Add =head1 LICENSE and/or the proper text of the well-known license to the main module in your code.
Add a META.json to the distribution. Your buildtool should be able to autogenerate it.
Add tests or move tests.pl to the t/ directory!
Define the license if you are using in Build.PL. If you are using MakeMaker (Makefile.PL) you should upgrade to ExtUtils::MakeMaker version 6.31.
Add 'use warnings' (or its equivalents) to all modules (this will require perl > 5.6), or convince us that your favorite module is well-known enough and people can easily see the modules warn when something bad happens.
This is not a critical issue. Currently mainly informative for the CPANTS authors. It might be removed later.