but I don't see a way to get those checks (kwalitee) dome on the development version.

It's right here.

The CONTRIBUTING file is a relatively recent phenomenon so there are fewer references to such a thing in the documentaion for module authors. If you are concerned about quality metrics then I would suggest three and a half sources:

• The kwalitee measure as already referred to.
• The test matrix - all green is good.
• The test coverage - the higher the percentages the better.
• and the half: Perl::Critic. It is highly opinionated but it might make some recommendations with which you agree. Just try not to get too obsessive about it.

It might help to unify things if you capitalised the dist name for future releases too.

Good luck.

Thanks once again for your very helpful responses.

Short of constructing the link manually in the browser's location bar, how would I be expected to navigate to https://cpants.cpanauthors.org/release/GWHAYWOOD/sendmail-pmilter-1.20_01 ? Is there a page somewhere with a link to that page?

The test matrix looks good, it was about the only thing that had made any sense to me so far.

I'd seen the "test coverage" link but it made no sense to me.
I'm beginning to think it tells me which statements in the released modules get exercised by the tests in t/, is that right?
Where is it documented?

I'll take a longer look at Perl::Critic, but at first glance it seems more a style thing than what I'd call "quality".

Some specific points:

• You suggest capitals for the "dist name". I guess I don't understand again but isn't the dist name Sendmail::PMilter ?
  I think I've been misled by downloads from, er, another place, which don't seem to keep the capitalisation in the archive (.zip) files.
  Do you mean the name of the tarball? Obviously it's no problem to change the name of the tarball.
• I've wandered around for days looking for an issue tracker for the development releases like there is for the full releases.
  Is there such a thing?
• The Kwalitee thing talks about META.yml or META.json but the tools create MYMETA.* instead.
  Do I just rename them?
• Unrelated, but it's starting to get to me: Are there alternative interfaces to this (for want of a better description) bulletin board?

Thanks again. I'll be back, I guess. :)

Do you mean the name of the tarball?

Yes.

I've wandered around for days looking for an issue tracker for the development releases like there is for the full releases. Is there such a thing?

Yes, it's at https://rt.cpan.org/. You can raise issues against dev releases there just the same as prod releases.

The Kwalitee thing talks about META.yml or META.json but the tools create MYMETA.* instead. Do I just rename them?

No! Those are totally different - the MYMETA.* files are generated when the user installs the module. Do not distribute these. The META.* files should be generated by you when you roll the release and should be distributed. The make dist should handle this for you automatically - if not, check your Makefile.PL and/or MANIFEST. See the Module Meta-Data section of the EU::MM docs for more on this.

Are there alternative interfaces to this

Maybe, assuming you mean The Monastery. Although the normal interface at https://www.perlmonks.org/ is highly customisable if that's what you're after. See How do I change my preferences?