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

Re: Multiple users working on the same checkout

From: Jeff Squyres <jsquyres_at_lam-mpi.org>
Date: 2004-08-26 00:34:34 CEST

We have a case where multiple developers sharing a single checkout is a
good thing -- the live docroot on a web site. We all develop in our
own, separate checkouts, but when we hit a stable point (which is
actually quite frequently), someone has to go do an "svn up" in the
live docroot. This is also, obviously, an SVN checkout.

Because of our workflow and the nature of our changes to the web site
(little changes in unrelated files -- it's a large web site and little
pieces of information change all the time), it really makes sense to
allow anyone in the group to be able to do an "svn up". The other
obvious alternative is to have only one person be able to do the "svn
up" in the live docroot -- which is the way it has to be now -- but
this has led to major bottlenecks.

So at least for our workflow, having a shared checkout makes sense and
would actually save work (hence, my e-mail earlier today about how the
problem doesn't seem to be solved in SVN 1.1rc2).

On Aug 25, 2004, at 6:17 PM, Thomas Harold wrote:

> Alex Martelli wrote:
>> On 2004 Aug 24, at 15:33, m christensen wrote:
>>> I'm sorry, but the whole idea of multiple people working on a single
>>> tree is
>>> counter to the whole concept of change management and effective
>>> revision control
>>> IMHO...
>> It's exactly the philosophy both CVS and SVN are based on. If you
>> want lockout-based systems rather than conflict-pinpointing ones, you
>> know where to find them. As for me, having sweated far too much
>> blood with ClearCase with a previous employer, I'll take CVS (or
>> better SVN) over it any day.
>
> I think they were talking about multiple people editing files in a
> single working tree. Where there's a common working folder up on a
> network share, rather then each developer having their own individual
> working folder.
>
> I was always told that each developer should have their own individual
> working folder (either on their hard drives or in their home/user
> directories). And that's the way I have our current source control
> system setup. All of our developers are in different towns, so it's
> not like we could use a shared working copy even if we wanted to.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>

-- 
{+} Jeff Squyres
{+} jsquyres@lam-mpi.org
{+} http://www.lam-mpi.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 26 00:34:56 2004

This is an archived mail posted to the Subversion Users mailing list.