[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Strategies for projects/branches layout

From: Jesse Erlbaum <jesse_at_erlbaum.net>
Date: 2005-11-07 23:16:04 CET

Hi All --

Just thought I'd get your feedback on my ultimate solution to the

> 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?

Here's what I went with -- using the example above:


  * No "trunk" directory. Seemed redundant. Whatever is in a "PROJ_X"
directory is the latest version -- aka, "trunk" (aka "HEAD").
  * No project dir branches and tags. To tag or branch I'll just copy
to the client-level directories.

The goal is to allow the projects to be "semi independent". A user can
work on just one, or on all of them. Conceivably, you could tag/branch
all the projects at once, or just one project. It seemed to be the best
of all worlds.

What do you all think? And problems you can foresee?



Jesse Erlbaum
The Erlbaum Group
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
Received on Mon Nov 7 23:18:37 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.