> From: SI COM [mailto:sicom007@yahoo.com]
> Sent: Thursday, October 25, 2007 7:20 PM
> To: users@subversion.tigris.org
> Subject: Comercial Users of Subversion
>
>
> All:
>
> I know a lot of folks have asked this before, but I am going to do it
again.
>
> I am part of the SCM team that is evaluating a replacement for VSS and
> Subversion is one of the choices at this point. So here are the
questions
> that I have:
>
> 1) We are a financial services company with almost all groups (other
than
> software development) using a SCM tool. Will Subversion be good for
> non-technical users esp. with not a lot of UI tools available?
If they're not doing merging, then SVN should be easy enough to use.
Otherwise you will need to train merge-meisters due to SVN's lack of
merge tracking, lack of true renames, and several merge bugs resulting
thereof (bidirectional merges, merging renamed files.) SVN 1.5 will
include merge tracking and true renames, but there's no official date
yet beyond maybe Q108. In the meantime, you can use the snvmerge.py
script, but IIRC, it doesn't check subdirs for merge info, and you still
need to address merging renamed files.
If you use short lived branches, then the merging issues are not much of
a problem. If you have long lived branches and do a lot of up/down
merging, then you're really going to need trained merge-meisters.
If they're running Windows, then just use TortoiseSVN. The command line
is pretty easy also.
Initially, people may have trouble wrapping their heads around SVN's use
of change sets, that there is one and only one version number, and that
labels are just branches.
> 2) We have invested a lot in creating push button builds ( any user
can
> create a build from a web page) so how good are the APIs that
Subversion
> provides?
The APIs are good. The command line was also designed to be easily
parsed (and most command line options include a --xml format option
(however, it's much faster to parse the text than the xml for commands
like 'svn log'.)) Therefore scripting/automation is easy.
However, the hooks/triggers run only on the server. Therefore you have
no visibility into and no control over the client, which can make it
difficult to enforce policy and/or standardize things (such as EOL type,
requiring appropriately formatted merge info in the comments, client
version, etc..)
> 4) I saw somewhere that paid support is available for Subversion. Can
someone
> please tell me where I can find that information.
Last I checked, Collabnet provides support.
*****
The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA621
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 26 15:46:54 2007