Branching with a Central Repository

[A. S. Budden]

2009/10/6 A. S. Budden <abudden at gmail.com>:
> Dear all,
>
> We are currently looking to move over to Bazaar at my workplace.  Due
> to the way work is backed up and shared, we will be using the central
> repository approach [1] mostly, such that everyone uses checkout to
> get projects.  The initial plan for a repository layout (no working
> copies) is:
>
>    root\ProjectGroup\Project1
>    root\ProjectGroup\Project2
[snip]
> Is there a better way to do this?  I've been reading the
> documentation, but most of the branching/merging discussion focuses on
> the distributed development workflow.

Many thanks to everyone for the answers: I've been experimenting with
this and it looks really promising.  I've adopted the shared repository
being Project1 approach and it seems fine.  Will this still work when
Nested Trees are implemented and the library modules are in a separate
repository?

I probably prefer working without the trunk folder, but I can certainly
live with it for the benefits of:

    bzr switch -b feature-gui

It'll be really nice when merge supports the relative paths and the
Explorer GUI supports this workflow.

I like the idea of the ^/... type of path (this would allow the nested
style of repository layout), but I must agree that the choice of prefix
needs to be chosen very carefully (and definitely not ~).

Many thanks again to the wide set of answers: I'll spend some time
experimenting with this before we roll it out to the department.  Oh,
and thanks again for a fantastic VCS!

Al

-- 
http://sites.google.com/site/abudden