Don't forget to bump the major version of the module (i.e. from 1.x to 2.x). Leave both the old and new versions on CPAN. Don't forget that some people will use other people's scripts that want the old module: the script still works so they don't have any reason to upgrade.
The deprecation warning is nice, but I'd at least have a way to turn it off.
Give plenty of notice of what's going to change, and give users a chance to comment on it informally. Hoepfully you know about some of the people who depend on your module and don't want to pull the rug out from under them.
Good luck :)
In reply to Re: Changing API's of CPAN modules
by brian_d_foy
in thread Changing API's of CPAN modules
by cog
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |