Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
MIME-Version: 1.0
In-Reply-To: <etPan.55cabced.6d308d8a.166@Jordans-MacBook-Pro.local>
References: <etPan.55c77393.7a37bb77.163@Jordans-MacBook-Pro.local>
	<CANykduZyZ=EnxLtAFftu8Au+askkB9Afxq77yZZHnkVoWphoMQ@mail.gmail.com>
	<etPan.55c7e4c6.797c6fd.163@Jordans-MacBook-Pro.local>
	<CANykdubhMY3fWcjc1f58BFAC7KG1w3uYEyb_LCQE8GrPzY_ADQ@mail.gmail.com>
	<etPan.55ca0573.548b5e89.166@Jordans-MacBook-Pro.local>
	<CANykduZQqs0uY5LxpoQ5P9XEP=xPzNyCpdBrifdgkK_ghEUaBA@mail.gmail.com>
	<CANykdub3SRuPh6-MpWTzdO9DdYGqTxER5rFQppYSGmv51UZ=-Q@mail.gmail.com>
	<etPan.55cabced.6d308d8a.166@Jordans-MacBook-Pro.local>
Date: Wed, 12 Aug 2015 13:39:09 +1000
Message-ID: 
 <CANykduaBo=V480Xvk2vO_kHzHD=_j61rNPKVRcwoPkBJxAcmYw@mail.gmail.com>
Subject: Re: Next Steps
From: Cameron McKenzie <mckenzie.cam@gmail.com>
To: "dev@curator.apache.org" <dev@curator.apache.org>
Content-Type: multipart/alternative; boundary=001a11378846200810051d14f666

--001a11378846200810051d14f666
Content-Type: text/plain; charset=UTF-8

My git knowledge is not deep enough to work out what's going on with the
CURATOR-3.0 branch, so I'm happy to go from scratch. Is it just a matter of
branching off master and merging all of the CURATOR-3.0 related branches?

On Wed, Aug 12, 2015 at 1:26 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> We need to come to a decision on the CURATOR-3.0 branch. My gut instinct
> is to start from scratch. Any other ideas?
>
> -JZ
>
>
>
> On August 11, 2015 at 5:28:30 PM, Cameron McKenzie (mckenzie.cam@gmail.com)
> wrote:
>
> Also, which branch should the CURATOR-214 fix come off? From memory the
> CURATOR-3.0 branch was broken in some capacity. Should I be branching off
> CURATOR-3.0-temp or something else?
> cheers
>
> On Wed, Aug 12, 2015 at 8:09 AM, Cameron McKenzie <mckenzie.cam@gmail.com>
> wrote:
> Will do. In the meantime could you please have a look at my suggested
> solution for CURATOR-228 (It's in the JIRA)? I don't want to start work on
> it until we have an agreed solution.
> cheers
>
> On Wed, Aug 12, 2015 at 12:23 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
> Hi Cameron,
>
> Go ahead and do CURATOR-214 - I assigned it to you.
>
> -JZ
>
>
>
> On August 9, 2015 at 6:47:50 PM, Cameron McKenzie (mckenzie.cam@gmail.com)
> wrote:
>
> Sounds reasonable, what's left for 3.0.0?
>
> I think that watcher removal is done. So just the host provider (
> https://issues.apache.org/jira/browse/CURATOR-213) and new create APIs (
> https://issues.apache.org/jira/browse/CURATOR-214).
>
> I'm happy to pick up the new create APIs if no one else is looking at it.
> cheers
>
>
> On Mon, Aug 10, 2015 at 9:39 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
> On August 9, 2015 at 5:15:36 PM, Cameron McKenzie (mckenzie.cam@gmail.com)
> wrote:
> As for Curator 3.0.0, any ideas when ZK 3.5.x is mean to get out of Alpha?
> I've seen some grumblings on the ZK mailing list, but nothing concrete. I
> guess we just need to be ready for that date whenever it is.
> cheers
> Cam
> Who knows :) But, I know people are using it in Production so I think we
> should just treat it as released software.
>
>
>
> -JZ
>
>
>
>
>

--001a11378846200810051d14f666--