Posts in category migration

dev.licorn.org migrated to a dedicated server, Licorn® project using Git and GitFlow

After some years of mutualized hosting, dev.licorn.org is now living on its own on a brand new Ubuntu 12.04 LTS server. It lives in a dedicated LXC container; the hosting machine is fully dedicated to the Licorn® project, running docs.licorn.org in another LXC, and many more things I wanted the project to have (a build machine, etc).

Meanwhile, we have switched from darcs to git. Having encountered the  fatal #1520 bug has urged us to do so, because this bug just prevents us from working. But it's really the tip of the iceberg, because I wanted to switch to Git for a long time.

Even better, we now officially use  GitFlow to follow the famous  successful Git branching model, and I'm very happy with this clean approach.

Things will only go better now ;-)

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.