On Mon, 7 Jul 2008 20:30:52 -0700
"Rory Clark" <roryslists_at_clarkzoo.org> wrote:
> My work is contemplating a move from CVS to a new source control tool.
> Currently on the potential "move to" list is Subversion and Team
> Foundation Server, as a few groups already use it. Since I run
> Subversion at home, there were a number of questions I was asked that
> I could not answer.
Well, obviously SVN is better than CVS. I don't know much about TFS
other than you have to pay for it and it is from MS. That's two
strikes against in my book :)
> One of the risks brought up was one person's encounter with database
> corruption in the repository. I have not seen this in my
> installations. Does anyone have an idea under what conditions, not
> including hardware malfunction, that this could cause this? Is there
> any knowledge about frequency of occurrences?
Don't use the db backend, use FSFS :). I don't think the db backend
has many problems these days, but FSFS is the default.
> Are there any Visual Studio 2005 and 2008 SCC plug in's for
> Subversion? Do you have links for them? I have found VisualSVN,
> TamTamSVN SCC, and AnkhSVN. Are there any others that you know about?
I'm in a Linux shop, so I can't comment.
> Branching and merging was brought as an issue. What are the
> complications around branching and merging that one should be aware
> of and how to mitigate those issues?
Nothing too special I would say. What do you mean by "brought as an
issue?" The one thing to keep in mind is that svn just knows files.
branches, tags, trunks, and mainlines are just directory names. Now
that 1.5.x is out with merge tracking built in, one can say that svn
knows a bit about what a branch is.
> Integration of Subversion with LDAP and ActiveDirectory for
> authentication of users. I see in the Red-Bean book that system
> accounts over SSH on SVNSERVE are supported, but does this apply to
> ActiveDirectory on Windows based installations as well? It looks like
> we would need to run an Apache web server for this, even on Windows.
> Is this correct?
System accounts have nothing to do with accessing subversion through
http (DAV) no matter what platform you are on. I use LDAP auth with
apache on a linux server just fine. That also happens to match my
system accounts since they auth to LDAP as well.
> Does SVN support the ability to apply policies over directories? For
> example, can I limit access to specific directories under the tree to
> different groups with different levels reading and writing
> Can I take it one step further and lock down the tree
> and prevent commits to it, like in the situation where we have a
> release candidate and we don't want anyone making unapproved
Yes. Just set everyone's access to r (read-only) or put in a
pre-commit hook that blocks all commits with a helpful message.
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-08 06:07:22 CEST