Relating to changes that I plan to make in my modules, I plan to add code that may significantly alter the use of those modules (for example, different order of arguments to key functions, etc), in addition to updating base code that will not affect the user interface. Obviously, I would not want to have a significant effect on any established code that is already using my classes, and while I can beta test with other users, full distribution and associated feedback is the best way to test these changes as with any open-source project.

So I'm thinking that if my module is My::Module, I would want to duplicate that and create My::Module::Beta, in which all significant interface changes would go. These would still be released as one perl package, but those that want to test the new versions can use My::Module::Beta, and if they want to revert back, it's a quick deletion in the use section. This would also allow me, when approaching the completion of beta testing, to insert warn statements in the My::Module code on those functions which might be depricated or changed such that users can be expected to switch over when My::Module::Beta changes are merged into My::Module.

Any other thoughts on this type of situation?

-----------------------------------------------------
Dr. Michael K. Neylon - mneylon-pm@masemware.com || "You've left the lens cap of your mind on again, Pinky" - The Brain
"I can see my house from here!"
It's not what you know, but knowing how to find it if you don't know that's important

In reply to Introducing beta code into CPAN modules by Masem

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.