[python-committers] Policy for committing to 2.7
Barry Warsaw
barry at python.org
Sat Jun 22 21:35:41 CEST 2013
More information about the python-committers mailing list
Sat Jun 22 21:35:41 CEST 2013
- Previous message: [python-committers] Policy for committing to 2.7
- Next message: [python-committers] Policy for committing to 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Jun 22, 2013, at 12:02 PM, Eli Bendersky wrote: >I may be missing something, but do we have a policy of what we're supposed >to commit to the 2.7 branch at this point? I was under the impression that >it's only bug fixes, documentation, and maybe tests. But it seems that >there are developers who see it otherwise. Strongly agree. One additional allowed category of changes are build system fixes, e.g. so that 2.7 can still be built on newer versions of operating systems it already supports. >It would be great if we could document this somewhere - the 2.7 branch is >not a usual bugfix-mode branch, I realize, and hence maybe there's some >special treatment it deserves. IMO, Benjamin being the 2.7 RM has ultimate[1] say in the matter. I'm very glad he's conservative in what he allows in the branch. -Barry [1] Well, maybe penultimate, but I wouldn't mind seeing the Mercurial equivalent of a wrastlin' match between him and the BDFL. :)
- Previous message: [python-committers] Policy for committing to 2.7
- Next message: [python-committers] Policy for committing to 2.7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list