the best way to use bazaar

[Talden]

> My general recommendation for any project that wants to have a "trunk"
> is to have the writers/developers keep 2 local copies. One which is a
> direct checkout of 'trunk' that they then merge into and commit, or
> merge from. And another which is their working version.

This is somewhat similar to how we work with Bazaar.

Master server holds branches that are published and have backup
(shared repos used for groups of related branches)

Each author then has a checkout of each master branch they're
interested in and a number of local branches in which they work.
Merges are done from local branch to master checkout.

If a branch is expected to be long running it will be pushed to the
server as a new master branch.

Currently, as we're not using Bazaar in critical work, there is little
done in controlling who can commit/push to different master branches -
naturally this is something we would do before we'd move to using
Bazaar for anything more significant.

Note that our non-use of Bazaar in critical work should be seen as a
symptom of the lack of IDE and GUI integration for Bazaar rather than
any issue we have with the tool itself.  Bazaar has so far proved to
be an excellent tool and our likely step forward from Subversion.
Tighter Windows support would be nice as well (EOL translation, better
support for case-retaining, case-insensitive file-systems).

--
Talden