curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cameron McKenzie <mckenzie....@gmail.com>
Subject Re: FYI - changing 2.6.1 to 2.7.0
Date Mon, 28 Jul 2014 21:42:31 GMT
How would we manage this with our current branching structure?


On Tue, Jul 29, 2014 at 7:36 AM, Mike Drob <madrob@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 <
> jordan@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
> >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message