Team packages maintained in bzr, one branch for the team or one for each debian directory?

[Alexander Sack]

On Sat, Jul 28, 2007 at 05:28:35PM +0200, Sebastien Bacher wrote:
> 
> The team contributors are likely to work on different packages and I
> think it would be easier to have everything at the same location.
> 
> Daniel has written a "get-branches" tool to make easy to get or update
> all the branches from a team, it has to connect and do checkout for
> every package though which is quite slow and quite verbose.
> 
> 

Are there features we get from putting everything into a single bzr
branch that we cannot easily get from improving the get-branches tool?

If not, I don't really see the benefit from putting everything into
a single tree.

 - Alexander