A proposed Subversion vision and roadmap

@man_ls, are you serious??? Saying that a tool which allows you to implement any workflow process you want is a bad thing is like being against a restaurant having more than one item on the menu. Talk about _catering_ to the lowest common denominator! To carry that analogy further, someone who doesn't like tacos keeps coming in to the restaurant and ordering tacos, then turns around and blames the restaurant for offering them on the menu in the first place.

AccuRev indeed will support whatever workflow you desire, as opposed to forcing one or a few upon you. Typically, when you migrate to AccuRev you take the golden opportunity to optimize that process. Even if you stick with the "broken" process in AccuRev, it will be still be far more manageable, as you even indicate yourself by saying you'd be forced to simplify in your "old" tool to avoid the gigantic mess. And you'll have the opportunity to dynamically change your process as you learn how to take advantage of the new power AccuRev provides. Try doing that in a branch and label tool.

I don't mean to take you to task individually, it's just that the premise of "don't use a tool that can help you because you'll invariably screw it up" is defeatist. There are tens of thousands of developers happily using AccuRev, and at an individual contributor level, it doesn't get any simpler. If the higher-level process is screwed up, someone in the organization needs to take responsibility and fix it; fortunately, with AccuRev that's possible...