While reading this it struck me as well that he was describing a perforce workflow, not subversion.
Re:The Subversion Mistake
by bluedanieru on Tuesday April 19, 2011 @03:24AM
(#2461923)
I didn't know Perforce at the time so I couldn't comment. I learned it later on which helped to understand that side of it. Still doesn't explain why they thought they can switch to a different tool but continue the same workflow as with the previous tool. (I can certainly explain that part but it would be out of context here, heh.)
The most frustrating aspect was it seems that, while far from perfect, using Subversion as intended, in your case and ours, would be 1/10th as painful even while introducing a few issues of its own. The explanation I always got was "long before you came on board we used Perforce but we switched to Subversion because it's open source but we still want to use it like it's Perforce." You seem to have reasoned about your change quite a bit more than this, so I'm interested in hearing why you think you need to do things this way.