Its simple

Release a development version (thats with a _ 01 in version number)

warn in the docs what the change is gonna be, fix what needs fixing

Wait for complaints (ex 1week or 1month)

Then in a week or month release the next stable version and you're done

Then wait the next ten years for complaints from regular fools who dont read docs or have test suits .... ;) It really is that simple ;)

For one example you can see about CGI changes since 4.03 2014-07-02

4.05 (LEEJO on 2014-10-08) 4.04_05 DEV (LEEJO on 2014-10-06) 4.04_04 DEV (LEEJO on 2014-10-06) 4.04_03 DEV (LEEJO on 2014-09-29) 4.04_02 DEV (LEEJO on 2014-09-28) 4.04_01 DEV (LEEJO on 2014-09-20) 4.04 (LEEJO on 2014-09-04)

LEEJO gets commit bit and sets about gutting ye olde tool bucketbagbox ...


In reply to Re: Minor API changes in 10-year-old module by Anonymous Monk
in thread Minor API changes in 10-year-old module by wanna_code_perl

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.