从 StarTeam 5 迁移到 Subversion 的策略? [英] Strategy to migrate from StarTeam 5 to Subversion?

问题描述

我需要将一个大型项目从 StarTeam 5 迁移到 Subversion，并且我想保留(至少)5-10 个主要版本的快照.我考虑了以下几点:

I need to migrate a large project from StarTeam 5 to Subversion, and I'd like to keep snapshots of (at least) 5-10 of the major releases. I've considered the following:

• 手动或脚本导出/导入每个快照.优点:简单，易于选择标记/日期版本.缺点:耗时，不保留评论.
• Polarion 提供了似乎是 svnimporter 中完美的工具，但它需要 StarTeam 8.0 中的 .jar 文件，而 StarTeam 5 中没有.优点:自动化、完整.缺点:需要升级到 StarTeam 8.0 才能一次性使用.
• 通过一些中间存储库迁移(例如 StarTeam -> CVS -> Subversion).我还没有找到任何与 StarTeam 合作的中介.
• 仅迁移最新的源.优点:简单、快速，鼓励开发人员发明新的解决方案而不是重复历史.缺点:鼓励开发人员发明新的解决方案，而不是重复历史.:-)

• Manual or scripted export/import of each snapshot. Advantages: straightforward, easy to select labeled/dated versions. Disadvantages: time-consuming, does not preserve comments.
• Polarion offers what seems to be the perfect tool in svnimporter, but it requires a .jar file from StarTeam 8.0 that is not present in StarTeam 5. Advantages: automated, complete. Disadvantages: requires upgrade to StarTeam 8.0 for one-time use.
• Migrate via some intermediate repository (e.g. StarTeam -> CVS -> Subversion). I haven't yet found any intermediary that will cooperate with StarTeam.
• Migrate only the latest source. Advantages: simple, fast, encourages developers to invent new solutions rather than repeating history. Disadvantage: encourages developers to invent new solutions rather than repeating history. :-)

如果您提供任何经验或建议，我将不胜感激.谢谢.

I'd appreciate any experiences or suggestions you might offer. Thank you.

推荐答案

我没有使用过 StarTeam，我不能说 - 但我认为您已经提出了一些不错的选择.

Having not used StarTeam I cannot speak to that -- but I think you've laid out some nice options.

1. 脚本导入似乎很耗时，并不能真正为您提供一切，但同时，它是进入 svn 并仍然保留您的发布历史的可靠方法.
2. 升级后放弃安装的真正缺点是什么?需要重新购买软件吗?这是一个乏味的升级吗?除此之外，听起来这可能是最好的选择.
3. 我真的会远离这个选项.cvs -> svn import 非常不稳定(真的，这是一次性的事情，可能没有多少人致力于它足以真正关心使其完美).从另一个 SCM 系统转到 cvs，然后转到 svn，这听起来像是无用历史数据和挫折的秘诀.:) 我只做过几次，实际上，最好的部分是一旦你完成了，你就在 svn 中，再也不会接触 cvs.
4. 这个选项确实很糟糕.你失去了所有的历史......不能再责备其他开发者搞砸了.不过从好的方面来说，如果一切都失败了，它绝对会奏效.

1. Scripted import seems like it could be time consuming, not really get you everything, but at the same time, be a reliable way to get into svn and still preserve your release history.
2. What is the real downside of upgrading and throwing away the install after? Do you have to re-purchase the software? Is it a tedious upgrade? Barring that, it sounds like this may just be the best option.
3. I would really stay away from this option. cvs -> svn import is pretty shaky (really, it's a one-off thing, probably not that many individual people work on it enough to really care about making it perfect). Going from another SCM system to cvs, and THEN to svn sounds like a recipe for useless history data and frustration. :) I've only done it a couple of times, and really, the best part is once you're done, you're in svn and never touch cvs again.
4. This option does really suck. You lose all your history.. can no longer blame other dev's for screwing things up.. On the upside though, it will absolutely work, if all else fails.

这篇关于从 StarTeam 5 迁移到 Subversion 的策略?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！