in reply to Re^4: Looking for the maintainer of Sendmail::Milter.
in thread Looking for the maintainer of Sendmail::Milter.

Yes, I followed the guidelines - I started this ball rolling in February 2017, and the response has been, to put it politely, thin.

Thanks very much for the links, looks like there have been no replies that I haven't seen.

  • Comment on Re^5: Looking for the maintainer of Sendmail::Milter.

Replies are listed 'Best First'.
Re^6: Looking for the maintainer of Sendmail::Milter.
by GWHAYWOOD (Sexton) on Jul 04, 2019 at 14:18 UTC
    Don't know if I'm using the comment facility in the way that's intended, please be gentle.

    Yes, it's been a while since I started this ball rolling.

    No luck at all with the (alleged) maintainer of Sendmail::Milter.

    I've re-written Sendmail::PMilter so that it doesn't need Sendmail::Milter.

    I've been exercising it for a while and it's Been Reliable For Me.

    I'd now like to work on the packaging, so I can get anyone who's interested to try a TRIAL version, and I'm looking at
    https://www.cpan.org/modules/04pause.html#before

    It's recommended there for newbies like me to use PrePAN, but unfortunately PrePAN wants me to log in using Twitter or Github.

    I neither have nor want accounts on Twitter and Github.

    Can anyone suggest alternatives?

    Thanks.

      You could upload it to CPAN as a developer release (a mechanism designed for scenarios just like yours).
        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?

      Can anyone suggest alternatives?

      If the user interface of Sendmail::PMilter is unchanged then I don't see that it needs to go to PrePAN anyway. All you will have done is changed how it performs its tasks internally which is something the module users won't care about. In which case, I agree with Arunbear and you should just roll a dev release.