Bazaar recommended practices

[Talden]

> I think it would be useful if there was a section in the wiki where
> experienced users could explain in detail how they used bzr within
> workflows so that new users could see some alternatives.

Though I haven't used Bazaar in anger yet I've done a fair bit of
experimentation looking at how we might migrate from a CVS system to
Bazaar in the future (probably via Subversion in the meantime).  I
looked for good guides and, somewhat like Subversion, Bazaar seemed to
just say 'whatever your workflow you can do it' - which (a) isn't true
- some things aren't supported, and (b) not all 'supported' workflows
are practical.

I came up with the following for a hypothetical developer X who is
able to check into the official branch.

Setup
1. Create a treeless repo
2. take branches of the various 'official' branches of interest as
local mirrors.

Work on an issue
1. Branch from a recently pulled local mirror and checkout (create a
working tree)
2. Hack, commit, hack, commit
3. If necessary, merge from a recently pulled local mirror.
4. build & test to get ready to deliver.

Delivery
1. Create (or update) a checkout of the official branch to deliver to
2. merge in your work branch
3. review and commit.

This seems to produce the most sensible revision history in the
official branch and makes good use of a repository and treeless
branches to have nice and cheap local branching, diffing etc.

I have no idea whether this is a common usage or whether there's some
gaping flaw in my plan... It would be great to have 'from the ground
up' best practices.  I can imagine there are a few interesting
scenarios in which you'd definitely use bazaar differently.

--
Talden