&gt; Furthermore it&#x27;s mostly a rant against subversion rather than going making any kind of argument about his assertions.<p>A completely misguided rant at that.  The author even admits it: &quot;To be fair, you can adopt this workflow with Subversion, using either task branches or patches...&quot;  This is exactly how my team uses Subversion (and used CVS before it; yes, we used this exact &quot;branch per issue, code review before merge&quot; workflow with CVS up through 2013) and we don&#x27;t find the overhead of branching and merging onerous.  Granted, I haven&#x27;t ever tried contributing to an open source project using SVN, but arguably Git is the more-correct tool for that kind of development anyways.