On Friday 16 March 2007 07:57, [EMAIL PROTECTED] wrote: > Common parlance for the parts of a version number is: > major.minor.micro > See: > http://twistedmatrix.com/documents/current/api/twisted.python.ver >sions.Version.html#__init__ > > Changing this terminology about Python releases to be more > consistent with other projects would be a a subtle, but good > shift towards a generally better attitude of the expectations of > "minor" releases.
I disagree entirely. Python has major releases, and bugfix releases. At the moment, the major releases are of the form 2.x, and bugfix 2.x.y. Trying to say that 2.4->2.5 is a "minor" release is just nonsensical. That suggests that very little new language development would go on, at all. Now, you might be arguing that in fact very little should go on (I know some people have argued this, I can't remember if you were one of these). My standard response to this is that people who really feel like this are welcome to pick a release, say, 2.3, and take on the process of backporting the relevant bugfixes back to that release, and cutting new releases, &c. -- Anthony Baxter <[EMAIL PROTECTED]> It's never too late to have a happy childhood. _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com