gtg-contributors team mailing list archive

[Luca Invernizzi <invernizzi.l@xxxxxxxxx>]

Hello people,
we merged liblarch with trunk, as all the development was occuring
there anyway and it reached a stability that is comparable with trunk
(more crash and burns, but no task duplications that were plaguing
trunk).

 It has the big advantage of being well tested and quite usable (while
trunk dnd is a nightmare), but it falls short in a few places, for
now. These are:
- performances in removing and updating nodes (lionel is working on it)
- gtk errors causing segfaults (sporadic)
- in the tags tree, when adding a tag all the partial tags are
displayed(@t, @ta, @tag)

Test it, and fix it! :D


On Wed, Sep 8, 2010 at 11:11 AM, Lionel Dricot <ploum@xxxxxxxxx> wrote:
> I think that release 0.3 should have the backends as the new feature. All
> the rest is optional but we should be feature equivalent.
>
> It means :
>
> - Drag-n-drop in liblarch (my job)
> - Plugins porting (I saw you did it. Perfect ! API plugin refactorization
> can wait)
> - testing, testing and bug fixing.
>
> We should consider merging liblarch_branch with trunk. Lilbarch is still
> quite unstable but I believe trunk is not in better state.
>
>
> Lionel
>
>
> On Fri, 3 Sep 2010 18:52:45 +0200, Luca Invernizzi
> <invernizzi.l@xxxxxxxxx>
> wrote:
>> Hello dear developers,
>> first of all, congrats to Lionel for fixing liblarch! I've been
>> testing it, and it works nicely. I cannot stress how great that is :D
>>
>> It's been a while since last gtg release, so I wanted to make the
>> point of the situation to see what's preventing us to release 0.3.
>>
>> After looking at the bugs list and at the FOSDEM notes, I'd say that
>> we have this TODO:
>> - drag and drop on liblarch (not implemented yet)
>> - fixing plugins API
>> - making sure that the transition between plugins and backends doesn't
>> duplicate tasks (my job :))
>> - better indicator plugin ("notification area") (also my job, not
>> release-critical)
>> - the couchdb and zeitgeist backends are not ready for merge request
>> yet. I don't want to put too many in a single release to avoid a bug
>> storm, but maybe the couchdb one should go in the release, as it was
>> planned in FOSDEM and in the roadmap. (not critical also)
>> - updating the initial tutorial. I've some ideas for this, I'll try to
>> put them on e-paper.
>> - lots of manual testing and translations
>>
>> Our roadmap also planned:
>> - columns rearrangement
>> - advanced tag editor
>> - improved task editor
>> - more plugins (!?)
>> But these can wait.
>>
>> Is there anything else?
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~gtg-contributors
>> Post to     : gtg-contributors@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~gtg-contributors
>> More help   : https://help.launchpad.net/ListHelp
>