basic usage questions

[Gábor Farkas]

hi,

i'm trying to work with bzr.

previously i have been using centralised version control systems, like 
cvs or snv.

i installed bzr,

went to the folder where i'm developing, did a bzr init, and started to 
use it. everything works fine.



but i still cannot "imagine" the development process with such a version 
control system.

for example, imagine that 3-5 people are working on a project.

in a svn/cvs world, they access the central repository, and commit their 
changes to that repository.

how is something like this achieved with bzr?

i understand that there can be a central repository,from wich everyone 
gets a copy (a branch), and works on it, committing to his own branch.

but then, when they are finished with a change, how does that change 
arrive back in the main branch?

i know that you can "push" your changes using sftp or rsync... but isn't 
it simply a copy of your repository?

let's describe a simple scenario:
2 developers, A and B, one central repository C.

A checks out a copy of C, and starts to work on a feature.
B also checks out C, and starts to work on a feature.

some time later, when the feature is completed, A would like to update C 
with his changes. how should he do it? should he simply rsync/sftp to C?
but then, what happens when B wants to update C with his changes? his 
"update" won't remove A's changes?

or the workflow is completely different in the case of bzr?

sorry for the long mail, i just would like to "grasp" this concept, and 
i still feel that it escapes me...

i've read http://bazaar.canonical.com/SVNPerspectiveOnBzr, but it did 
not help unfortunately...
my problem with that document is that he always talks about "merge from".

what i don't understand is how "merge to" happens :)

or there is no "merge to"? meaning that there's no central repository, 
but someone has to kind-of "own" the central repository and "pull" the 
other developer's branches changes into it?


thanks,
gabor