My Suggestion is in line with the plan to move to time based releases. Branching for releases makes no sense under that policy.
Effectively, we move from shipping "when it's done" to shipping "what is done" Sent from my iPhone On Sep 6, 2011, at 5:01 PM, David Smith <catfish....@gmail.com> wrote: > I disagree. The concept of "trunk" focuses testing a lot. I know when > we had a few feature branches going I immediately set up my own branch > that I merged them all to so I could test more than one thing at once. > > David > > On Tue, Sep 6, 2011 at 4:52 PM, Stephen Holt <sh...@adium.im> wrote: >> I think we should stop branching releases entirely. >> >> Feature work done in branches, merged+intergated into the mainline when >> stable. New features released the next release after they're done. (Releases >> are tagged for historical reasons, of course) >> >> We've have a DVCS for several years, let's start developing like we have one. >> >> -- >> Steve >> >> On Sep 6, 2011, at 4:47 PM, Eric Richie wrote: >> >>> Now that we've got 1.4.3 out the door, I think it's time we go ahead and >>> branch 1.5. >>> >>> Any objections? >>> >>> -Eric >> >> >> >
