I’ve been using CVS for revision control for quite some time for a number of different things here, not the least of which being a public repository of scripts and miscellany that I have tossed into the Internet for public consumption. Recently I have started to feel the desire to change to one of the newer version control systems out there. Git and Hg smell a lot of ‘ooh shiny’ syndrome and we use Subversion at work so I was sort of naturally drawn towards Bazaar. It doesn’t help that I’m a huge fan of Canonical and Ubuntu, and as that seems to be the VCS du jour over there these days I figured that this would give me a good excuse to learn it.
The moral of this story as I’m sure no one cares why I chose which VCS is to say that any of the code hosted on my CVSweb and linked to in one of my previous posts is likely to have moved to the new loggerhead interface over at repo.ub3rgeek.net. If you happen to follow me on FriendFeed or watch the home page here, you will see updates from my bazaar commits as they happen.
Fancy, eh?
Tags: blackberry, programming, python, software, technology
I just moved us from 90/10 CVS/Subversion to a git-based model and couldn’t be happier. My experience is that Subversion is a “sort of better CVS” but still suffers from many of the same fundamental flaws as CVS and doesn’t really provide enough of an improvement to justify the migration from CVS. Git was really compelling — the move has already had a profound improving impact on our development workflow and I think the discomfort of the migration has been worth it.
If you ever feel so motivated, I’d encourage you to give it another look. It’s a powerful tool and there’s more too it than just ‘rails’-style meringue enthusiasm.