Posts in category bzr

Switch back to darcs (and forth to Trac 0.12)

After having used bzr for a few months, we switched back to our beloved darcs. Bzr is not bad per se, but darcs is much more smooth, easy and powerfull when it comes to merges, which is what we do most of the time: small corrections of small bugs, pushed and pulled from/to dev branches. The concept of branches in bzr is a little bit more, we can't forward patches on branches with uncommitted code, which is a pain (darcs does this magically if the patch concerns untouched files). The concept of selective pull/push is a great help, too.

I used the pretext to upgrade Trac to 0.12 (migrated from 0.11.7 which was in production only since a few days, migrated from 0.11.1).

Everything seems to work very fine (at least in Trac), but I haven't commited since darcs migration. I will do in the next hours.

Milestones cleanup

I re-ordered and renamed milestones, to make them stick better to real life. All new bugs have been accepted.

I'm now using bzr with quite comfort, and have taken back full use of geany and regexer, which I haven't used for a year (I never stopped using GVim, even under Windows and Mac OS X ;-) ).

Starting bugfixing now. In fact it has already started, since I merged external bugs reports before working with trac.

Work has (re-)begun

I'm back at Licorn® coding after nearly a year of sleep. Many things have evolved since then and I'm coming back with shining new ideas.

First I will merge the new WMI, which has fewer bugs and is more pretty than the old. I will be learning bzr during this period (branching, pushing, merging).

Then I will improve daemon internals, execute pylint and fix bugs.

Then fully implement the keywords part (internals and GUIs), in parallel of other tasks (client, cluster...). Not a prioritary task, but this will add a killer feature, IMO.