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

Repository Configuration Question

From: <dkrobbins_at_micron.com>
Date: 2005-02-14 19:21:01 CET

My company recently selected Subversion as our new source code control
tool. We have several hundred developers spread around dozens of
departments. I've been playing around with the tool and I am starting to
understand some of the basic functions. However, I'm not getting a good
feel for how the repositories should be configured. I am thinking of
setting the repositories up like svn\repositories\<department>\<group>,
for example:


One question is should projectA and B be repositories or just
subdirectories under the group1 repository? Project A & B do not need to
share files, so I would initially say repositories, but if we did that
company wide, we'd have thousands of repositories. Should that be a
concern? If we go with them as subdirectories, then our concern is that
we have repositories with thousands of revisions, which might confuse
users (the revision of my project changed, but I didn't make a change)
and be inefficient.

One other question that came up is whether or not hosting the
repositories on Windows is a bad idea or not? Most of our experience is
with Windows servers, so we are leaning that way. However, if there are
performance and stability issues on that platform, our minds could be

Any other tips, tricks, or advice would be appreciated. Thanks.

Received on Mon Feb 14 19:24:10 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.