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

RE: Re: I, too, miss tags.

From: Rob van Oostrum <rob.vanoostrum_at_blastradius.com>
Date: 2006-02-27 16:56:06 CET

> -----Original Message-----
> From: Saulius Grazulis [mailto:grazulis@ibt.lt]
> Sent: Monday, February 27, 2006 4:44 AM
> To: users@subversion.tigris.org
> Subject: Re: I, too, miss tags.
> A system must be clear and simple to be
> adopted :(.

And that is the crux of the matter right there. There is very little
about SVN that should have to be "clear and simple" in order for it to
be adopted. SVN is NOT Windows/Word/dare I say VSS. It, as is any other
enterprise-grade SCM, first and foremost a complicated tool that is
invaluable in the hands of people who know what they're doing. It is
certainly possible to set SVN up to be usable for non-technical types
(project managers etc) but that would generally only include basic
checkout/update/commit usage profiles through a point-and-click client
such as TortoiseSVN.

If you need an all-around "clear and simple" SCM, SVN is probably not
it, though it can certainly be setup to be simple. Its advanced features
are however not for the weak of heart, nor should they be. What you find
"ad-hoc" or obscure or unclear, I and many others find powerful and

It's entirely common for IT organizations to use a "complicated" SCM for
their development teams, and VSS to allow PMs etc to store their Word
docs / project plans etc.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 27 19:01:21 2006

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.