|
2977.1.6
by Ian Clatworthy
first cut at Central development chapter |
1 |
Centralized development |
2 |
======================= |
|
3 |
||
4 |
Motivation |
|
5 |
---------- |
|
6 |
||
7 |
Rather than working in parallel and occasionally merging, it can be |
|
8 |
useful at times to work in lockstep, i.e. for multiple people to |
|
9 |
be continuously committing changes to a central location, merging |
|
10 |
their work with the latest content before every commit. |
|
11 |
||
12 |
This workflow is very familiar to users of central VCS tools like |
|
13 |
Subversion and CVS. It is also applicable to a single developer |
|
14 |
who works on multiple machines, e.g. someone who normally works |
|
15 |
on a desktop computer but travels with a laptop, or someone who |
|
16 |
uses their (Internet connected) home computer to complete office |
|
17 |
work out of hours. |
|
18 |
||
19 |
If centralized development works well for your team already, that's |
|
20 |
great. Many teams begin using Bazaar this way and experiment with |
|
21 |
alternative workflows later. |
|
22 |
||
23 |
Centralized workflow |
|
24 |
-------------------- |
|
25 |
||
26 |
The diagram below provides an overview of the *centralized workflow*. |
|
27 |
||
28 |
.. image:: images/workflows_centralized.png |
|
29 |
||
30 |
Even if your team is planning to use a more distributed workflow, many |
|
31 |
of the tasks covered in this chapter may be useful to you, particularly |
|
32 |
how to publish branches. |