> I think there should be some rules of thumb.

In open source we should rather talk about habits and culture, if there are rules they developed from tradition.

> how to minimize the damage from a possible bad decision in the first place? 

Flag your module as experimental, till its implementation is fixed.

Or contact the users, if there are no reverse dependencies you should be fine.

> we'd run out of CPAN namespaces

Not if you keep the old API for a deprecation period.

For instance you could refactor the "bad" part of module XXX to XXX::Old, and use it internally.

Or new users need a use XXX :modern attribute or version number during a grace period.

You should know best what is feasable!

Sorry, I'm not aware of any policy which will safe you from being called names by old users if you break their code, even after warning them for years.

It's up to you. .. :)

Just have a look at CGI.pm

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice


In reply to Re^3: Sane deprecation policy for a CPAN module? by LanX
in thread Sane deprecation policy for a CPAN module? by Dallaylaen

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.