Jeff Squyres wrote:
> 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.
This EXACTLY What I do, BUT what you are describing in not a common
'working' directory.
The rule here is absolutely NOBODY EVER edits that directory tree
directly, the ONLY way it's
ever changed us thru and SVN update.
What they were talking about, applied to your situation, was to pretty
much just letting everyone have at your
live web directory and long as they commit regularly and skip all the
'complexity' of individual working copies.
Marc
---------------------------------------------------------------------
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:47:00 2004