Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

Thanks everyone that participates the verification of this release! Your help is greatly appreciated. Given 3 binding votes from PMC members and no objections, I've published release artifacts and documents and announced this release on dev/user list just now. On Fri, Apr 14, 2017 at 3:42 PM,

Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

+1 We are interacting with ZK via Distributedlog incubator and curator 2.11.0 recipes. To test these bits, I have pointed them to a server running ZK 3.5.3.-beta candidate bits. All our scenarios work as expected. Regards, Arvind On 4/14/17, 3:31 PM, "Flavio Junqueira" wrote:

Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

+1, I have checked license and notice, RAT report, digests and signature. I have also ran a few local tests. Looks good! I have an observation about the RAT report, but I'll send to the list separately. -Flavio > On 13 Apr 2017, at 05:47, sandeep shrids wrote: > >

Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

Yeah, this one worked, thanks. -Flavio > On 14 Apr 2017, at 20:08, Michael Han wrote: > > gpg --keyserver keys.gnupg.net --recv 767E7473

Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

Another idea is to try explicit request the key see if it works gpg --keyserver keys.gnupg.net --recv 767E7473 If it still can't connect to the keys server, then maybe a network issue? On Fri, Apr 14, 2017 at 10:59 AM, Michael Han wrote: > Works for me: > > gpg2 --verify

Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

Works for me: gpg2 --verify zookeeper-3.5.3-beta.tar.gz.asc zookeeper-3.5.3-beta.tar.gz gpg: Signature made Mon Apr 3 09:39:14 2017 PDT using RSA key ID 767E7473 gpg: Good signature from "Michael Han (CODE SIGNING KEY) " [ultimate] My gpg version: gpg2 --version gpg (GnuPG)

Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

Did you import the KEYS? Patrick On Fri, Apr 14, 2017 at 10:42 AM, Flavio Junqueira wrote: > Michael, > > I can't verify the signature of the RC: > > $ gpg2 --verify zookeeper-3.5.3-beta.tar.gz.asc > zookeeper-3.5.3-beta.tar.gz > gpg: Signature made Mon Apr 3 18:39:14 2017

Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

Michael, I can't verify the signature of the RC: $ gpg2 --verify zookeeper-3.5.3-beta.tar.gz.asc zookeeper-3.5.3-beta.tar.gz gpg: Signature made Mon Apr 3 18:39:14 2017 CEST using RSA key ID 767E7473 gpg: requesting key 767E7473 from hkp server keys.gnupg.net : can't connect to

Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

+1 Tests passed for me. Started zk in standalone and in cluster mode. Used command-line for my tests, java version "1.8.0_121". Minor comment: the artifact ending with .tar.gz is not a gzip archive but a tar. -Sandeep On Thu, Apr 13, 2017 at 5:28 AM, Patrick Hunt wrote: > +1

Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

I've been on vacation - spent some time reviewing the release candidate today and voting. Keep in mind that the date for a release vote is the _minimum_ time, not the max. The intent is to allow everyone to participate. Patrick On Fri, Apr 7, 2017 at 12:25 PM, Michael Han

Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

+1 xsum/sig verified, RAT ran clean. Tests passed for me. I started a few different cluster sizes, ran the command line client and it all seemed fine. Patrick On Mon, Apr 3, 2017 at 10:26 AM, Michael Han wrote: > Hi all, > > This is the second release candidate (RC1) of

Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

Thanks, Michael, for your efforts to get this release out. +1 - built zookeeper jar from source with jdk1.8.0_45 - ran zk unit test suite, all passed - tested with a couple of different ensemble sizes, exec basic cli commands, jmx beans - verified sig/xsum - checked release notes Rakesh On

Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

Sure, let's extends the vote for another cycle and now the vote will end on *April 14th 2017, 23:59 UTC+0. * On Fri, Apr 7, 2017 at 11:57 AM, Raúl Gutiérrez Segalés wrote: > +1 -- Is am traveling so I need a few more days to test this in one of our > dev clusters. > > >

Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

+1 -- Is am traveling so I need a few more days to test this in one of our dev clusters. -rgs On Apr 7, 2017 2:53 PM, "Flavio Junqueira" wrote: > Would it be ok to extend the vote until mid next week? > > -Flavio > > > On 03 Apr 2017, at 18:26, Michael Han

Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)

Would it be ok to extend the vote until mid next week? -Flavio > On 03 Apr 2017, at 18:26, Michael Han wrote: > > Hi all, > > This is the second release candidate (RC1) of 3.5.3-beta, following the > first release candidate (RC0) cut off last week [1]. It fixes incorrect >

Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

Thanks Arshad for your vote! Friendly reminder, the vote will expire in two days. I am expecting to see more votes coming from you guys that's on this mailing list. Anyone? We value any inputs on helping making the release happen. On Wed, Apr 5, 2017 at 9:51 PM, Mohammad Arshad

Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

+1 Run all tests on Ubuntu 15.10 on java 7. Built tar ball on Ubuntu and Windows. Run releaseaudit Generated documentation Verified basic features, create znode,delete znode, get data, set data, get acl, set acl etc. Verified 4lw commands. Verified CLI commands On Mon, Apr 3, 2017 at 10:56 PM,

[VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1

Hi all, This is the second release candidate (RC1) of 3.5.3-beta, following the first release candidate (RC0) cut off last week [1]. It fixes incorrect Implementation-Version information contained in the manifest file of the generated artifacts. There is no code changes, just regenerated and