You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This sub would run various quality assurance checks on a module source to report what a module could use to improve its release. See Release::Checklist for some prior art. Some things to check for include:
Good module name (first-level namespaces are generally bad)
Tests
Are there tests
Do the tests succeed
Does installation of the module succeed
Documentation
A README with
Synopsis
Examples
Copyright information
A correct META6.json
Presence of some optional but useful fields
No unused dependencies
Dependency version adverbs
Version using a SemVer capable approach
(I understand not everyone is a huge fan of it as I am, but I've yet to find a better versioning scheme, and assixt can be a little opinionated on its QA. If there are better schemes out there, I'd like to hear, though.)
POD blocks for each sub and argument
Clean tree
Use version control to check for lingering files
Tree meta files
Check for a CHANGELOG
Check for a LICENSE
The text was updated successfully, but these errors were encountered:
This sub would run various quality assurance checks on a module source to report what a module could use to improve its release. See
Release::Checklist
for some prior art. Some things to check for include:META6.json
(I understand not everyone is a huge fan of it as I am, but I've yet to find a better versioning scheme, and
assixt
can be a little opinionated on its QA. If there are better schemes out there, I'd like to hear, though.)The text was updated successfully, but these errors were encountered: