Jorge Diaz (
866●44●34)
| answered Feb 27 '15, 7:16 a.m.
JAZZ DEVELOPER
Hi VK,
deciding the versions to migrate is always a consideration when planing any SCM tool migration effort. You have to consider and plan for aspects like:
- How many versions do I need to move? IMHO, the least the last. So you can take this opportunity to just migrate what is really needed and do a little of house cleanup (the least the best). Try to avoid thinking of migration anything that ***might*** be needed.
- You have to also consider during the migration effort versions that are "on-fly" during the time, and how you are going to manage the overlapping period for migration, in which you are importing versions in the new RTC system, while in the old there is still work being done everyday.
Being said that, you can run the import several times for each baseline of versions you want to move, from the oldest version (first run), to the newest (last run). Note that you want to ultimately end up with validating your build process in your RTC streams with (1) your latest production versions and (2) any deltas that are to be consolidated from the development work.
Regards,
Jorge.