This article covers various strategies for getting your existing SCM data into OurayCM.
There are several different strategies one can take in importing data (which one is correct depends on your situation):
If your latest version of software is where most of your activity is, then importing is simple: simply add your latest version of the source to OurayCM and proceed. Your old non-Ouray repo is always there if you need it.
If you are working on multiple releases in parallel and must continue to support them, then you can still import your data, but it will be a bit more effort, depending on the complexity of your maintenance work. Basically, what you need is to create a branching structure in OurayCM that matches your ongoing parallel development efforts.
Start by identifying all of the releases that must be imported. Then, identify the genealogy of the releases: a hierarchy of dependencies of what release came before another. This will determine what order to enter the information in OurayCM in. The oldest release should be entered first, followed by the next oldest, and so on. Use the 'ocm vref edit' feature to tag a given OurayCM version as holding a given release. Use the 'ocm version copy' feature to verify that what you put in was what you thought.
If your releases do not follow a linear pattern, use the OurayCM branching feature to represent the dependency structure of your releases.
In the future we will provide sample conversion scripts. Contact us at EMAIL_SUPPORT if you need a conversion script for a specific tool.
If you have any feedback on this article, feel free to email the author.