[EMAIL PROTECTED] wrote:
> How should I set up
> my repository to best benefit the development/management effort?
> should we have multiple repositories? each repository represents one of our
> clients. or should we have just 1 repository, define multiple
> modules and each module represents one client/project combination?
My company has played around with various approaches. We started out
with the one-repository-many-modules model, which we didn't particularly
like for some reason that now escapes me, and then moved to a
one-repository-per-project model. I don't really like that either.
Finally, it looks like we're settling on a
one-repository-per-functional-group model, so the infrastructure group
has their own repository with potentially several modules in it, the
client-facing teams have their own repositories with potentially several
modules, and so on.
Hope that helps.
Cheers,
Laird
