最后一点：我们已经在 Linux 和 Windows 上使用了 Surround，而且它在这两种系统上的表现似乎都一样好。拥有相同的界面真是太好了。
I have used Surround at my job for about three years.
It does work well with their (Seapine's) test management and issue tracker program. If you are already using TestTrack, I would say Surround is a good choice.
In general I agree with @eremzeit, but the 'buggy and confusing' comment rarely applies to our workflow. The default diff tool (Guiffy) is bad, but often good enough.
One part I like is the easy ability to share files across repositories without needing to share a whole project/repository. Git does not have a mechanism to do this easily.
Last note: we have used Surround on Linux and Windows and it appears to work just as well on either. It is nice to have the same interface.
Can apply a development work flow for all files. No two revisions of a file can be in the same status in the work flow.
Has a good UI.
Good licensing system.
Cons:
Stores all data in a RDBMS.. heading for a performance problem if the repo size is huge.
Does not support atomic commits. (you can do atomic commits but the files are still revisions and cannot be refereed using the changelist #)
My ideas about other tools
Subversion suits well for a corporate setup. Perforce is like subversion but faster and has a good UI, simple licensing terms and really super support system. Recently Accurev has gained a strong footing with its innovative branching methodology.
IMHO. go for tool sets that interact well with your defect tracking, test case management and build management solution. This would help you create a good developer ecosystem thereby saving time.
功能没有得到很好的记录 当然，他们发布了用户指南，但它与 Microsoft Windows 帮助功能一样有用。它逐步告诉您如何在 UI 中执行操作（即“单击“创建影子目录”，然后单击“确定””，但它不会告诉您这些功能是什么以及如何使用它们，服务器端实际发生了什么等等。
顺便说一句，如果您知道解决这些问题的任何好方法，请告诉我:)
I've been using Surround SCM at my job and I'll say it is what it is, but there are a few things that I find lacking. Though, I've heard that surround scm integrates well with surround's issue tracking system, but I can't comment on that because we don't use that.
I personally find the UI to be buggy and confusing.
The workflows are confusing and often offer you with prompts that don't apply, so you get used to ignoring warnings.
eg. "are you sure you don't want to auto-merge?" "Are you sure you want to overwrite files?"
The UI always badgers you to use the auto-merge feature but every time I've tried it, it ends up messing up my code (C#).
On top of that, the packaged diff tool (Guiffy) is buggy and doesn't display text properly.
Weird workflow quirks can result in your changes being overwritten.
It doesn't do directory syncing ...which means that every time you add a new file to your project you must by-hand go and add it to the SCM repository. If you don't, everything will look normal to you until one of your teammates emails you because you broke the build.
There's no good way to copy over revision histories when you are branching ... which means that you are less likely to branch when you should be. There's nothing more frustrating than to have to store code locally because you're making changes right before a release and your team refuses to branch the code into another repository.
There's no good way to blacklist certain files from being checked-in or from being overwritten during an update. If there's a file that you don't want to check-in then you're left with the painful chore of scanning through a long list of files and deselecting those you don't want every time you want to check-in. Yuck.
Features aren't documented that well Of course, they release a user's guide but it's about as helpful as Microsoft Windows help function. It tells you step by step how to do things in the UI (ie. "click 'Create Shadow Directory', then click 'OK'", but it doesn't tell you what those features are, how they are intended to be used, what actually happens server-side etc.
Btw, if you know of any good way to get around these problems let me know :)
发布评论
评论（4）
我在工作中使用 Surround 已经大约三年了。
它确实与他们（Seapine 的）测试管理和问题跟踪程序配合得很好。如果您已经在使用 TestTrack，我会说 Surround 是一个不错的选择。
总的来说，我同意@eremzeit，但“错误且令人困惑”的评论很少适用于我们的工作流程。默认的 diff 工具 (Guiffy) 很糟糕，但通常足够好。
我喜欢的一点是可以轻松地跨存储库共享文件，而无需共享整个项目/存储库。 Git 没有一种机制可以轻松地做到这一点。
最后一点：我们已经在 Linux 和 Windows 上使用了 Surround，而且它在这两种系统上的表现似乎都一样好。拥有相同的界面真是太好了。
I have used Surround at my job for about three years.
It does work well with their (Seapine's) test management and issue tracker program. If you are already using TestTrack, I would say Surround is a good choice.
In general I agree with @eremzeit, but the 'buggy and confusing' comment rarely applies to our workflow. The default diff tool (Guiffy) is bad, but often good enough.
One part I like is the easy ability to share files across repositories without needing to share a whole project/repository. Git does not have a mechanism to do this easily.
Last note: we have used Surround on Linux and Windows and it appears to work just as well on either. It is nice to have the same interface.
环绕单片机。
优点：
缺点：
我对其他工具
Subversion 的想法非常适合公司设置。 Perforce 类似于 subversion，但速度更快，并且具有良好的 UI、简单的许可条款和真正超级的支持系统。
最近，Accurev 凭借其创新的分支方法奠定了坚实的基础。
恕我直言。选择能够与缺陷跟踪、测试用例管理和构建管理解决方案良好交互的工具集。这将帮助您创建一个良好的开发者生态系统，从而节省时间。
Surround SCM.
Pros:
Cons:
My ideas about other tools
Subversion suits well for a corporate setup. Perforce is like subversion but faster and has a good UI, simple licensing terms and really super support system.
Recently Accurev has gained a strong footing with its innovative branching methodology.
IMHO. go for tool sets that interact well with your defect tracking, test case management and build management solution. This would help you create a good developer ecosystem thereby saving time.
我在工作中一直使用 Surround SCM，我会说它就是这样，但我发现有一些东西缺乏。不过，我听说 Surround scm 与 Surround 的问题跟踪系统集成得很好，但我无法对此发表评论，因为我们不使用它。
我个人认为 UI 存在缺陷且令人困惑。
当我尝试过它时，它最终弄乱了我的代码（C#）。
适当地。
它不进行目录同步
...这意味着每次您向项目添加新文件时，您都必须手动将其添加到 SCM 存储库。如果你不这样做，一切对你来说看起来都很正常，直到你的一位队友因为你破坏了构建而给你发电子邮件。
在分支时没有复制修订历史记录的好方法
...这意味着你不太可能在应该分支的时候分支。没有什么比必须在本地存储代码更令人沮丧的了，因为您在发布之前进行更改，而您的团队拒绝将代码分支到另一个存储库。
没有好的方法可以将某些文件列入黑名单，防止其在更新过程中被签入或覆盖。
如果有一个您不想签入的文件，那么每次您想要签入时，您都会经历扫描一长串文件并取消选择那些您不需要的文件的痛苦苦差事。恶心。
功能没有得到很好的记录
当然，他们发布了用户指南，但它与 Microsoft Windows 帮助功能一样有用。它逐步告诉您如何在 UI 中执行操作（即“单击“创建影子目录”，然后单击“确定””，但它不会告诉您这些功能是什么以及如何使用它们，服务器端实际发生了什么等等。
顺便说一句，如果您知道解决这些问题的任何好方法，请告诉我:)
I've been using Surround SCM at my job and I'll say it is what it is, but there are a few things that I find lacking. Though, I've heard that surround scm integrates well with surround's issue tracking system, but I can't comment on that because we don't use that.
I personally find the UI to be buggy and confusing.
time I've tried it, it ends up messing up my code (C#).
properly.
It doesn't do directory syncing
...which means that every time you add a new file to your project you must by-hand go and add it to the SCM repository. If you don't, everything will look normal to you until one of your teammates emails you because you broke the build.
There's no good way to copy over revision histories when you are branching
... which means that you are less likely to branch when you should be. There's nothing more frustrating than to have to store code locally because you're making changes right before a release and your team refuses to branch the code into another repository.
There's no good way to blacklist certain files from being checked-in or from being overwritten during an update.
If there's a file that you don't want to check-in then you're left with the painful chore of scanning through a long list of files and deselecting those you don't want every time you want to check-in. Yuck.
Features aren't documented that well
Of course, they release a user's guide but it's about as helpful as Microsoft Windows help function. It tells you step by step how to do things in the UI (ie. "click 'Create Shadow Directory', then click 'OK'", but it doesn't tell you what those features are, how they are intended to be used, what actually happens server-side etc.
Btw, if you know of any good way to get around these problems let me know :)
危险！危险，威尔·罗宾逊！
Surround 是一个数据监狱。一旦你承诺了，你就会陷入困境。没有已知的方法可以将您的历史记录返回到另一个 SCM。不要被困住！
一般来说，这往往是闭源 SCM 的问题，但我有直接报告称 Surround 的情况尤其糟糕。
Subversion、git、Mercurial 或 Bazaar 会是更好的选择。
Danger! Danger, Will Robinson!
Surround is a data jail. Once you commit to it, you're stuck. There is no known way to get your history back out to another SCM. Don't get trapped!
This tends to be a problem with closed-source SCMs in general, but I have direct reports that it's especially bad with Surround.
Subversion, git, Mercurial, or Bazaar would be better choices.