Neither one is easy to learn. Perforce's weirdness is focused around branching and private work areas. AccuRev's weirdness is focused around streams, promoting between them, and reparenting them. Both systems are a little hard to get your head around, especially if you're used to CVS.
For my two cents, AccuRev is the better product. The streams are a very powerful tool for managing development vs. QA vs. patches. And the concept of server-shadowed private workspaces is a godsend - there is no reason for a user not to checkpoint their workspace several times a day, and it goes into your server backups.
If you are still choosing you may want to read AccuRev - another story how to screw UI and Reply by AccuRev. As an AccuRev user, I think that idea of stream tree is really powerful and many of the features like time locks, promoting by transactions or issues, etc. are useful, but UI implementation is awful. You definitely need to play hard with it before switching.
I can't speak for AccuRev - honestly I haven't even heard of it before now - but I can speak for Perforce:
I find it incredibly easy once you understand a few truly key aspects:
Anything that might change the "depot" (server side SCM managed repository) happens through changelists.
All of those interactions on changelists are also tied to a client workspace - in other words, you can't really work with files that haven't had a mapping established from the depot to your filesystem.
Also, the three days of training in San Francisco (or perhaps a closer location) was well worth it for me as I have an administrative role in our Perforce environment - though I had been using it prior to the training just fine to manage our code base.
That being said, there are many variables you need to consider: developer experience, what tool you are currently using, what your team can afford to buy etc.
If your main concern is simply figuring out what is easier, both vendors offer free trials/licenses. You should download them and test them out against your code base and existing tools.
Also - try to get your team involved to ease the transition.
发布评论
评论（4）
两者都不容易学。 Perforce 的怪异之处集中在分支和私有工作区域。 AccuRev 的怪异之处在于流、它们之间的升级以及重新设置它们的父级。 这两个系统都有点难以理解，特别是如果您习惯了 CVS。
对于我的两分钱来说，AccuRev 是更好的产品。 流是管理开发、QA 和补丁的非常强大的工具。 服务器影子私有工作区的概念是天赐之物 - 用户没有理由不每天多次检查其工作区，并且它会进入您的服务器备份。
Neither one is easy to learn. Perforce's weirdness is focused around branching and private work areas. AccuRev's weirdness is focused around streams, promoting between them, and reparenting them. Both systems are a little hard to get your head around, especially if you're used to CVS.
For my two cents, AccuRev is the better product. The streams are a very powerful tool for managing development vs. QA vs. patches. And the concept of server-shadowed private workspaces is a godsend - there is no reason for a user not to checkpoint their workspace several times a day, and it goes into your server backups.
如果您仍在选择，您可能需要阅读AccuRev - 另一个如何搞砸 UI 的故事 和 AccuRev 回复。 作为 AccuRev 用户，我认为流树的想法非常强大，许多功能（如时间锁定、通过事务或问题进行推广等）都很有用，但 UI 实现很糟糕。 在切换之前你肯定需要努力尝试它。
If you are still choosing you may want to read AccuRev - another story how to screw UI and Reply by AccuRev. As an AccuRev user, I think that idea of stream tree is really powerful and many of the features like time locks, promoting by transactions or issues, etc. are useful, but UI implementation is awful. You definitely need to play hard with it before switching.
我不能代表 AccuRev - 老实说，我以前从未听说过它 - 但我可以代表 Perforce：
一旦你了解了几个真正关键的方面，我发现它非常容易：
此外，在旧金山（或者可能更近的地点）进行的三天培训对我来说非常值得，因为我在 Perforce 环境中担任管理角色 - 尽管我在培训之前一直使用它来管理我们的代码根据。
I can't speak for AccuRev - honestly I haven't even heard of it before now - but I can speak for Perforce:
I find it incredibly easy once you understand a few truly key aspects:
Also, the three days of training in San Francisco (or perhaps a closer location) was well worth it for me as I have an administrative role in our Perforce environment - though I had been using it prior to the training just fine to manage our code base.
这个问题有点主观！
话虽如此，您需要考虑许多变量：开发人员经验、您当前使用的工具、您的团队可以购买的工具等。
如果您主要关心的是简单地找出更简单的方法，那么两家供应商都提供免费试用/许可证。 您应该下载它们并根据您的代码库和现有工具对其进行测试。
另外 - 尝试让您的团队参与进来以简化过渡。
This question is a bit subjective!
That being said, there are many variables you need to consider: developer experience, what tool you are currently using, what your team can afford to buy etc.
If your main concern is simply figuring out what is easier, both vendors offer free trials/licenses. You should download them and test them out against your code base and existing tools.
Also - try to get your team involved to ease the transition.