[python-committers] py3k vs trunk branches

Brett Cannon brett at python.org
Mon Apr 12 23:34:06 CEST 2010

On Mon, Apr 12, 2010 at 00:39, Dirkjan Ochtman <dirkjan at ochtman.nl> wrote:

> On Mon, Apr 12, 2010 at 09:35, Tarek Ziadé <ziade.tarek at gmail.com> wrote:
> > Since the 2.x line is now feature frozen (since 2.7 is the last 2.x
> > release and we have reached beta), most new developments will start in
> > the py3k branch.
> > I was wondering if it wouldn't make sense to rename the current trunk
> > to /py26 and  /py3k to /trunk.
> >
> > Although I am not sure if this is relevant with the work done on
> mercurial side.
> Yeah, I'd prefer to keep it like this for now.
Ditto. Since development will eventually switch there is no need to
complicate the svn stuff and bust existing checkouts by changing the names
now. Better to make any changes when we make the svn/hg switch.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-committers/attachments/20100412/951f4112/attachment.html>

More information about the python-committers mailing list