[EMAIL PROTECTED] schrieb: > >Not sure what you mean by "minor release". The change isn't proposed > >for the next bug fix release (2.5.1), but for the next major release > >(2.6). See PEP 6. > > Common parlance for the parts of a version number is: > major.minor.micro > See: > > http://twistedmatrix.com/documents/current/api/twisted.python.versions.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.
When PEP 6 was originally written, it said "feature release", and "bug fix release". This was then changed at some point (too lazy to look up subversion log now) to say "major release" and "bugfix release", indicating that the major releases (in the sense of the common expectation) *are* the 2.x releases. At that time, it wasn't clear whether there ever would be a 3.0 release. This is where my understanding of policy comes from: bug fix releases are for bug fixes *only*, major releases can add new features, and correct problems that may break existing applications (using parallel APIs, warnings, etc, as appropriate). Regards, Martin _______________________________________________ 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
