bazaar - a distributed VCS or a new spin of the old RCS
Like most people of my age, I graduated from RCS, to CVS, then to Subversion. Recently, a friend of mine implemented bazaar on production servers at work and urged me to check it out.
I did.
- It is written in python. some modules are written in C for speed.
- functions are pretty much complete, yet the control of publishing is more of a P2P model.
- Bazaar’s notion of personal branch is appealing. Any user can just start a branch and the repository database is stored in a directory named ‘.bzr’ right there, in the working directory. This sounds scary, for sys admin and release manager alike who are more used to centralized RCS (revion control system). Yet, such a concept is really similar to what you do in the old RCS, you make a directory named ‘RCS’, then start to check in (ci) and out (co) . If you don’t make a directory named RCS, the revision db file will coexisting with your working copy.
- I don’t like the fact the revision db is right there with the working directory.