[python-committers] Please don't commit to 3.2 branch anymore
Georg Brandl
g.brandl at gmx.net
Sat Mar 30 18:25:13 CET 2013
More information about the python-committers mailing list
Sat Mar 30 18:25:13 CET 2013
- Previous message: [python-committers] Please don't commit to 3.2 branch anymore
- Next message: [python-committers] Please don't commit to 3.2 branch anymore
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 03/30/2013 06:14 PM, Antoine Pitrou wrote: > Le samedi 30 mars 2013 à 10:13 -0700, Ned Deily a écrit : >> In article <20130330141534.44893250BDD at webabinitio.net>, >> "R. David Murray" <rdmurray at bitdance.com> wrote: >> > This is the first time we've been in the situation of having a >> > security-only branch in Mercurial (other than 2.7, which is its own head). >> >> 3.1? > > Or 2.6? > I also don't know what "which is its own head" is supposed to mean :-) Whatever :) Policy is, and always was, that security fixes are coordinated and committed to old branches by the release manager for that branch. Georg
- Previous message: [python-committers] Please don't commit to 3.2 branch anymore
- Next message: [python-committers] Please don't commit to 3.2 branch anymore
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list