Barry Warsaw wrote:
That aside, is it actually a python-wide policy to *forbid* patching
older releases where the patch isn't security-related?
I set this policy for the releases I manage, namely 2.4 and 2.5.
This is a Python-wide policy.
...and, now that Martin has explained it, it makes perfect sense...
When Python 2.7 is released, there will be one last 2.6.x bug fix
release, and then it will go into security-only mode. Similarly, when
Python 3.1 is released, there will be one last 3.0.x release and it too
will go into security-only mode.
...of course, in a perfect work, it'd be nice to have 2 or 3 previous
second point releases in bug-fix mode, rather than just one ;-)
Chris
_______________________________________________
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
