gtg-user team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxx>]

On Mon, Mar 01, 2010 at 10:00:59AM +0100, Lionel Dricot wrote:
> First of all, I want to thanks Luca and all the contributors to the nice
> and shiny 0.2.2 release.
> 
> Now for some exciting news : if Luca is very good at fixing bug, I'm
> personally good at creating new ones. This means that trunk will be soon
> completely broken.
> 
> *DON'T USE TRUNK ANYMORE*
> 
> For a few weeks, don't use trunk if you don't plan to contribute code.
> 
> If you are a very brave tester, you can try to list regressions. Fill them
> in launchpad with the tag "regression". But, because there are so many
> regressions, please be careful to not fill in duplicates. If you are
> unsure, don't do anything (
> https://bugs.edge.launchpad.net/gtg/+bugs?field.tag=regression )

Now that a few weeks are over, it'd be great to get trunk back to a
usable state, since various development efforts are pending which would
benefit from having a stable base to build on.

Sadly as Lionel promised the trunk is pretty crashy.  In testing it I've
found it at least is not corrupting my tasks xml, but it does choke on a
lot of the stuff in it.

I've accumulated some fixes to this branch:

   lp:~bryceharrington/gtg/0.3-fixes

For testing, a good idea is to start gtg using ./scripts/debug.sh and
then write the minimum set of steps to reproduce the bug.  I think this
will help make it clearer to developers what the issue is so they're
quicker to fix.

./scripts/debug.sh will make it so gtg 0.3 does *not* touch your current
tasks.  You can also run two instances of gtg simultaneously (your
regular gtg/2.4, plus the debug gtg/3.0-trunk) which I find quite
convenient.

Bryce