Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>In my experience, relying on SVN merge in stuff like you're going to do (heavy refactoring) the way you're going to do it (working in branches) turned out <strong>extremely</strong> counter-productive.</p> <p>Per my recollection, doing things that way lead to developers wasting about 1/4 if not 1/3 time on fixing regression bugs introduced by SVN merge (we've got these estimates from <a href="http://en.wikipedia.org/wiki/JIRA" rel="nofollow noreferrer">JIRA</a>).</p> <ul> <li>When I first noticed that issue my initial assumption was that this is just a matter of <em>learning curve</em> - I expected that after gaining sufficient experience we will discover how to do it right. Unfortunately, even after several months of working with the project, "waste rate" steadily kept as high as in the beginning.</li> </ul> <p>Our way out of this mess was to change branching strategy (search the web for something like <em>version control branching strategy</em> if you're interested). Strategy we changed to was <em>unstable trunk</em> (this is also searchable term in case if you're interested). That switch required quite noticeable efforts to prepare and some changes in dev process (more on that below) but overall the result turned out more than satisfactory - IIRC <em>waste rate</em> dropped by more than 4x.</p> <p>Most notable of <em>changes in dev process</em> I mention above are regular "checkpoint" trunk releases and regression test cycles. We introduced these to act as a replacement to natural checkpoints which were previously enforced by merges.</p> <blockquote> <p>...or do I need an external tool?</p> </blockquote> <p>That option looks worth considering, too. I remember discussing SVN merges issues with an ex-colleague some time after my project switched to <em>unstable trunk</em>. He told me that for his current project, switching to better merge tool made a big difference.</p> <p>Back then I was happy enough with what we had so I didn't mark what tool he referred to. Though there seem to be plenty related discussions at SO, for example:<br> - <a href="https://stackoverflow.com/questions/572237/whats-the-best-three-way-merge-tool">What&#39;s the best three-way merge tool?</a><br> - <a href="https://stackoverflow.com/questions/218053/tools-for-svn-merging">Tools for SVN Merging</a><br> - <a href="https://stackoverflow.com/questions/50371/better-merge-tool-for-subversion">Better Merge Tool for Subversion</a></p> <hr> <p>PS. And, no matter how you work around merging issues, having a comprehensive and easy to use set of tests would be really helpful</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload