[python-committers] py3k vs trunk branches
Dirkjan Ochtman
dirkjan at ochtman.nl
Mon Apr 12 09:39:21 CEST 2010
More information about the python-committers mailing list
Mon Apr 12 09:39:21 CEST 2010
- Previous message: [python-committers] py3k vs trunk branches
- Next message: [python-committers] py3k vs trunk branches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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. Cheers, Dirkjan
- Previous message: [python-committers] py3k vs trunk branches
- Next message: [python-committers] py3k vs trunk branches
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list