comment on

While i do make mistakes when i upload a new release to CPAN, i do not upload development releases. The reason is because i have other tools to handle the items you listed out:

travis-ci will run smoke tests across several perls every time i push changes to my github repo
jenkins requires more work, but i find it invaluable to building my distros. Between travis-ci and my jenkins installation, i can get a very good idea at the quality of the current state of my distribution.
perlbrew is now more important to me than use strict. We'll come back to it later ...
cpanm allows me to install and uninstall the distros that i build via Jenkins. I configure Jenkins to make a successful build's tarball available for downloading via a URI. I can install this tarball directly with cpanm and see if there are any unexpected problems. Clean up is a breeze via cpanm -U.

So now i have a pretty good infrastructure set up to catch blunders i make: i should have commit hooks that will only fire when all tests pass, but i am pretty good at making sure tests pass before i commit code. I can browse travis-ci and make sure nothing is red: perhaps i added a dependency that an older perl didn't have or a newer one no longer ships with, etc. I can access my Jenkins server and build a test distro. I also use pod2html to make document artifacts that give me a decent approximation of how CPAN sites will format them. I can use perlbrew to switch to a clean perl distro and see how long it takes to install my module from scratch via cpanm.

Finally, after several days have passed since i uploaded a new version, i can check the CPANTS reports which is more exhaustive than my setup. I can recreate any test failures by installing that version of perl (thank you perlbrew) and running my tests against it. For example, i finally fixed this long running issue. (And so far ... so good.)

In summary, i do not want to give the impression that development releases are in anyway prohibited at CPAN. Quite the opposite. I just happened to acquire some skills to allow me to handle those issue you listed out before i upload to CPAN. Hope this helps. :)

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to Re: Uploading a devel version to PAUSE by jeffa
in thread Uploading a devel version to PAUSE by stevieb

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:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.