On Fri, Feb 17, 2012 at 8:50 AM, Christoph Zwerschke c...@online.de wrote:
But if that next release will be 2.2 and we later want to release a 2.1.5
bugfix we should also have a separate 2.1 branch (which still supports Py2.4
and works without Crank). Since the development branch has already
Ok, I have now added download directories development and next for
the corresponding branches in our Git repository. The development
directory contains the Crank package which made Chuck really happy.
Is the development branch supposed to work with Python 2.4? There are
two issues that
I remember Python2.4 support being dropped with the last release.
Michael can probably confirm this as I remember him adding version
check inside the TG source code.
If we didn't it is probably the right time to do it as the python3
development branch also drops support for python2.5, so dropping
Am 16.02.2012 20:15, schrieb Alessandro Molina:
I remember Python2.4 support being dropped with the last release.
Michael can probably confirm this as I remember him adding version
check inside the TG source code.
There is only a version check that allows Py2.4 to work by adding
pysqlite and
Am 16.02.2012 20:45, schrieb Alessandro Molina:
I'm currently managing work this way:
development branch - 2.2
pylons-less branch - 2.3
python3 branch - whatever will be after that
And the next branch is for the next 2.1.x bugfix release, right?
--
You received this message because you
On Thu, Feb 16, 2012 at 10:53 PM, Christoph Zwerschke c...@online.de wrote:
Am 16.02.2012 20:45, schrieb Alessandro Molina:
I'm currently managing work this way:
development branch - 2.2
pylons-less branch - 2.3
python3 branch - whatever will be after that
And the next branch is for
Am 16.02.2012 23:20, schrieb Alessandro Molina:
Actually I always thought that the next branch was only for release
process like stated on
http://www.turbogears.org/book/appendices/preprelease.html#finalizing-changes-on-next-branch
Makes sense, then this is only intended as a temporary branch.
Yes, it's a few days that it's broken due to Crank, we need a way to
handle the insertion of new dependencies inside the project during the
development process. Not having it makes a bit useless Jenkins itself
as you are not able to know if things are broken for real as they
always result being
