Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Say you install an unstable/dev library, and you develop your app with it. You finish testing your app, you're ready to roll it into production, but the *library* hasn't come out of unstable/dev yet. That's what the policy's about.
    • Come on, makes sense? Be serious!

      This billion dollar guys are relying on free software (read CPAN) to do their job and they won't even take the hassle of testing a new version of this module which has been fixed for them and for free???

      Of course, you should release the changes on CPAN, so that they perceive this as "stable". The world is awesomely funny... :)

      • I did say *some* sense, not "perfect sense."

        It's one of the minor peeves I have with CPAN, though: it's not terribly clear to newbies exactly how mere mortals might go about testing a module, or submitting a new release. Those big red "UNAUTHORIZED RELEASE"s are not exactly confidence-inspiring when one is showing one's boss. Especially when one is part of a "billion-dollar company," which is generally synonymous with "hidebound bureaucracy," especially if there's government contracts involved.

        Not saying it's right. Just saying it makes a sort of sense.