On Mon, Jan 13, 2014 at 5:39 PM, Walter Bright <walter@digitalmars.com> wrote:

On 1/12/2014 10:30 PM, Daniel Murphy wrote:
How is it more work?  Worst case: delete 2.065 branch, make new one.


That works for me.


Ok, cool.  I think this would work for release branches in general - if we've made a beta/release candidate and merging commits from master has become too difficult, simply abandon it and re-branch.   This way we never have to stop work on master, and never get stuck with complex merges and backporting.