Synchronization of labels

Published 06 December 06 05:28 PM | mmitrik 

In my previous posts, it was not made clear that the migration toolkit will support bi-directional synchronization as well as one-way conversion.  This enables many useful scenarios including the ability to migrate portions of a project over time.

 

Synchronization does bring up some complex scenarios, especially for non-versioned items.  We have come across a few questions concerning how labels in a version control system should be migrated/synchronized with TFS.  Any feedback on this is welcome.

 

  1. What level of support for migrating labels is optimal?
    1. Should all labels be migrated during the initial conversion of data,
    2. or should users be able to choose specific labels to migrate,
    3. or should no labels be migrated (they can be added in TFS after migrating)?

 

  1. For labels that exist in both systems (the original system and TFS) after initial conversion:
    1. Is it useful to synchronize labels across systems?
    2. Are there specific labels that would be useful to synchronize between systems (i.e. a recent build label)?
    3. Should labels only be synchronized if they are manually chosen to be synchronized?

Comments

# brycecalhoun said on January 3, 2007 3:25 PM:

I'm working with a client that is currently using Seapine SCM for their source code management, but wants to move to TFS in the near term.  Do you have a timeframe for when you will be releasing the migration toolkit, and what (at a high level) will be required to create a custom adapter?

Anonymous comments are disabled

Search

This Blog

Syndication

Page view tracker