Re: Subversion 1.5

Irvine, Chuck R [EQ] wrote:
>
> If I had heard that the current implementation of renames can and
> probably will lead to code loss (from the latest revision), my reaction
> would have been much different. To me, probably the first rule of source
> code management is "thou shalt not lose code".

No source control mechanism can prevent code loss at the latest revision
if someone commits changes that cause it. What the revision mechanism
provides is a way to get back any older version ever committed.

> At this point we have adopted it as our standard tool, moved
> applications to it, bought 24x7 support, etc, so we are committed and
> will have to figure out how to avoid losing code.

Develop on the trunk and branch for releases. That should make it a
rare case that you ever have to merge refactoring-type development work
back from a branch to the trunk where someone may have concurrently
added things to a file that has been renamed/replaced on the branch.

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org