Re: general subversion theory for developers?

On Wed, 2004-01-07 at 04:33, Sean Moss-Pultz wrote:
> They say to give everyone their own
> "sandbox", by making a branch for each user, and then one admin merges
> all the changes back to the trunk, creates all new branches (or they
> can update theirs) and the process continues forever in this manner. Do
> any of you guys use a method that you feel works particularly well? I
> would love some guidance.

I've never worked this way, but personally, it sounds a bit cumbersome
to me. If each developer is working on a private branch 100% of the
time, there's a *whole* lot of merging going on. Not only merging N
branches to the trunk, but merging the trunk back to N branches again.

I think the Subversion project has a very good model:

  * everyone has a working copy of trunk.

  * trunk must compile and pass regression tests at all times.
developers that break this rule are publically humiliated. :-)

  * if your change can be done in a single reviewable commit, then just
commit to trunk.

  * if your change needs many commits and/or might destabilize or break
code, then do the commits on a temporary branch.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 7 16:59:25 2004