<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 19 August 2014 00:51, Grant Edwards <span dir="ltr"><<a href="mailto:invalid@invalid.invalid" target="_blank">invalid@invalid.invalid</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="">On 2014-08-17, Mark Lawrence <<a href="mailto:breamoreboy@yahoo.co.uk">breamoreboy@yahoo.co.uk</a>> wrote:<br>
> A blog from Nick Coghlan<br>
> <a href="http://www.curiousefficiency.org/posts/2014/08/python-4000.html" target="_blank">http://www.curiousefficiency.org/posts/2014/08/python-4000.html</a> that<br>
> should help put a few minds to rest.<br>
<br>
</div>I agree with the comments that the appellation for "simply the next<br>
version after 3.9" should be 3.10 and not 4.0. Everybody I know<br>
considers SW versions numbers to be dot-separated tuples, not<br>
floating point numbers.<br>
<br>
To all of us out here in user-land a change in the first value in the<br>
version tuple means breakage and incompatibilities. And when the<br>
second value is "0", you avoid it until some other sucker has found<br>
the bugs and a few more minor releases have come out.<br></blockquote><div><br></div><div> No. A major version increase *may* introduce breakage and incompatibilities. It does not mean that it *has* to introduce breakage and incompatibilities. If the major version increase is documented as "just being the next version" then there's no reason to avoid it - unless your policy is "wait for the first patch release" i.e. never take major.minor.0 but always wait for major.minor.1.</div>
<div><br></div><div>What is more important is that minor and patch version increases should avoid introducing breakage and incompatibilities wherever possible (security fixes are one reason to allow incompatibility in a minor release).</div>
<div><br></div><div>BTW I agree with the idea that 4.0 would be an appropriate time to remove anything that has been deprecated for the requisite number of versions.<br></div><div><br></div><div>Tim Delaney</div></div></div>
</div>