use Perl

• Module::Release :) (Score:1)

  by jbisbee (2452)

  Grab Module::Release

  Module::Release [cpan.org]

  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)

  by chaoticset (2105)

  I read that wrong at first -- I thought your wordlist was called FRELL [farscape.com].

  --
  
  ------------------------------
  You are what you think.
• Just release them (Score:2)

  by jhi (318)

  People will find out the bugs that matter. Those they won't find, don't matter.
  
  (No, I haven't drunk the Microsoft QA kool-aid. I'm just being pragmatic.)
  
  • Re:Just release them (Score:2)

    by htoug (771)

    Yes.

    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)

      by nkuitse (193)

      Release early, release often.
      
      To these I hope to add: Release happily.
      
      Rather than Release nerve-wrackingly, that is. :-)