ready to be released are in master and everything else
is just waiting in its branch.
-Jordan
From: Mike Drob
Reply: dev@curator.apache.org >
Date: July 28, 2014 at 4:49:56 PM
To: dev@curator.apache.org >
Cc: Cameron McKenzie >
Subject: Re: FYI - changing 2.6.1 to 2.7.0
might make m
he.org >
> Date: July 28, 2014 at 4:42:57 PM
> To: 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 wrote:
>
> > Is
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 wrote:
> Is it possible (or desirable?) to split some of the bug fixes into a 2.6.1
> before adding the AP
How would we manage this with our current branching structure?
On Tue, Jul 29, 2014 at 7:36 AM, Mike Drob 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...@jo
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
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
