Is SVN ready for use?

[Roman Rytov <rr...@entopia.com>]

I played a bit with SVN and have to confess it impressed me. But since
there is no edit-related commands I doubt whether it's ready for
production usage? I mean how do developers work together w/o knowing
that a file is "checked-out"? Maybe in the open-souce world it's not
really important since exclusive lock doesn't exist but inside a team I
can't rely on carefull manual merging (I mean I don't want to oblige
people to ever think about it). How do you work it around? I saw
edit-related commands are in the list far behind the release. 


Roman Rytov

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Is SVN ready for use?

[Ben Collins-Sussman <su...@collab.net>]

Karl Fogel <kf...@newton.ch.collab.net> writes:

> "Roman Rytov" <rr...@entopia.com> writes:
> > really important since exclusive lock doesn't exist but inside a team I
> > can't rely on carefull manual merging (I mean I don't want to oblige
> > people to ever think about it).
> 
> What happened when you tried the non-locking model?

Subversion is first and foremost a concurrent system.  Roman, you
should read chapter 2 of the Subversion Book to understand the
philosophy:

   http://svnbook.red-bean.com/book.html#svn-ch-2


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Is SVN ready for use?

[Karl Fogel <kf...@newton.ch.collab.net>]

"Roman Rytov" <rr...@entopia.com> writes:
> really important since exclusive lock doesn't exist but inside a team I
> can't rely on carefull manual merging (I mean I don't want to oblige
> people to ever think about it).

What happened when you tried the non-locking model?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org