Comments on: A Tale of Version Control http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/ Mitch Denny, Principal Consultant at Readify Sun, 12 Jul 2009 01:45:19 +0000 http://wordpress.com/ hourly 1 By: Mitch Denny http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-79398 Mitch Denny Wed, 17 Oct 2007 05:41:20 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-79398 Hi Jon, Yes, sadly the images are the victims of a botched content migration. Hi Jon,

Yes, sadly the images are the victims of a botched content migration.

]]> By: Jon http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-78202 Jon Mon, 08 Oct 2007 18:41:26 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-78202 Thank you for a post on this topic. Is it just me, or are the links to the images broken? Thank you for a post on this topic. Is it just me, or are the links to the images broken?

]]> By: David http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-7088 David Fri, 03 Nov 2006 16:44:24 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-7088 I was just having a discussion about this with another member of my team. I would like your thoughts on my structure if possible. Because TFS existed prior to my arrival (I'm now responsible for the layout) I left the existing application as the Trunk (Stable version) with the suggestion of MS to create all new projects from the Trunk. This allows for not only a stable environment for production, but also for the build process. In other words if you are to modify the trunk and branch a finalized version your build process will always need to migrate to the next project. As far as the work items go I have another possible solution for thought. When I split the code I created a Maintenance project along with one for the current project. This keeps the projects clean (not mixing maintenance items with project specific work). If you query work items from the trunk you get a view of all work items across projects...or you can go to a specific project and get only those tasks. Once a project has been completed it's tasks have no need to transition to the next project (again seperation is clean). This post has been dead for a number of months...hoping it's still of interest. -David I was just having a discussion about this with another member of my team. I would like your thoughts on my structure if possible.
Because TFS existed prior to my arrival (I’m now responsible for the layout) I left the existing application as the Trunk (Stable version) with the suggestion of MS to create all new projects from the Trunk. This allows for not only a stable environment for production, but also for the build process. In other words if you are to modify the trunk and branch a finalized version your build process will always need to migrate to the next project.
As far as the work items go I have another possible solution for thought. When I split the code I created a Maintenance project along with one for the current project. This keeps the projects clean (not mixing maintenance items with project specific work). If you query work items from the trunk you get a view of all work items across projects…or you can go to a specific project and get only those tasks. Once a project has been completed it’s tasks have no need to transition to the next project (again seperation is clean).
This post has been dead for a number of months…hoping it’s still of interest.
-David

]]> By: Martin Woodward http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2086 Martin Woodward Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2086 I'd always wondered why somebody would use the "Create from Branch" option in the new project wizard - now I understand! <br /><br /> Thanks for the clarification - it is always good to understand different approaches. <br /><br /> Martin. I’d always wondered why somebody would use the “Create from Branch” option in the new project wizard – now I understand!

Thanks for the clarification – it is always good to understand different approaches.

Martin.

]]> By: Martin Woodward http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2087 Martin Woodward Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2087 Of course a major downside of creating a new team project per version is the lack of support for moving work items (and other artifacts / settings) between team projects. Not the end of the world, but just a caveat. Of course a major downside of creating a new team project per version is the lack of support for moving work items (and other artifacts / settings) between team projects. Not the end of the world, but just a caveat.

]]> By: Mitch Denny http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2088 Mitch Denny Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2088 Hi Martin, <br /><br /> Yeah - I can see that is a problem. But a good TFS configuration manager should be able to do it. It would be relatively easy to write a quick little program to do work item migrations - in fact I think one already exists. Hi Martin,

Yeah – I can see that is a problem. But a good TFS configuration manager should be able to do it. It would be relatively easy to write a quick little program to do work item migrations – in fact I think one already exists.

]]> By: Vincent http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2089 Vincent Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2089 A quick and dirty to export Work Items between projects would be to dump them in an excel spreadsheet and reimport them back in your new project. A quick and dirty to export Work Items between projects would be to dump them in an excel spreadsheet and reimport them back in your new project.

]]> By: Ian http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2090 Ian Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2090 <a target="_new" href="http://zkgllcqt.com/moio/hita.html">http://zkgllcqt.com/moio/hita.html</a> http://zkgllcqt.com/moio/hita.html

]]> By: Nicole http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2091 Nicole Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2091 <a target="_new" href="http://zkgllcqt.com/moio/hita.html">http://zkgllcqt.com/moio/hita.html</a> http://zkgllcqt.com/moio/hita.html

]]> By: Kevin http://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2092 Kevin Tue, 30 Nov 1999 00:00:00 +0000 https://notgartner.wordpress.com/2006/04/16/a-tale-of-version-control/#comment-2092 <a target="_new" href="http://zkgllcqt.com/moio/hita.html">http://zkgllcqt.com/moio/hita.html</a> http://zkgllcqt.com/moio/hita.html

]]>