RE: Re: Strategies for projects/branches layout

Hi David --

> There is a third option, which is the one I chose when
> migrating from VSS:
>
> /project_repository/trunk
>
> The advantage is that it will look like you described your
> CVS layout to
> be - each 'module' becomes a repository with distinct
> versions, tags, etc.
> The disadvantage is you can't enumerate all repositories on a server,
> only directories within a repository. So that makes it a little more
> awkward, but I think the benefits far outweigh.

Problem with this is redundancy, particularly if I want to assert that
all the "modules" in a repository are accessed by the same group of
people. For example

  Repository: "CLIENT_A"
  Modules: "PROJ_1", "PROJ_2", "PROJ_3", "PROJ_4", "PROJ_5"

This way I can set UNIX permission such that all users who work with
Client A have access to all the projects.

My question is thus: Is it better to put "branches", "tags", and
"trunk" directories at the repository level, or at the project level?

Warmest regards,

-Jesse-

--
 
Jesse Erlbaum
The Erlbaum Group
jesse@erlbaum.net
Phone: 212-684-6161
Fax: 212-684-6226
 
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org