7
In many cases, two minds can be better than one. You may be the one
8
who started a project and someone wishes to help, or perhaps it's you
9
who wants to help another. Perhaps you are both members of a larger
10
team that have been assigned a task together as pair programmers.
11
Either way, two people need to agree on a process, a set of
12
guidelines and a toolset in order to work together effectively.
14
Imagine if you were not allowed to call someone on the phone directly
15
and the only way to talk to them was by registering a conference call first?
16
Companies and communities that only share code via a central VCS
17
repository are living with a similar straight-jacket to that every day.
18
There are times when central control makes a lot of sense and times
19
when peer-to-peer rocks. Either way, Bazaar is designed to help.
24
While it's certainly not the only way to do it, the *partner workflow*
25
below is a good starting point for a pair of people who wish to
26
collaborate using Bazaar.
28
.. image:: images/workflows_peer.png
30
Over and above the tasks covered in the previous chapter, this
31
chapter introduces two essential collaboration activities:
33
* getting a copy of a branch
34
* merging changes between branches.
36
Even when it's just you working on a code base, it can be very useful
37
to keep multiple branches around (for different releases say) and
38
to merge changes between them as appropriate. Your "partner" may indeed
added
removed
doc/en/user-guide/partner_intro.txt
