[Python-Dev] Mercurial migration readiness (was: Taking over the Mercurial Migration)

[Tim Delaney]

On 2 July 2010 09:08, Tim Delaney <timothy.c.delaney at gmail.com> wrote:

> On 2 July 2010 08:07, Barry Warsaw <barry at python.org> wrote:
>
>>
>> Other than that, while I sometimes review patches in email, I do not think
>> patches in a tracker are the best way to manage these.  A dvcs's biggest
>> strength is in branches, so we should use those as much as possible.
>>
>>
> 7. Merged default branch was pushed to the central repo, which triggered a
> continuous build.
>
> Clarification here - I mean that a committer would merge it to default,
then pull it into the main python repo - there would be one that anyone
could push changes to, and those named branches would then be cherry-picked
to be merged and pulled into the main repo by committers. Or something along
those lines.

Tim Delaney
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20100702/a6a7e408/attachment.html>