> On Mon, Sep 23, 2013 at 1:50 PM, Bob Archer <bob.arc...@amsi.com> wrote: > >> It really depends. I think all work for a specific release should be done > >> in a > single branch/folder. Many people follow the stable trunk model. In this model > you generally do all work on trunk and then branch for a release. This is the > same model svn itself is developed under. In this model you would also use > what are called "feature" branches. This is generally for a feature/use case > that > will take more than a day to complete or will be worked on by more than one > developer. > > > > Once again, it's up to the people not the tool to ensure your release > management is done properly. > > Well, sort-of. It is always a good idea to (a) include tests for new > code and (b) have a workflow that ensures that the tests are run and > that someone checks the results. Expecting one person to never make > a mistake just doesn't always work out.
Isn't is up to the people to put those processes in place? To create the correct workflow? To write the automation? I don't think I ever said it should be ONE person's responsibility to manually do this work. Where did I say that? BOb > > A general rule can't cover all cases, but in general I think the longer you > let > branches diverge with isolated work, the more likely they are to have > conflicting changes that will take extra work to resolve when you finally do > merge. > > -- > Les Mikesell > lesmikes...@gmail.com
