In my personal opinion, doing a dev release to CPAN without an initial release without having at least done your own suite of multi-environment testing borders on abusing the cpantesters network

My understanding was that we should always upload a dev release first!

I thought I got that from Re: What do I use to release a module to CPAN for the first time? but rereading it, that's not where it came from...
The point of this thread was to try to lessen the load on cpan testers, certainly not to abuse them.

Surely, if we upload a production release before a dev release, people can start using it before it is properly tested - or am I missing something here?

there's no reason for not doing a suite of tests long before any release or dev-release to CPAN, on at least Ubuntu and Windows

The tests were created ahead of writing the code. However, one test I couldn't write without the help from Testing image output. I had planned what I wanted to test but couldn't convert that visual test into a programmatic test. v0.01_1 omitted that test, subsequent versions included it and tried to get it to work in different environments. The tests were all run locally using prove and passed...I wouldn't have uploaded a module that failed local tests.

As a very recent user of GitHub, I had no idea I could test modules with it!

And as a final small piece of advice: always include the META_MERGE in your Makefile.PL

It's on my list of things to do...to work out what all these META files are in a distribution...

It strikes me as very odd that we have to run gmake disttest, then go and copy files from one place to another. Surely, the toolchain should do that for us if it always needs doing, shouldn't it? I always forget if I'm supposed to be copying META.yml or MYMETA.yml. I guess that if I understand the significance of these files, it will all be clearer.

Question...

Given where I am with 4 dev releases, what would you advise I do next?

Is it sensible to remove the tests that fail and upload a production release next and then develop it further from there?

In reply to Re: testing/release advice [was: Stopping tests] by Bod
in thread Stopping tests by Bod

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.