multiple developers commit different files to same bound branch

[Colin D Bennett]

On Thu, 08 Jan 2009 09:22:48 +0100
Vaclav Bilek <vaclav.bilek at e-comsystems.cz> wrote:

> Thank you for your comment.
> 
> You are right that I am coming from CVS (and later SVN) world.
> The reason why I look for the solution I described is folowing:
> - my development team is about 5 to 7 people
> - we process working trees of sizes about:
>     - 1000-20000 files (structured in balanced directory tree)
>     - the total disk space occupied (by working tree) is about 15GB
>     - every project has about 3 working trees in parallel (three
> developers)
> - there are about 5 projects like this per year
> - the number of commits in each project vary from 300 to 2000 per
> project
> 
> And that is the reason why is very hard (because of the disk space
> and the time) to have for each developer his own branch.

I think you will find that giving each developer his or her own
branch (and probably the option to have multiple branches for a
variety of purposes) is useful, and it will not use much disk
space in the repository (make sure the central repository is using
branches *without* working trees).

Having multiple related branches in a shared repository takes very
little extra space. Bazaar is smart and does not duplicate every file,
so you can have 100 different developer branches based off of the same
trunk branch, and it will hardly take any more space.  This is why we
say Bazaar has "cheap branching."

Regards,
Colin