This really depends on how many people are using your code. If you were making changes to LWP, you would have a much different strategy than if you were making changes to a module only a handful of people actively use. If only a few people use it, then just warn the folks using the module, make the change and be done with it. Otherwise six months from now someone using an older version of your module will have a problem and you won't be able to remember when you made a particular change permanent, etc. Who needs that?
Also, I think it's confusing to distribute in the same module beta code that duplicates functionality of stable code. Most people will never use it (they just need to get a job done), so you've gone and confused them without any benefit (comments, patches, etc.) to yourself. The people who will actively use beta code are likely motivated enough to download a separate package from a separate site.
All IMO, of course :-)
Chris
M-x auto-bs-mode
In reply to Re: Introducing beta code into CPAN modules
by lachoy
in thread Introducing beta code into CPAN modules
by Masem
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |