-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mar 5, 2009, at 6:18 PM, Martin v. Löwis 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. 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. Barry -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iQCVAwUBSbBgJHEjvBPtnXfVAQIEbQP6Ah9I4SikMQ++vlSYb4BdNgw0VXF/8PMH aTkG0+haOBoJ+mJ9G5GbBiJVtnV0B6qRV1gSV5FSIOzbQE/t0zU27APwnIWv57l9 uZIyyjU1AA0Gz5DSOsC9xtoAqEu/iFH9aRd17tE/N2Yib5p62myqAUVHIRPBl0fD sh+ztoL3q2c= =vgz0 -----END PGP SIGNATURE-----
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4