Evaluating Bazaar in a CVS environment.

[Andy Walker]

I would like to evaluate Bazaar in the development environment where I work.

We are currently a CVS shop, and have a massive centralized project managed by
CVS.  The plan is to move to something better soon, and I would like to evaluate
Bazaar for this and collect my experiences for review.

I would like to run Bazaar to manage my workflow on a bug-by-bug basis for now,
but I'm having some difficulty with the terminology and how to set this up. 
Perhaps I am improperly understanding when branches should be used and when they
shouldn't.

Ideally, I would be able to create a branch for each bug that I'm working on in
order to edit the files with impunity.  The catch is that this source tree is
really large, and I don't want to be copying the whole thing each time I start
to work on a bug.  Ideally, I'd be able to have a branch that only contains the
modified files that relate to a particular task or bug, and then, upon
completing my work, merge that branch to the "trunk" CVS-controlled directory
and issue 'cvs up'.

Based on my current understanding, I should create a "work" or "code" directory,
and issue 'bzr init-repo --no-trees" in that directory.  Then I create a
directory for this main work project called HEAD, and copy the highest level of
the CVS tree that I will be working on into that directory.  Then I 'bzr init'
HEAD, 'bzr add' and 'bzr commit' the initial revision.