4 ms·
There doesn't seem to be anything specific to a "Perl Shop" on the list. Perl specific maturity items would be: 1) Do all packages have documentation (pod) st
by fabricode 14y ago
There doesn't seem to be anything specific to a "Perl Shop" on the list.
Perl specific maturity items would be:
1) Do all packages have documentation (pod) stored in the package file(s), and is it up to date?
2) Are there tests built using TAP (e.g. Test::More), and is this built into some kind of continuous build/test server?
3) Have a set of perlcritic rules been set up for the shop? Are these checked as part of code-review or scm check-in?
4) Is there a consistent set of rules for how external packages are brought into the current build? How are local changes to CPAN-originated packages handled?
These are the kinds of policies I'd expect to see implemented in a mature Perl Shop. The policies listed in the original post are those which I'd expect to see implemented in a mature software firm.