Mercurial and Agile

Paul Crowley paul at lshift.net
Thu Jul 2 09:07:13 UTC 2009


We update to the last released version before implementing each feature 
in its own named branch; that way creating a new release is just a 
sequence of standard merges.  Sometimes feature B depends on feature A, 
in which case work on feature B will be started at the end of branch A. 
  At release time my desk is generally covered with big A3 multicoloured 
"dotlog" printouts from which I work out what to merge!
-- 
   [][][] Paul Crowley
     [][] LShift Ltd
   []  [] www.lshift.net



More information about the Mercurial mailing list