At 17:59 -0400 8/16/00, [EMAIL PROTECTED] wrote:
>Hi, I'm new in CVS. After reading lots of newsgroup and reading Karl
>Fogel's CVS book, I'm ready to import our corporate codes into cvs. We have
>multiple clients and each client has multiple projects. 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?
We have multiple clients, too. We have a contractural obligation to protect
their Intellectual Property, and we want to protect ours, too. Therefore,
we use different repositories for different clients. Our work processes, as
well as CVS's behavior, inhibit checking out modules from multiple
repositories under the same directory tree. This helps us avoid the
accidental mixing of IP from different places. It also lets us segregate
the development to a fixed set of machines, which we must do if they are to
be delivered to the customer.
When we have several projects from one client, we sometimes make separate
repositories for different projects, and sometimes make different modules
within the same repository. It all depends on the amount of sharing of the
code base we expect, on the whim of the project leader, and on the phase of
the moon :-).
Fred
==
Fred Brehm, Sarnoff Corporation, [EMAIL PROTECTED]
