|
|
Scrum for Team System - v1.x Support
Started by amdMcBook at 09-09-2008 10:44 PM. Topic has 1 replies.
  
|
|
Sort Posts:
|
|
|
|
 09-09-2008, 10:44 PM
|
amdMcBook
Joined on 09-09-2008
Posts 1
|
Definitive guide for upgrading to 2.x scrum template
|
|
|
|
|
Is there a single place where all the steps needed to upgrade from TFS 05-Scrum template 1.2 -> TFS 08->Scrum template 2.x is documented??
I've searched on the forums here and have found different posts, some of which suggest a solution, only to say later dowen the thread that the suggestions does not work and that the customer should try another method. It's hard to know what works and what does not.
What is the recommended way to upgrade the scrum template?
|
|
|
|
|
Report
|
|
|
|
|
09-11-2008, 8:06 AM
|
Crispin Parker
Joined on 11-13-2007
Posts 664
|
Re: Definitive guide for upgrading to 2.x scrum template
|
|
|
|
|
|
Hello amdMcBook,
Your observation and question are completely valid. We do not have a complete end to end guide for migration from SfTS 1.2 to SfTS 2.x.
The reason for this is largely due to the inability to migrate Team Projects from a TFS 2005 into a TFS 2008 environment. This is not a SfTS issue, the core TFS platform does not allow you to do this. However, we have tried to help version 1.x users by providing a migration utility.
You can read more about the migration utility in my blog post:
This utility is limited to the migration of work item data (including all work item history) only. Version control, custom check in policies, build tasks, subscriptions, etc are all left behind.
Here is some advice on how to migrate from a 1.x to 2.x team project:
Prerequisites:
- You have a target TFS 2008 (WSS 3.0) environment setup and running.
- You have a source SfTS 1.x team project.
- The source team project is stable with all version data checked in (preferably at a release point).
- If the TFS 2008 is hosted elsewhere, there is common AD access (to maintain work item ownership data)
Process:
- Take a snapshot of the source projects code base. Getting the latest version to a new work space should accomplish this.
- Create a new target SfTS 2.x team project.
- Setup the new project as required. See my Getting Started with SfTS 2 blog post for more info:
http://blogs.conchango.com/sfts/archive/2008/06/04/getting-started-with-scrum-for-team-system-version-2.aspx
- Add the required user access permissions to the target team project and project portal.
- Import the source projects code base (extracted in step 1) to the target projects version control. You can use the Team Explorer Source Control interface for this.
- Use the Migration Utility to export and import the work item data. The blog post (detailed at the top of this post) walks you through this process.
- Add any additional project requirements. This could include event subscriptions, custom check-in policies, build tasks and that sort of thing.
- Decommission your source project. I would advise that it is kept available in order to keep the version control history available.
And that should be about it. I invite any other community members to recount their migration stories and advice below.
Regards,
Crispin Parker,
Technical Consultant,
Conchango.
"It is better to light a candle than to curse the darkness"
|
|
|
|
|
Report
|
|
|
|
|
Scrum for Team ... » Version 1.2 - T... » Scrum for Team ... » Definitive guide for upgrading to 2.x scrum template
|
|
|
|