[python-committers] Please don't commit to 3.2 branch anymore
R. David Murray
rdmurray at bitdance.com
Sat Mar 30 15:15:33 CET 2013
More information about the python-committers mailing list
Sat Mar 30 15:15:33 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 Sat, 30 Mar 2013 13:41:39 +0100, Jesus Cea <jcea at jcea.es> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 28/03/13 08:55, Georg Brandl wrote: > > with 3.2.4 being the last regular 3.2 maintenance release and the > > rc out of the door, the 3.2 branch should only be committed to for > > security releases. So please don't commit anything there anymore. > > To help everyone remember, I've configured the push hook to reject > > changesets to the 3.2 branch. > > What is the procedure for commiting security fixes?. Is it documentes > anywhere? 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). So I don't believe we have articulated a procedure yet. --David
- 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