Eeeek!
Run away from AccuCrap as fast as you can.
We migrated from AccuCrap to Subversion because it is a pile of crap.
It has this seductive model about layered streams and how you can promote
from each stream upwards.... in practice you can never trust promoting
changes will have the correct effect.
I have promoted files only to have them disappear from the stream I am
promoting into as well as from the stream I am promoting from... only to be
replaced by another version.
I ended up writing an AccuCrap to Subversion conversion utility. As this
was done on work's dime I cannot share it with the world, but I will say
this... after digging through the AccuCrap metadata, I would _never_ use
AccuCrap at all.
There are the versions that we "kept" which AccuCrap refuses to give us
back...
There are sections of our history which AccuCrap can only give a guess as to
what the repository looked like (due to problems with the metadata)
Do not use AccuCrap
-Stephen
2009/10/8 Bryan Wilkins <bryan.wilkins_at_sdl.usu.edu>
> The company I work for has been using Subversion happily/successfully for
> the past two years. A couple of months ago a new Configuration Manager was
> hired. For that last two weeks he has been “hot and heavy” into webinars and
> evaluations of AccuRev. He really thinks that it will “increase”
> productivity. The AccuRev marketing has really been selling him on their
> “stream” paradigm vs. the traditional “branches” paradigm. AccuRev says that
> that “stream” paradigm is the “way of the future”.
>
>
>
> This is a quote from one of AccuRevs Senior Developers/Marketers, how does
> the group feel about this statement.
>
>
>
> *I’d highly suggest you take a thorough evaluation of AccuRev to realize
> the true value of the technology and the benefits. I was an evaluator just
> like you…then a customer… and now a believer. I’ll never go back to a
> branch-based system [cvs/svn/p4/cc/git/etc]. Never. Streams are just so
> natural for managing software development. In the same way that OO paradigm
> trumped Functional programming, streams are trumping branches [in fact, the
> stream inheritance model is… OO….].*
>
>
>
> I would like to get some of the users group opinions on AccuRev. AccRev is
> giving our CM their opinions and thoughts about Subversion (of course they
> are biased toward AccuRev, how else would they stay in business), but what
> are yours?
>
>
>
> Are there any users in the group that have used AccuRev in past jobs and
> what are their thoughts?
>
>
>
> Another concern we have as a group is preserving our history. When we moved
> from CVS to SVN our entire code base history was preserved (via cvs2svn),
> everything I can see is that if we move to AccuRev we can only take
> “snap-shots” of the SVN repo at particular revisions and then “import” that
> exact revision into AccuRev, (can’t “dump” our svn repo and then read it
> back into AccuRev) do you know if that is the case?
>
>
>
> If our CM forces this move upon us and then down the road we find out that
> AccuRev was not the expected “bang for your buck” and we move back to
> Subversion do you know if you can “dump” the AccuRev repo and then read it
> back into a SVN repo?
>
>
>
> The majority of the developers I work with would like to stay with
> Subversion, but we are getting the feeling that our opinion might not
> matter. Some help from this group with a “why stick with Subversion” would
> be great. Suggestions other then “Subversion is free v AccuRev is expensive”
> would be beneficial as we have already brought this up with our CM and he
> doesn’t see that as a valid reason.
>
>
>
> Thanks for your help, we are really looking for opinion to keep our CM from
> forcing this move upon us.
>
>
>
> ---------------------------------------------
>
> Bryan Wilkins
>
> Software Engineer
>
> ---------------------------------------------
>
>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2405126
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-08 17:17:51 CEST