Thanks for the replies. There are enhancements to the API, but it's basically the same API so I think it's going to be a developer release. That sounds right.

The documentation isn't clear to me. For a developer release, do I need to do something with the $VERSION scalar in the .pm files themselves to make PAUSE recognize that it's a developer release, or will it be sufficient to name the uploaded tarball "sendmail-pmilter-1.21-TRIAL3.tar.gz" while in the two .pm files which it contains will be

our $VERSION = '1.21';

the intention being to leave $VERSION at that value after any fixes to the developer release are completed?

In reply to Re^8: Looking for the maintainer of Sendmail::Milter. by GWHAYWOOD
in thread Looking for the maintainer of Sendmail::Milter. by GWHAYWOOD

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.