https://metacpan.org/release/HMBRAND/Release-Checklist-0.17/view/Checklist.pm#Version-coverage and https://metacpan.org/release/HMBRAND/Release-Checklist-0.17/view/Checklist.pm#Multiple-perl-versions recommend Travis for automated testing, but as far as I can tell, Travis is dead.
The linked site (travis-ci.org) doesn't exist anymore (it redirects to travis-ci.com), and my own Travis tests stopped running years ago (and the Travis management interface just sits and spins, so I can't fix or even diagnose anything).
Nowadays it is probably better to recommend GitHub Actions for integration testing.
PS: The .travis.yml link in https://metacpan.org/release/HMBRAND/Release-Checklist-0.17/view/Checklist.pm#Version-coverage is broken: It goes to https://metacpan.org/pod/#.travis.yml, which is 404.
https://metacpan.org/release/HMBRAND/Release-Checklist-0.17/view/Checklist.pm#Version-coverage and https://metacpan.org/release/HMBRAND/Release-Checklist-0.17/view/Checklist.pm#Multiple-perl-versions recommend Travis for automated testing, but as far as I can tell, Travis is dead.
The linked site (travis-ci.org) doesn't exist anymore (it redirects to travis-ci.com), and my own Travis tests stopped running years ago (and the Travis management interface just sits and spins, so I can't fix or even diagnose anything).
Nowadays it is probably better to recommend GitHub Actions for integration testing.
PS: The
.travis.ymllink in https://metacpan.org/release/HMBRAND/Release-Checklist-0.17/view/Checklist.pm#Version-coverage is broken: It goes to https://metacpan.org/pod/#.travis.yml, which is 404.