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.
>
> 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).
That's exactly what we're doing now; we couldn't be any happier! I've
read others people arguments about its con, however for a small team of
people and for many small changes it is too much work to have more than
one step ("file save") to have the changes availabe to test on some
webserver.
Every major changes are commited, conflicts, due the small team, are a
non-issue.
thanks evyerone for sharing his idea, sincerly,
- Markus
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Aug 30 12:50:22 2004