Is it possible to copy an RTC repository, upgrade it, and merge with the original (upgraded) repository later ?
The Infosphere development group cannot be up graded to the latest version because the Infosphere is not supported with a newer release of Eclipse. is it possible to take a copy of the RTC repository and upgrade it to the latest version (6.0.3), and when Infosphere can use a newer version of Eclipse later this year, upgrade and merge the original RTC repository ?
2 answers
How far away from 6.0.3 is the current server version ? The point is that client compatability is supported for 1 major version less than the server. i.e. 6.0.x server will accept 5.0.x clients. If you're going up a point release for same version, just do it; clients will be fine.
Comments
Kevin,
The current RTC version is 4.0.6, and it is at End-Of-Life in Sept '17.
The Infosphere SW development team is using a 3.0.1.6 Eclipse client. Infosphere will not work with a newer version of the Eclipse client. A new release of Infosphere is expected to be released the end of this year that can run on a newer version of Eclipse.
So there are now two RTC repositories, the original 4.0.6 and the new 6.0.3. When the new Infosphere release is available, can the Infosphere Projects on the RTC 4.0.6 repository be upgraded and merged with the previously upgraded RTC 6.0.3 repository, so there is just one server?
Thanks,
Don
Don and I have been discussing this off-line, and the short answer is, no, in general, you cannot "merge" one RTC repository with another RTC repository (even if one was created as a clone of the other one). For the SCM data, what you can do is use distributed deliver to replicate the SCM data to another repository, and then once the two repositories are back to the same version, you can use distributed deliver to merge the SCM data back. For the work item data, you can use a combination of import and work item replication (via something like the Tasktop RLIA adapter) to get a subset of the work item data transferred.