Describe your workflow

[Colin D Bennett]

On Wed, 25 Jun 2008 22:19:15 -0400
"Spencer Chastain" <sechastain at gmail.com> wrote:

> We recently moved my development team (~10-14 core developers, many
> internal customer user/developers, distributed across multiple sites)
> to bzr.
> [...]
> Our project regularly requires that you be testing on multiple
> machines at once - and not all test machines have access to the same
> filesystems.  So we encourage our developers to make use of checkout
> in this case, though I'm wondering if a pull/up-load system may work
> better.  There does seem to be some level of unneeded overhead when
> you want to keep 2 branches synched. Trying to educate my developers
> on what they're doing and why they're doing it seems ...
> overburdensome.  It's an easy concept, it should be an easy
> use-case.  Maybe I'm missing something.
> [...]
> I do think it could be made simpler - specifically,
> keeping two branches in synch.  Making this simpler would make the
> lives of some of my developers simpler as well.

By "keeping two branches in synch", what do mean, specifically?
Do you mean that you have two related branches (let's call them A and
B), you make different commits to each branch, and then you want to
merge the changes to A into B and the changes to B into A?

Regards,
Colin