Version Control migration – 2006 makes a design decision

Last time I bribed my 1999 self to answer 20 questions about what was needed from a version control migration process.  Below is the summary of key points from the answers: 1)      We need to support migrating only a portion of the entire source tree at a single time. 2)      We need to support migrating…

0

Time travel, 20 questions and the power of free soda.

Yesterday I presented 20 questions that I think are a good starting point when designing or evaluating a version control migration product.  The point is basically to get folks thinking about what should be migrated, how it should be migrated and what would happen if that data were not there. Last night I conjured up…

1

It’s Time for the Version Control Migration Feud!

Introducing on Team Foundation Server family!  We have Work Item Tracking, Team Build, Version Control and the Data Warehouse!”  And the “Other System” family!  With Proprietary Bug Tracking, Informal Build Process and Your Version Control System of Choice! On Your Marks!  Let’s start the… VC MIGRATION FEUD! “We asked 100 people to name the version…

1

Writing Version Control Migration Tools – Handling Namespace Cycles

Last time I discussed the issues surrounding namespace conflicts when designing a version control migration tool.  The basic lesson was that there are times when operations must be executed in a specific order for them to migrate properly.  But what if there are namespace collisions for which there is no order that resolves the collision?…

0

Writing Version Control Migration Tools – Handling Namespace Conflicts

Migrating from one version control system to another is tough.  I don’t care what the internet forums are saying or what Joe from down the hall told you.  It’s hard.  Very hard.  Deceptively hard. The obvious algorithm looks trivial: FOR EACH Changeset CS in History DO      FOR EACH Change C in Changeset CS DO…

1