I have three Perl modules just begging to be released:
Plus a new version of FRELI, my English wordlist.
But somehow I just can't seem to let them go. I find myself racking my brains to think of every little detail:
cvs tag!!
With tools like make distcheck, t/pod.t, and cpan-upload there's really no reason to worry. But for some reason I do anyhow.
It's like I'm a parent whose child is getting ready to leave home and go to college. All for a few little bits of code and data. Sheesh! So pathetic...
It's hard to let go.
Module::Release :) (Score:1)
Once you install the package, read the docs, and get things setup, just cd into your distribution directory and 'release'.
It makes sure CVS is up to date, generates the MANIFEST, runs all the checks, then sends the tarball off to either or both CPAN and Source Forge. (I'm sure I'm missing other wonderful things it does so just read the docs) :)
It took a bit to get things setup and found a couple annoyances (that I didn't bother to note back then and can't rem
-biz-
Heh (Score:1)
------------------------------
You are what you think.
Just release them (Score:2)
(No, I haven't drunk the Microsoft QA kool-aid. I'm just being pragmatic.)
Re:Just release them (Score:2)
Release early, release often
Your users will find many more bugs than you ever could - if they don't then everything is fine.
You will even get to test things better yourself, because you will be installing the module from CPAN (you will be doing that won't you?) just as anybody else - so many bugs may show up at that point. I find that a release after a major overhaul resultat in a flurry of small bug-fix releases until everything stabilises.
If you are really uncertain, then tell you users that this is a
Re:Just release them (Score:1)
To these I hope to add: Release happily.
Rather than Release nerve-wrackingly, that is.
:-)