The issue of version control is central to many multiperson software projects. You need some hopefully simple way of handling crucial issues like committing and then [oops!!] rolling back. Bazaar is a recent solution that appears easy to learn and use. Gyerik describes the basic operations and also gives us a useful summary of other major version control systems out there. One thing you'll readily see in the book is that there is an emphasis here on free code packages, including Bazaar, understandably. There is a certain tradeoff with Bazaar. Unlike a central version control method, it is distributed. This means each person on a project has all the revisions; ie. all the earlier versiosn and the present working version. Some readers might cringe at the duplication of code. But these days, if what is being stored is source code, or text documents, then the inefficiencies implied might not be material. Note one disadvantage of a distributed method. The very raison d'etre of each person having all the revisions means it might be [or likely will be] hard of impose any security compartmentalisation between the users. There is an implicit assumption that all the users can be trusted with everything you put into a project. For a project that will be distributed across users in different countries or companies, this might sometimes be problematic. Ok, you could think this is an edge case. But keep it in mind. Small teams within a startup, say, won't find this an issue. But a large corporation concerned with doing outsourcing of some of its development needs to be aware. The text is good at not just explaining using Bazaar by itself but also in a collaborative development environment [CDE]. One chapter suggests how you can incorporate it with common CDE tools like Launchpad, Redmine, Trac and Loggerhead. One common property of those 4 tools is the web based access. Clearly, the browser metaphor has become dominant even in a programming workplace.