Comments on: Keeping Track of your DVCS Development http://www.robertcowham.com/blog/179/keeping-track-of-your-dvcs-development/ Robert Cowham's Musings Fri, 27 Aug 2010 14:52:28 +0000 http://wordpress.org/?v=2.8.6 hourly 1 By: robertcowham http://www.robertcowham.com/blog/179/keeping-track-of-your-dvcs-development/comment-page-1/#comment-9 robertcowham Mon, 08 Mar 2010 18:45:47 +0000 http://www.robertcowham.com/blog/?p=179#comment-9 Yes, excellent point. A cloned DVCS repository is equivalent to a branch in many ways - and as you say, the definition of "done" is important to avoid work being lost track of. Yes, excellent point. A cloned DVCS repository is equivalent to a branch in many ways – and as you say, the definition of “done” is important to avoid work being lost track of.

]]> By: The Build Doctor http://www.robertcowham.com/blog/179/keeping-track-of-your-dvcs-development/comment-page-1/#comment-8 The Build Doctor Mon, 08 Mar 2010 18:19:38 +0000 http://www.robertcowham.com/blog/?p=179#comment-8 DVCS doesn't let you off the hook for process. In fact, I think it makes process more important. If people must use feature branches, then IMHO they should need to merge them to a nominated master branch in order to call them done.<br><br>Continuous Integration is useful here. Hudson can do the merge to another branch automatically if the build passes, which is an interesting possibility. I think I'd prefer developers to merge to that 'master' branch and have a CI server pick that up, though. DVCS doesn't let you off the hook for process. In fact, I think it makes process more important. If people must use feature branches, then IMHO they should need to merge them to a nominated master branch in order to call them done.

Continuous Integration is useful here. Hudson can do the merge to another branch automatically if the build passes, which is an interesting possibility. I think I'd prefer developers to merge to that 'master' branch and have a CI server pick that up, though.

]]>