You have no choice but to bump your version number each time, and yes, development versions get tested... note that you're taxing the Testers servers with each new upload though.

What I do, is have a Perlbrew setup locally, for all versions of perl, and spin my tests there (I construct/decom after each dist candidate test run). I also house at least one VM with Strawberry on Windows. If I have a fail on Testers, I'll spin a VM replicating the setup of the failed tests as best as possible and include that in my test regime before upload.

I also use Travis CI for each build which is run on each github push. See this .travis.yml file if you want an example Travis config (after you're on github and integrate with the service).

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.