On Wed, Jul 22, 2009 at 5:46 AM, Yuki KODAMA<endflow....@gmail.com> wrote: >>> 2. Adopt named branches for releases, drop crew repository. >> >> why did you decide to go for named branches instead a seperate crew repo, >> which seems to have been common practice up to now? > > He said "mainly for dogfooding". > To implement & improve "named branch" feature, we should be heavy user for > that.
It also nicely documents the feature branch on which changes were introduced. And I expect it to simplify a number of smaller issues (bug fixes made on the feature branch will close issues in the issue tracker, and it will be easier to follow from the issue tracker to the branch on which the fix was made). > but I might be confuse it a bit when moved to "named branch" development... There will be an adjustment period, but I don't think it will be too bad. -- Steve Borho ------------------------------------------------------------------------------ _______________________________________________ Tortoisehg-discuss mailing list Tortoisehg-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
