Re: Need ammo against those who say "lock everything"

> When you've made a change C in your workspace,
> you need to integrate it via an algorithm that
> looks something like the following:
> checkout tree
> make change C
> loop
> test it
> if tests pass, break loop
> fix
> end loop
> loop
> update from mainline
> test it
> if tests pass
> if there has not been a change
> checkin
> break loop
> fi
> fi
> end loop
> You can short-circuit some of these steps,
> but the above is pretty much what you want to do
> if you want to guarantee that only code that
> passes all tests is checked in.
> Unfortunately, the above process is
> NOT guaranteed to terminate.

For an article that still supports copy-modify-merge
but which also discusses several different locking
mechanisms for ensuring the above DOES terminate
(without resorting to file-locking) take a look
at "Codeline Locking and Merging: Continuous Update,
Two-Phased Commits" at:
   http://www.cmcrossroads.com/newsletter/articles/agilenov03.pdf

-- 
Brad Appleton <brad@bradapp.net> www.bradapp.net
  Software CM Patterns (www.scmpatterns.com)
   Effective Teamwork, Practical Integration
"And miles to go before I sleep." -- Robert Frost
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org