How does that impact master vs. 1.4.x?
On Wed, Apr 17, 2013 at 4:36 PM, Noah Slater <[email protected]> wrote: > The goal was that you only merge in features when they are ready, and come > with tests, and docs, and what have you. And that you actually call a lazy > consensus "merge request" on dev@ before you can merge in. > > > > > On 17 April 2013 15:18, Dirkjan Ochtman <[email protected]> wrote: > >> On Wed, Apr 17, 2013 at 4:02 PM, Noah Slater <[email protected]> wrote: >> > So that features can be merged into it as they become ready. >> > >> > Check out: >> > >> > http://wiki.apache.org/couchdb/Merge_Procedure >> > >> > Thoughts? >> >> Seems like you could call the next-feature-release branch "master", >> and not have to start a new branch every time. >> >> Cheers, >> >> Dirkjan >> > > > > -- > NS
