> I was referred to this email to find out questions I have about
> Subversion. We're doing an analysis of different source code
> config. Mgt. applications and we have a list of requirements that
> must be met before we make our selection. Would you be able to
> fill out this document for whether Subversion meets these
> requirements and preferences, or point me to someone who can?
The answer to every one of your questions is a yes, but in some cases
it's a qualified yes. Some features, such as merge may not be as
robust as you'd like, and many features either require the use of a
second program (e.g. TortoiseSVN for Windows GUI) or require you to
do some script programming to set up the appropriate hook scripts to
be run in response to SVN events such as commit (e.g. to prevent
commits with empty logs). You will also find that much of the
terminology that Subversion uses is different from the terminology in
your document, and you will also find the way much of that
functionality is implemented foreign to the way it's described in
your document. For example, Subversion does not have "labels" but
you can create a "tag" in the form of a cheap copy (i.e. a logical
copy that doesn't require duplication of the content) and then use a
hook script to disallow further modification of said tag, which will
give you essentially the functionality that you're asking for.
I suggest reading (or at least skimming) the following two books---
both of which are freely downloadable:
http://svnbook.red-bean.com/
http://www.williamnagel.net/svn.php (full disclosure--I wrote this one)
As for your document itself, I think you're probably going to have to
fill that one out yourself. Subversion is an open source project
developed entirely by volunteers (there are some paid full-time
developers working on Subversion, but they are paid by companies such
as CollabNet who pay them to donate to the project---there is no
company that owns Subversion and directs its development). As a
volunteer project, no one really has any standing to make any sort of
binding commitment about Subversion's suitability to a certain
purpose. It's one thing to respond to questions on a mailing
list...it's another entirely to fill out an officialish document for
an unknown corporation that very well might have a legal department
that will view such a document as a full-fledged suitability
statement that could lead to them coming back on the person who
filled out the document with a lawsuit if the company were to
implement Subversion and it led to big losses for the company due to
misunderstandings in the answers to the questions. At least that's
my opinion (and reason for not filling out your document).
Of course, if you want to pay someone to do a suitability analysis,
you might be successful.
-Bill
> Thanks for your help!
>
>
> <<Subversion Requirements.doc>>
>
> Anja Hollinger
> 703-368-6107 ext. 354
>
> <Subversion Requirements.doc>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 17 20:04:28 2006