| |||||||||||||
A proposed Subversion vision and roadmapA proposed Subversion vision and roadmapPosted Apr 4, 2010 19:01 UTC (Sun) by xxiao (subscriber, #9631)Parent article: A proposed Subversion vision and roadmap
For people like me that have to use accurev at work, svn vs. git comparison is pointless, both are superior. Accurev is for project managers, not for developers.
What I do is to git init the accurev stuff and work from there, only use accurev when I need 'promote' my patches to the repo on the server.
(Log in to post comments)
Indeed Posted Apr 11, 2010 16:08 UTC (Sun) by man_ls (subscriber, #15091) [Link] True, and Accurev can make your really shitty workflow a reality. With other tools you just end up with such a gigantic mess that your workflow will probably have to be simplified (and developers' lives made considerably funnier to live) just to cope; but Accurev makes it all possible. Therefore, it's a good example of how manageability can sometimes become a bad quality.
A proposed Subversion vision and roadmap Posted Apr 12, 2010 14:37 UTC (Mon) by blottfish (guest, #65212) [Link]
@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...
A proposed Subversion vision and roadmap Posted Apr 12, 2010 23:40 UTC (Mon) by bronson (subscriber, #4806) [Link]
Sounds like Accurev discovered LWN.
So it's like serving Chinese, Italian, and burgers all in the same restaurant? Wonderful. Does it also read mail?
A proposed Subversion vision and roadmap Posted Apr 13, 2010 16:32 UTC (Tue) by blottfish (guest, #65212) [Link]
AccuRev didn't discover LWN; AccuRev merely discovered someone with a very narrow-minded viewpoint on a certain subject. That can happen anywhere, not just in the Linux community. Google alerts does not discriminate, nor does this poster.
And your analogy is close, once I offer a minor correction. Instead of serving those cuisines in the same restaurant, AccuRev is indeed like being able to offer those choices, only it's in a Food Court, where all patrons are able to find something that suits their (change) palette, and all can happily co-exist!
Look, every tool isn't going to be for every organization. You choose the one that best fits your needs. My problem was with the premise that the ideal solution was to dumb down the process simply on the assumption that complexity automatically leads to trouble. Which it can, with most tools, if not managed properly. Just not AccuRev...
|
|||||||||||||