How about 3.3.3 -> 3.3.4 is a "minor" release, 3.3 -> 3.4 is a "feature" release and 3 -> 4 is not something we generally talk about (or "compatibility-breaking" or something like that).
The issue with that is that the "y" in 'Python x.y.z' is usually called the minor release (see: http://docs.python.org/devguide/devcycle.html ). Switching which digit the minor release is would be confusing when reading older documents. It might be better to instead keep the old name, "bugfix", since that isn't confusing. Then we would be left with "compatibility-breaking.feature.bugfix", which isn't really bad in any sense I can see (aside perhaps from being new and unusual?) Devin On Wed, Aug 31, 2011 at 1:45 PM, Paul Moore
On 31 August 2011 18:33, Antoine Pitrou
wrote: (*) Can we pick a terminology so we all agree that "3.3.3" is a "minor release", "3.3" is a "major release", and "3" an "earthshattering release"? Or other terms -- but something that is both agreed upon and clear enough without explanation. I'm tired of having to clarify minor and major every time I use them out of fear they'll be mistaken for "3" and "3.3".
+1! "Minor" really sounds like a misnomer when applied to feature releases.
How about 3.3.3 -> 3.3.4 is a "minor" release, 3.3 -> 3.4 is a "feature" release and 3 -> 4 is not something we generally talk about (or "compatibility-breaking" or something like that).
I suspect that "minor" for changing the last digit is pretty comprehensible, it's using "major" for 3.3 that confuses people, so let's avoid that term...
Paul. _______________________________________________ Python-ideas mailing list Python-ideas@python.org http://mail.python.org/mailman/listinfo/python-ideas