Home Original page

[python-committers] branches and merging

Brett Cannon brett at python.org
Tue Mar 2 03:06:33 CET 2010 
On Mon, Mar 1, 2010 at 14:24, Barry Warsaw <barry at python.org> wrote:

> On Mar 01, 2010, at 02:06 PM, Brett Cannon wrote:
>
> >Well, if we are already screwed if we do a blind merge we might as well
> stop
> >wasting our time on doing blocks since that is the only real use case for
> >bothering.
>
> Maybe we should consider switching to hg now rather than waiting?  (Well,
> by
> "now" I mean after I release 2.6.5 :).  We're still a month away from 2.7
> beta
> 1 and 6+ months away from 3.2 beta 1.  If svn is hopeless (and my vote is
> that
> it is) let's do the switch now with plenty of time to shake out the pain.
> Nothing like angry developers to motivate that, and at least now that
> Pycon's
> over, physical intimidation is more difficult. :)
>
> Seriously though, do we really have to wait until 2.7 is released?
>

The hold-up will ultimately be the EOL extension and the updated docs now
that Dirkjan has a patch for sys.mercurial. The 2.7 date was to give a
target date push those last two items to be done.

-Brett




>
> -Barry
>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> http://mail.python.org/mailman/listinfo/python-committers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20100301/23ede7b3/attachment-0001.html>
More information about the python-committers mailing list