in reply to Uploading a devel version to PAUSE
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:
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)
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Uploading a devel version to PAUSE
by stevieb (Canon) on Jul 23, 2015 at 17:40 UTC |