in reply to Introducing beta code into CPAN modules

I think your approach is wise and well thought out. I'm about to tackle a similar problem myself with some of my own code.

Perhaps distributing the Beta as a separate package would be better? That way it wouldn't be somewhat hidden. Anyone browsing CPAN directly would see it separately, and perhaps you could wire a message into the make sequence to notify people of the Beta. Thus, someone using CPAN.pm would also be made aware of it.

HTH

/\/\averick
perl -l -e "eval pack('h*','072796e6470272f2c5f2c5166756279636b672');"

  • Comment on Re: Introducing beta code into CPAN modules

Replies are listed 'Best First'.
Re(2): Introducing beta code into CPAN modules
by FoxtrotUniform (Prior) on Nov 06, 2001 at 21:43 UTC

    I prefer Masem's approach, if only because it's simpler (just one package to worry about). The only issues I can see with it are:

    • Reduced visibility of the beta code (which isn't necessarily an issue: you don't really want people finding beta code before a stable version that already does what they want, and when they grab the stable version, oh hey, here's a beta module to try out)
    • increased footprint (extra code means extra files that the user doesn't have much of a choice about downloading, which might be annoying for student users with fascist disk quotas to worry about).
    --
    :wq