That’s a good point. I think, we’d have master just be whatever the next release will be. Then, we could have a 2.7.0 branch that would become master after 2.6.1 is released. OK?
-JZ From: Cameron McKenzie <mckenzie....@gmail.com> Reply: dev@curator.apache.org <dev@curator.apache.org>> Date: July 28, 2014 at 4:42:57 PM To: dev@curator.apache.org <dev@curator.apache.org>> Subject: Re: FYI - changing 2.6.1 to 2.7.0 How would we manage this with our current branching structure? On Tue, Jul 29, 2014 at 7:36 AM, Mike Drob <mad...@cloudera.com> wrote: > Is it possible (or desirable?) to split some of the bug fixes into a 2.6.1 > before adding the APIs for 2.7.0? > > > On Mon, Jul 28, 2014 at 4:34 PM, Jordan Zimmerman < > jor...@jordanzimmerman.com> wrote: > > > FYI > > > > There will be some new APIs in the next release (CURATOR-126 for example) > > that suggests making this 2.7.0 instead of 2.6.1 > > > > -JZ > > > > >
