comment on

Release a new module. If it contains substanitially more functionality, keep the backward compatible API distinct.

Old::Module

 becomes

New::Module
New::Module::OldModCompat
[download]

Then update the old module, addind text referring to the new module, and saying that the old will receive no further maintenance work. Don't remove it.

And think very carefully about the new modules name!

In reply to Re: Changing a module's namespace on CPAN by qq
in thread Changing a module's namespace on CPAN by jacques

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


XP is just a number
	PerlMonks