Am 01.04.2011 13:57, schrieb Michael Foord:
On 01/04/2011 11:46, Georg Brandl wrote:
Am 31.03.2011 19:35, schrieb Éric Araujo:
I would like to apply this patch (or its moral equivalent) to all active, affected branches of Python, meaning 2.5 through 2.7, and 3.1 through 3..3, as soon as possible. Without this, it will be very difficult for anyone on future Ubuntu or Debian releases to build Python. Since it's not a new feature, but just a minor fix to the build process, I think it should be okay to back port. If I understand the policy correctly, 2.5 and 2.6 are not considered active branches, so any doc, build or bug fixes are not acceptable. I wouldn't say doc fixes are not acceptable, but they are rather pointless since there won't be any more online docs or released docs for those versions. In the case that docs are wrong for unmaintained (but still used) versions of Python, is there any reason other than policy not to fix and update online docs?
I think I was unclear: I'm not advocating doing doc fixes in security-only branches; I'm just explaining why it wouldn't even make sense to do these fixes. Let's not make life harder for the RMs of security-only branches... Georg