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.55d2a451.4c92735f.164@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>
	<CANykduaBo=V480Xvk2vO_kHzHD=_j61rNPKVRcwoPkBJxAcmYw@mail.gmail.com>
	<etPan.55cac0bc.79798c48.166@Jordans-MacBook-Pro.local>
	<CANykduY_OqjLuLheg=whT3gPvjdv0kTyf=yq1aO+duVrx6VhtQ@mail.gmail.com>
	<etPan.55cac3c4.7d7373c7.166@Jordans-MacBook-Pro.local>
	<CANykduZGmNK+xxGCpQCZQz+xdxKpuPetY_GnNZ3yh6QczRCX2g@mail.gmail.com>
	<CANykduZ1TEifzV1duFw25a1GUhv92qoEiirnuHVo1ykV_+_waQ@mail.gmail.com>
	<etPan.55cacba5.64a345c2.166@Jordans-MacBook-Pro.local>
	<CANykduYfrvJarFMOtChvG0qgkaz3Y4e=BQDp6AsJKavDPnEriw@mail.gmail.com>
	<CALuNCpibCH-px9Q_UBM_vreBcjjQxmCX0LpXkU95SVeXa1A-hQ@mail.gmail.com>
	<etPan.55cb7642.a1a099.166@Jordans-MacBook-Pro.local>
	<CALuNCpgghkL1N4xiDdZCxkN4XPtaOvxkFCCp+YgTMvo67AA4ug@mail.gmail.com>
	<CALuNCpj-xJutW8=_7d7cg9wzZFuD9NbXinHMWmhX0PzjM1RoFw@mail.gmail.com>
	<etPan.55cb9ef0.10dfc0e.166@Jordans-MacBook-Pro.local>
	<CALuNCpir2qzJyz2Usoi8nU=aVM6XwgDhT_Q4OrpQCs3HvoE1cA@mail.gmail.com>
	<CALuNCpi=CkMJayBrz1KwcfO0d_D=vT6cPT5mH03SOtq8MP95bA@mail.gmail.com>
	<CALuNCphy=Zeyp9sSkDof3hnnt6+9pme1FQORLjVpkLqckwq1mw@mail.gmail.com>
	<6A96E809-8DC6-4BBF-B40D-B542B6E4D888@jordanzimmerman.com>
	<CALuNCpgh3kK+hqUmje46u+LzT6o5VKLXxy2ut4Nhz5bJug7-Bg@mail.gmail.com>
	<CANykduZPfOixGKe0OHx9A7qsmTLehZ=RVvr5XPj+-=eF_-Jn7Q@mail.gmail.com>
	<CALuNCpiYQWWYtzB1KC2Nw=rKn3saahUs=795q3iSaYaYf2yx6g@mail.gmail.com>
	<CAFAMeY+oa0z7M8KpT44YQ-uthsL9-2EsvyU8T2he37PT=E18kw@mail.gmail.com>
	<CALuNCpimUvZ2bJ7o_fk1m9kSbsyuz0CkxKkuYHknJn0=AsCTcw@mail.gmail.com>
	<CANykduZeGM0ce1ciph-o=rjMP9dFpx=ywrwEFnUbYfcadJ5NPQ@mail.gmail.com>
	<CALuNCpijYV-xqunj=D2YG3QLBXY4vuuWOw8E6uWJh9syhB4O4Q@mail.gmail.com>
	<CANykduZB=HgUNoBpAwu-PrFfhRrX9r2vvcPLxj=OxM8zXg__Hw@mail.gmail.com>
	<CALuNCpgUdnJXZTDP6vjQfJ9ot4tn_nFy-0hzH=wWsUmpYNfnpA@mail.gmail.com>
	<CANykduYvFp8aHeoNytpe_mpZ4m5BLzKYSYNav27QjTPXo7SUwA@mail.gmail.com>
	<CAFAMeY+FbObsjm5yoRCHneuLQD3D8-WFvitWG6z3jwtKY=D84w@mail.gmail.com>
	<CALuNCpgani-roZrNrPLHCSMUR8L5AwobCmeW7_e7vp+bBChrLw@mail.gmail.com>
	<90EAFA8B-696D-47C3-ADD6-E15589D4C67F@jordanzimmerman.com>
	<CANykduYPWHQkvp1i-EB68KSmAiD9DBv2EVTxGZL5BjcZ3wHxTA@mail.gmail.com>
	<etPan.55d2a451.4c92735f.164@Jordans-MacBook-Pro.local>
Date: Mon, 17 Aug 2015 23:27:37 -0400
Message-ID: 
 <CALuNCphi+LktAuqyWECEEAw9vadJYWpLb01A5rKLBhLk4FA3Dw@mail.gmail.com>
Subject: Re: Next Steps
From: Scott Blum <dragonsinth@gmail.com>
To: "dev@curator.apache.org" <dev@curator.apache.org>
Cc: Cameron McKenzie <mckenzie.cam@gmail.com>
Content-Type: multipart/alternative; boundary=001a113ecfdaf22346051d8d7fde

--001a113ecfdaf22346051d8d7fde
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I think just confirm that ZooDefs.CONFIG_NODE is the correct watcher path
for getConfig()?

On Mon, Aug 17, 2015 at 11:19 PM, Jordan Zimmerman <
jordan@jordanzimmerman.com> wrote:

> Sorry - it=E2=80=99s hard to follow this thread. What do I need to do?
>
> -Jordan
>
>
>
> On August 17, 2015 at 6:18:21 PM, Cameron McKenzie (mckenzie.cam@gmail.co=
m)
> wrote:
>
> Thanks Scott,
> I've just merged CURATOR-217 into master and have one small issue.
>
> Jordan, with the changes you made with to the Watching.java class, the
> getWatcher() call now takes a CuratorFramework reference and a path
> reference.
>
> The GetConfigBuilderImpl breaks when merging because it's using the old
> getWatcher() call that doesn't exist any more. This isn't an issue to fix=
,
> but I'm just wondering what path reference should be used for the
> configuration case, as it's a different sort of watch. It's just passed t=
o
> the getConfig() call on the ZooKeeper class. It seems that I can't just
> pass in a null path as this gets validated. Suggestions?
>
> cheers
>
>
> On Tue, Aug 18, 2015 at 3:30 AM, Jordan Zimmerman <
> jordan@jordanzimmerman.com> wrote:
>
> > Great work. Thank you.
> >
> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > Jordan Zimmerman
> >
> > > On Aug 17, 2015, at 12:10 PM, Scott Blum <dragonsinth@gmail.com>
> wrote:
> > >
> > > This is now done, sorry for the delay. Let me describe the current
> state
> > > of the world:
> > >
> > > CURATOR-215-original, CURATOR-160-original, CURATOR-3.0-old,
> > > CURATOR-3.0-temp - these are the old versions of all the branches, we
> > > should consider pruning them at some point.
> > >
> > > CURATOR-215, CURATOR-160, CURATOR-3.0 - these are fixed/rebased
> versions
> > of
> > > the branches we should stick with.
> > >
> > > *ALL MASTER COMMITS ARE NOW MERGED INTO CURATOR-3.0.* There is nothin=
g
> > > that has been committed to master that isn't in 3.0 now.
> > >
> > > Procedures going forward:
> > >
> > > - If you're working on stuff for 2.8 / 2.9, branch from master and
> > > merge/commit to master.
> > >
> > > - If you're working on stuff for 3.0, branch from CURATOR-3.0 and
> > > merge/commit to CURATOR-3.0.
> > >
> > > - Periodically, we'll want to get master changes into 3.0. To do this=
,
> > *check
> > > out CURATOR-3.0*, and merge master into that, then push the result
> after
> > > fixing conflicts (which should be small / non-existent). *Don't do it
> > the
> > > other way, don't check out master and merge 3.0 into it.*
> > >
> > > For discussion: there is a *3.0-rejects* branch. One of the commits
> > there
> > > is and added System.out.println that I think we don't want. The other
> > one
> > > is the work to migrate to fasterxml Jackson. I think we actually want
> > this
> > > commit on 3.0. Please take a look and let me know, if we want this
> > commit,
> > > we should cherry-pick it onto 3.0. I'm happy to do that.
> > >
> > > Everything I did should be reversible, so let me know if I screwed
> > anything
> > > up!
> > >
> > > --Scott
> >
>

--001a113ecfdaf22346051d8d7fde--