可以向 SUN Teamware 的客户/老板提出哪些论点 -> 现代SCM迁移？
我工作的团队仍然使用 SUN Teamware 进行源代码管理 (SCM)。 我已经使用它一段时间了（超过 10 个月），我对此没有任何特别的抱怨。
Teamware 已用于管理Sun 最大的源代码树，包括Solaris 操作系统和Java 系统的源代码树，而且效果非常好。 但它也是一个已经停产的老商业（闭源）产品。 这是 Sun 将其代码库转换为开源社区过程的一部分，而该社区又导致转向更新的版本控制系统，例如 Mercurial。
这让我感觉有点像我们在使用 Teamware 时陷入了困境，而世界已经转向更新的系统。 然而，我并没有错过任何特定的功能，除了可能有一个源树的 Web 视图来浏览和查看文件的历史记录（我们使用 VersionTool 做的事情，所以并不重要）。
使用 SUN Teamware 的团队是否应该迁移到更现代的 SCM（如 git 或 Mercurial）？
更重要的是，您可以向团队其他成员提出哪些论据来支持这一转变？
The team where I work still uses SUN Teamware for Source Code Management (SCM). I've worked with it for a while now (over 10 months) and I don't have any particular complaints about it.
Teamware has been used to manage Sun’s largest source trees, including those for the Solaris operating system and the Java system, and it works pretty well. But it is also an old commercial (closed-source) product that has been discontinued. This came as part of the process of Sun converting their code bases to open source communities which by its turn led to moving to newer revision control systems such as Mercurial.
This makes me feel a bit like we've got stuck in time using Teamware and the world has moved on to newer systems. I do not however miss any particular functionality except maybe having a web view of the source tree to navigate through and see the history of files (something we do with the VersionTool so not critical).
Should a team using SUN Teamware migrate to a SCM more modern like git or Mercurial?
And more important, what arguments can you present to the rest of the team to support that transition?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我是 SCM 的忠实粉丝，但我不得不说，如果它没有坏，就不要修复它。 继续使用它，直到 Teamware 不再满足您的需求。
I'm a big fan of SCM but I have to say, if it ain't broke, don't fix it. Until Teamware no longer meets your needs, continue to use it.
您是否看到 Sun 对以下内容所做的评估：
作为 Solaris 代码库替代 Sun Teamware VCS 的候选者？
这可能会为考虑迁移时需要评估的主题提供一些想法。
Git 调查 2007-2008 中列出了其他一些主题。
Did you see the evaluations that Sun did of:
as candidates to replace the Sun Teamware VCS for the Solaris code base ?
That may gave some ideas about topics to evaluate when thinking about a migration.
Some other topics are listed in this Git Survey 2007-2008.
读到字里行间，我想即使你也没有什么真正的论点，除了个人感觉要远离当前的趋势。 不幸的是，这并不是将大型代码库从一个 SCM 迁移到另一个 SCM 的理由。
如果你想保持最新状态，你仍然可以在家玩 git/Mercurial/Bazaar。
Reading between lines, I guess that even you have no real argument except the personal feeling to be left from current trends. Unfortunately this is not an argument for migrating a big code base from one SCM to the other.
I you want to stay up to date, you still can play with git/Mercurial/Bazaar at home.