Home Original page

[python-committers] Is 3.1 open?

Nick Coghlan ncoghlan at gmail.com
Wed Mar 17 22:26:10 CET 2010 
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 the repository to getting it ready for
>> release, while the main repository accepts new changesets. The point
>> would be not stopping commits, ever.
> 
> 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 interesting explanation from Joel Spolsky the other day
as to why this isn't actually true (even with svnmerge):
http://hginit.com/00.html

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.

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
---------------------------------------------------------------
More information about the python-committers mailing list