On Apr 01, 2011, at 03:07 PM, Michael Foord wrote:
That was about whether the release manager should backport doc fixes from 2.7 to the 2.6 branch and the conclusion was "not to bother", which is very different from saying that individual developers *can't* apply doc fixes if *they want*.
Of course if the release manager says *do not* (which is different from *we won't be bothering*) then that is their decision and should be honoured.
Yeah, I know what I said before but I really am still on the fence about non-behavior changing fixes. Both sides have valid positions, IMO. :/ But as before, I'll abide by consensus, if such a thing can be determined. Not applying the patch to 2.6 will make things harder for me if I ever have to do another 2.6 release, but not impossible. However, because of the hg forward porting policy, I would like to decide asap on how far back to port the fix. As I see it, the patch is uncontroversial for 3.3, 3.2, and 2.7. And it definitely will not be applied to 3.0. That leaves 2.5, 2.6, and 3.1. If you really care one way or the other, please register your vote in the tracker. http://bugs.python.org/issue11715 (Hey, tracker voting would be a cool GSoC project perhaps) -Barry