VSS Sourcesafe Migration Tool - queries
When looking at the currently released version of the Source Control Migration tool, there were some issues which made us unable to move forward. It's unclear from the documentation whether all of these issues are bugs or whether they are features. So, the resultant questions are :
- In VSTS Source Control, changes can be merged, but only between branches. VSS branches which were migrated forwards into VSTS did not have their branch status maintained so merging was no longer possible. Is it intentional that migrated source loses its branch information or will this be fixed ?
- Migrated source which was Pinned is migrated at the final version point with a Label added to indicate the location of the old Pin. We have tens of thousands of source files which have been pinned and branched - what's the intended migration path for such files ? There's no way that we can roll-back these pins by hand to their correct location in the history & right now I shudder at the thought of trying to test the results if I try to automate this.
- Is there a way to associate two source trees together as branches, or must they be created as branches in the 1st place? Without this linkage there appears to be no way to perform merges, which removes the workaround option for the migration tool failing to maintain this linkage. Thoughts on any of these points would be appreciated, Cheers, Martin
