-----BEGIN PGP SIGNED MESSAGE-----
I've voted with 1 repository per project.
If a repository with 1,000 projects in it gets hosed, you'd lose 1,000
If a repository with 1 project in it gets hosed, you'd lose 1 project.
Even with backups, do you want the developers of 999 projects waiting
restore a repository to fix an issue with 1?
On Feb 14, 2005, at 10:21 AM, email@example.com wrote:
> 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 changed.
> Any other tips, tricks, or advice would be appreciated. Thanks.
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Mon Feb 14 21:10:32 2005