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 ...
-
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.
|
