Re: [python-committers] Is 3.1 open?

2010-03-17 Thread Antoine Pitrou
Le dimanche 14 mars 2010 à 03:52 +0100, Jesus Cea a écrit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 03/14/2010 03:35 AM, Benjamin Peterson wrote: > >> Mercurial, where are you?. This would be a non issue :) > > > > How so? > > The release manager could clone the repository to ge

Re: [python-committers] Is 3.1 open?

2010-03-17 Thread Nick Coghlan
Antoine Pitrou wrote: > Le dimanche 14 mars 2010 à 03:52 +0100, Jesus Cea a écrit : >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> On 03/14/2010 03:35 AM, Benjamin Peterson wrote: Mercurial, where are you?. This would be a non issue :) >>> How so? >> The release manager could clone

Re: [python-committers] Is 3.1 open?

2010-03-17 Thread Benjamin Peterson
2010/3/17 Nick Coghlan : > Short version: SVN and other non-DVCS systems don't store enough (or the > right) metadata to support merging properly, so branching becomes > unnecessarily painful. This isn't really true these days given svn merge --reintegrate. -- Regards, Benjamin ___

Re: [python-committers] Is 3.1 open?

2010-03-17 Thread Antoine Pitrou
Le jeudi 18 mars 2010 à 07:26 +1000, Nick Coghlan a écrit : > > > > We could already do so with SVN, simply by opening a release branch when > > entering rc phase, and only merging selected (release blocking) fixes to > > that branch. There's nothing DVCS-specific here. > > I came across an inter

Re: [python-committers] Is 3.1 open?

2010-03-17 Thread Nick Coghlan
Benjamin Peterson wrote: > 2010/3/17 Nick Coghlan : >> Short version: SVN and other non-DVCS systems don't store enough (or the >> right) metadata to support merging properly, so branching becomes >> unnecessarily painful. > > This isn't really true these days given svn merge --reintegrate. File

Re: [python-committers] Is 3.1 open?

2010-03-17 Thread Martin v. Löwis
Nick Coghlan wrote: > Benjamin Peterson wrote: >> 2010/3/17 Nick Coghlan : >>> Short version: SVN and other non-DVCS systems don't store enough (or the >>> right) metadata to support merging properly, so branching becomes >>> unnecessarily painful. >> This isn't really true these days given svn mer

Re: [python-committers] Is 3.1 open?

2010-03-17 Thread Antoine Pitrou
Le mercredi 17 mars 2010 à 23:02 +0100, "Martin v. Löwis" a écrit : > My expectation is that the release process won't change in this respect > after the switch to Mercurial. We will continue to freeze the > maintenance branch for releases, because everything else is too tedious > for the release m