从ClearCase迁移到SVN的最佳策略是什么? [英] What is the best strategy when migrating from ClearCase to SVN?

问题描述

我们正在考虑从ClearCase迁移到Subversion.该项目已经存在了一段时间(7年)，我们积极支持三个主要"版本(分支)，以及一些较早版本中的偶尔修复.该项目相当大-大约有200万行Java代码.

We are considering moving from ClearCase to Subversion. The project has been there for a while (7 years) and there are three "major" versions (branches) that we actively support, plus some occasional fixes in older releases. The project is fairly large - around 2 mln lines of java code.

我很好奇，是否有人进行过类似的迁移.

I am curious if there is someone that has done similar migration.

• SVN能够处理如此大的项目吗?
• 迁移所有历史版本/分支是否有意义?是可以有选择地执行此操作的工具吗?
• 此类项目的迁移过程需要多长时间?迁移正在进行中，有效的工作方式是什么?

推荐答案

由于进行了几次此类迁移，因此我认为:

For having made several migrations of this kind, I would argue that:

• 您不需要将 all 的ClearCase版本的历史记录导入到SVN中.在大多数情况下(根据我的经验)，除非您确实需要细粒度的历史记录修订本，否则仅需要带标签的版本(在给定集合的所有文件上一致应用的版本).

• you do not need to import all the history of the ClearCase versions into SVN. Most of the time (for my experience), only the labeled versions (the one which are applied consistently on all the files of a given set) are needed, unless you have a real need for a fine-grained history revision examen.

您需要在迁移过程中考虑 重组 :您要导入什么?您要离开什么?您想让SVN内容反映出来吗? 精确地存储在ClearCase VOB中的文件的结构?有时，这种迁移是重新考虑某些文件组织的机会(通常是通过对某些目录的简单重命名规则).

you need to think about reorganization during a migration: what do you import ?, what do you leave ?, and do you want the SVN content reflect exactly the structure of the files as stored in the ClearCase VOB ? Sometime, such migrations are the occasion to rethink some of those files organization (usually through simple renaming rules for certain directories).

以ClearCase 2 SVN方式迁移更快，因为SVN以存储库为中心并提交了一组文件，而ClearCase以文件为中心并提交了逐个文件(非常繁琐)

the migration is quicker in the ClearCase 2 SVN way, since SVN is repository-centric and commit a set of files, while ClearCase is file-centric and commits file-by-file (much sloooower)

如果清楚地标识了要导入的文件集，则迁移过程可以重复多次，这意味着您可以在进行第一次(大)导入时在ClearCase中继续工作，然后放置一个在代码上加上基线(UCM标签)，然后仅重新导入增量，从而有效地结束了迁移过程.

if the set of files to import is clearly identified, the migration process can be repeated multiple times over, which means you can go on working within ClearCase while the first (large) import is taking place, then put a Baseline (UCM label) on your code, and re-import only the delta, effectively ending the migration process.

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