Re: How many repositories question

Its really a matter of taste... If the client code shares nothing I common with each other the you probably would want multiple repositories.

Keeping things in one repo let's you merge certain changes between clients... It simplifies management of the repository, especially if you have the same access rules for each repo.

There are some cons to keeping thing in one repository. The bigger it gets, arguably the slower it gets. I have nothing to support this, just a gut feeling. You can't delete things from the repository other then using the clunky svndumpfilter. If you have a client who leaves, his project will forever be in the repository taking up space.

Other then that, I can't think of any good reasons to have separate repositories.

Russ
Sent wirelessly via BlackBerry from T-Mobile.

-----Original Message-----
From: "Jiho Han" <jhan@InfinityInfo.com>
Date: Fri, 10 Nov 2006 16:28:55
To:<users@subversion.tigris.org>
Subject: How many repositories question

Should each project get its own repository?

What I mean is, if you are for example, a consulting company and has
many clients and for each client you might have one or more projects.
I am wondering whether there should be a repository per client.

Or if you have multiple product lines, (not different editions but
completely different lines), would you create a repository per line?

Jiho Han
Senior Software Engineer
Infinity Info Systems
The Sales Technology Experts
Tel: 212.563.4400 x6375
Fax: 212.760.0540
jhan@infinityinfo.com
www.infinityinfo.com <http://www.infinityinfo.com/>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 11 02:58:56 2006