You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by Michael Han <ha...@cloudera.com> on 2017/04/03 17:26:07 UTC
[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
resigned artifacts.
The full release notes are available at:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12310801&version=12335444
**** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
Source files:
https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
Maven staging repo:
https://repository.apache.org/content/groups/staging/org/
apache/zookeeper/zookeeper/3.5.3-beta/
The tag to be voted upon:
*https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
<https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
ZooKeeper's KEYS file containing PGP keys we use to sign the release:
http://www.apache.org/dist/zookeeper/KEYS
Should we release this candidate?
[1]
http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
--
Cheers
Michael.
Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)
Posted by Flavio Junqueira <fp...@apache.org>.
Yeah, this one worked, thanks.
-Flavio
> On 14 Apr 2017, at 20:08, Michael Han <ha...@cloudera.com> wrote:
>
> gpg --keyserver keys.gnupg.net <http://keys.gnupg.net/> --recv 767E7473
Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release
3.5.3-beta candidate 1)
Posted by Michael Han <ha...@cloudera.com>.
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 <ha...@cloudera.com> wrote:
> 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) <ha...@apache.org>"
> [ultimate]
>
> My gpg version:
>
> gpg2 --version
>
> gpg (GnuPG) 2.0.30
>
> libgcrypt 1.7.6
>
> Copyright (C) 2015 Free Software Foundation, Inc.
>
> A search indicates others hit similar issue, maybe this is only
> reproducible for specific pgp and/or OS version?
>
> https://lists.gnupg.org/pipermail/gnupg-users/2015-October/054540.html
>
> On Fri, Apr 14, 2017 at 10:56 AM, Patrick Hunt <ph...@apache.org> wrote:
>
>> Did you import the KEYS?
>>
>> Patrick
>>
>> On Fri, Apr 14, 2017 at 10:42 AM, Flavio Junqueira <fp...@apache.org>
>> 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 CEST using RSA key ID
>> 767E7473
>> > gpg: requesting key 767E7473 from hkp server keys.gnupg.net
>> > : can't connect to `keys.gnupg.net': host not found
>> > gpgkeys: HTTP fetch error 7: couldn't connect: Not found
>> > gpg: no valid OpenPGP data found.
>> > gpg: Total number processed: 0
>> > gpg: Can't check signature: No public key
>> >
>> > Is there anything I'm doing wrong?
>> >
>> > -Flavio
>> >
>> > > On 03 Apr 2017, at 19:26, Michael Han <ha...@cloudera.com> 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
>> > > Implementation-Version information contained in the manifest file of
>> the
>> > > generated artifacts. There is no code changes, just regenerated and
>> > > resigned artifacts.
>> > >
>> > > The full release notes are available at:
>> > >
>> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> > > projectId=12310801&version=12335444
>> > >
>> > > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0.
>> ****
>> > >
>> > > Source files:
>> > > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
>> > >
>> > > Maven staging repo:
>> > > https://repository.apache.org/content/groups/staging/org/
>> > > apache/zookeeper/zookeeper/3.5.3-beta/
>> > >
>> > > The tag to be voted upon:
>> > > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
>> > > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
>> > >
>> > > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
>> > > http://www.apache.org/dist/zookeeper/KEYS
>> > >
>> > > Should we release this candidate?
>> > >
>> > > [1]
>> > > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
>> > 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
>> > CrHUrw%40mail.gmail.com%3E
>> > >
>> > > --
>> > > Cheers
>> > > Michael.
>> >
>> >
>>
>
>
>
> --
> Cheers
> Michael.
>
--
Cheers
Michael.
Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release
3.5.3-beta candidate 1)
Posted by Michael Han <ha...@cloudera.com>.
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) <ha...@apache.org>"
[ultimate]
My gpg version:
gpg2 --version
gpg (GnuPG) 2.0.30
libgcrypt 1.7.6
Copyright (C) 2015 Free Software Foundation, Inc.
A search indicates others hit similar issue, maybe this is only
reproducible for specific pgp and/or OS version?
https://lists.gnupg.org/pipermail/gnupg-users/2015-October/054540.html
On Fri, Apr 14, 2017 at 10:56 AM, Patrick Hunt <ph...@apache.org> wrote:
> Did you import the KEYS?
>
> Patrick
>
> On Fri, Apr 14, 2017 at 10:42 AM, Flavio Junqueira <fp...@apache.org> 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 CEST using RSA key ID
> 767E7473
> > gpg: requesting key 767E7473 from hkp server keys.gnupg.net
> > : can't connect to `keys.gnupg.net': host not found
> > gpgkeys: HTTP fetch error 7: couldn't connect: Not found
> > gpg: no valid OpenPGP data found.
> > gpg: Total number processed: 0
> > gpg: Can't check signature: No public key
> >
> > Is there anything I'm doing wrong?
> >
> > -Flavio
> >
> > > On 03 Apr 2017, at 19:26, Michael Han <ha...@cloudera.com> 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
> > > Implementation-Version information contained in the manifest file of
> the
> > > generated artifacts. There is no code changes, just regenerated and
> > > resigned artifacts.
> > >
> > > The full release notes are available at:
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12310801&version=12335444
> > >
> > > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0.
> ****
> > >
> > > Source files:
> > > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/groups/staging/org/
> > > apache/zookeeper/zookeeper/3.5.3-beta/
> > >
> > > The tag to be voted upon:
> > > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> > >
> > > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > > http://www.apache.org/dist/zookeeper/KEYS
> > >
> > > Should we release this candidate?
> > >
> > > [1]
> > > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> > 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
> > CrHUrw%40mail.gmail.com%3E
> > >
> > > --
> > > Cheers
> > > Michael.
> >
> >
>
--
Cheers
Michael.
Re: Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release
3.5.3-beta candidate 1)
Posted by Patrick Hunt <ph...@apache.org>.
Did you import the KEYS?
Patrick
On Fri, Apr 14, 2017 at 10:42 AM, Flavio Junqueira <fp...@apache.org> 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 CEST using RSA key ID 767E7473
> gpg: requesting key 767E7473 from hkp server keys.gnupg.net
> : can't connect to `keys.gnupg.net': host not found
> gpgkeys: HTTP fetch error 7: couldn't connect: Not found
> gpg: no valid OpenPGP data found.
> gpg: Total number processed: 0
> gpg: Can't check signature: No public key
>
> Is there anything I'm doing wrong?
>
> -Flavio
>
> > On 03 Apr 2017, at 19:26, Michael Han <ha...@cloudera.com> 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
> > Implementation-Version information contained in the manifest file of the
> > generated artifacts. There is no code changes, just regenerated and
> > resigned artifacts.
> >
> > The full release notes are available at:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12310801&version=12335444
> >
> > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
> >
> > Source files:
> > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/groups/staging/org/
> > apache/zookeeper/zookeeper/3.5.3-beta/
> >
> > The tag to be voted upon:
> > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> >
> > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/zookeeper/KEYS
> >
> > Should we release this candidate?
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
> CrHUrw%40mail.gmail.com%3E
> >
> > --
> > Cheers
> > Michael.
>
>
Can't verify signature of RC (Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)
Posted by Flavio Junqueira <fp...@apache.org>.
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 `keys.gnupg.net': host not found
gpgkeys: HTTP fetch error 7: couldn't connect: Not found
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: Can't check signature: No public key
Is there anything I'm doing wrong?
-Flavio
> On 03 Apr 2017, at 19:26, Michael Han <ha...@cloudera.com> 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
> Implementation-Version information contained in the manifest file of the
> generated artifacts. There is no code changes, just regenerated and
> resigned artifacts.
>
> The full release notes are available at:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310801&version=12335444
>
> **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
>
> Source files:
> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
>
> Maven staging repo:
> https://repository.apache.org/content/groups/staging/org/
> apache/zookeeper/zookeeper/3.5.3-beta/
>
> The tag to be voted upon:
> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
>
> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/zookeeper/KEYS
>
> Should we release this candidate?
>
> [1]
> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
>
> --
> Cheers
> Michael.
Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release
3.5.3-beta candidate 1)
Posted by Patrick Hunt <ph...@apache.org>.
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 <ha...@cloudera.com> wrote:
> 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 <
> rgs@itevenworks.net
> > wrote:
>
> > +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" <fp...@apache.org> wrote:
> >
> > > Would it be ok to extend the vote until mid next week?
> > >
> > > -Flavio
> > >
> > > > On 03 Apr 2017, at 18:26, Michael Han <ha...@cloudera.com> 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
> > > > Implementation-Version information contained in the manifest file of
> > the
> > > > generated artifacts. There is no code changes, just regenerated and
> > > > resigned artifacts.
> > > >
> > > > The full release notes are available at:
> > > >
> > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > > projectId=12310801&version=12335444
> > > >
> > > > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0.
> > ****
> > > >
> > > > Source files:
> > > > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> > > >
> > > > Maven staging repo:
> > > > https://repository.apache.org/content/groups/staging/org/
> > > > apache/zookeeper/zookeeper/3.5.3-beta/
> > > >
> > > > The tag to be voted upon:
> > > > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > > > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> > > >
> > > > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > > > http://www.apache.org/dist/zookeeper/KEYS
> > > >
> > > > Should we release this candidate?
> > > >
> > > > [1]
> > > > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> > > 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
> > > CrHUrw%40mail.gmail.com%3E
> > > >
> > > > --
> > > > Cheers
> > > > Michael.
> > >
> > >
> >
>
>
>
> --
> Cheers
> Michael.
>
Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release
3.5.3-beta candidate 1)
Posted by Michael Han <ha...@cloudera.com>.
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 <rgs@itevenworks.net
> wrote:
> +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" <fp...@apache.org> wrote:
>
> > Would it be ok to extend the vote until mid next week?
> >
> > -Flavio
> >
> > > On 03 Apr 2017, at 18:26, Michael Han <ha...@cloudera.com> 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
> > > Implementation-Version information contained in the manifest file of
> the
> > > generated artifacts. There is no code changes, just regenerated and
> > > resigned artifacts.
> > >
> > > The full release notes are available at:
> > >
> > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > > projectId=12310801&version=12335444
> > >
> > > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0.
> ****
> > >
> > > Source files:
> > > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> > >
> > > Maven staging repo:
> > > https://repository.apache.org/content/groups/staging/org/
> > > apache/zookeeper/zookeeper/3.5.3-beta/
> > >
> > > The tag to be voted upon:
> > > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> > >
> > > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > > http://www.apache.org/dist/zookeeper/KEYS
> > >
> > > Should we release this candidate?
> > >
> > > [1]
> > > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> > 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
> > CrHUrw%40mail.gmail.com%3E
> > >
> > > --
> > > Cheers
> > > Michael.
> >
> >
>
--
Cheers
Michael.
Re: Extending the vote (was: Re: [VOTE] Apache ZooKeeper release
3.5.3-beta candidate 1)
Posted by Raúl Gutiérrez Segalés <rg...@itevenworks.net>.
+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" <fp...@apache.org> wrote:
> Would it be ok to extend the vote until mid next week?
>
> -Flavio
>
> > On 03 Apr 2017, at 18:26, Michael Han <ha...@cloudera.com> 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
> > Implementation-Version information contained in the manifest file of the
> > generated artifacts. There is no code changes, just regenerated and
> > resigned artifacts.
> >
> > The full release notes are available at:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12310801&version=12335444
> >
> > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
> >
> > Source files:
> > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/groups/staging/org/
> > apache/zookeeper/zookeeper/3.5.3-beta/
> >
> > The tag to be voted upon:
> > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> >
> > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/zookeeper/KEYS
> >
> > Should we release this candidate?
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> 201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVij
> CrHUrw%40mail.gmail.com%3E
> >
> > --
> > Cheers
> > Michael.
>
>
Extending the vote (was: Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1)
Posted by Flavio Junqueira <fp...@apache.org>.
Would it be ok to extend the vote until mid next week?
-Flavio
> On 03 Apr 2017, at 18:26, Michael Han <ha...@cloudera.com> 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
> Implementation-Version information contained in the manifest file of the
> generated artifacts. There is no code changes, just regenerated and
> resigned artifacts.
>
> The full release notes are available at:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310801&version=12335444
>
> **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
>
> Source files:
> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
>
> Maven staging repo:
> https://repository.apache.org/content/groups/staging/org/
> apache/zookeeper/zookeeper/3.5.3-beta/
>
> The tag to be voted upon:
> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
>
> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/zookeeper/KEYS
>
> Should we release this candidate?
>
> [1]
> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
>
> --
> Cheers
> Michael.
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by Michael Han <ha...@cloudera.com>.
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 <arshad.mohammad.k@gmail.com
> wrote:
> +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, Michael Han <ha...@cloudera.com> 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
> > Implementation-Version information contained in the manifest file of the
> > generated artifacts. There is no code changes, just regenerated and
> > resigned artifacts.
> >
> > The full release notes are available at:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12310801&version=12335444
> >
> > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
> >
> > Source files:
> > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/groups/staging/org/
> > apache/zookeeper/zookeeper/3.5.3-beta/
> >
> > The tag to be voted upon:
> > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> >
> > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/zookeeper/KEYS
> >
> > Should we release this candidate?
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> 201703.mbox/%3CCA%
> > 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
> >
> > --
> > Cheers
> > Michael.
> >
>
--
Cheers
Michael.
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by Rakesh Radhakrishnan <ra...@apache.org>.
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 Thu, Apr 6, 2017 at 10:21 AM, Mohammad Arshad <
arshad.mohammad.k@gmail.com> wrote:
> +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, Michael Han <ha...@cloudera.com> 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
> > Implementation-Version information contained in the manifest file of the
> > generated artifacts. There is no code changes, just regenerated and
> > resigned artifacts.
> >
> > The full release notes are available at:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12310801&version=12335444
> >
> > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
> >
> > Source files:
> > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/groups/staging/org/
> > apache/zookeeper/zookeeper/3.5.3-beta/
> >
> > The tag to be voted upon:
> > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> >
> > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/zookeeper/KEYS
> >
> > Should we release this candidate?
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/20170
> 3.mbox/%3CCA%
> > 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
> >
> > --
> > Cheers
> > Michael.
> >
>
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by Mohammad Arshad <ar...@gmail.com>.
+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, Michael Han <ha...@cloudera.com> 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
> Implementation-Version information contained in the manifest file of the
> generated artifacts. There is no code changes, just regenerated and
> resigned artifacts.
>
> The full release notes are available at:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310801&version=12335444
>
> **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
>
> Source files:
> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
>
> Maven staging repo:
> https://repository.apache.org/content/groups/staging/org/
> apache/zookeeper/zookeeper/3.5.3-beta/
>
> The tag to be voted upon:
> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
>
> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/zookeeper/KEYS
>
> Should we release this candidate?
>
> [1]
> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%
> 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
>
> --
> Cheers
> Michael.
>
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by Michael Han <ha...@cloudera.com>.
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, Kandhare, Arvind <Ar...@dell.com>
wrote:
> +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" <fp...@apache.org> wrote:
>
> +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 <sa...@gmail.com>
> wrote:
> >
> > +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 <ph...@apache.org>
> wrote:
> >
> >> +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 <ha...@cloudera.com>
> 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
> >>> Implementation-Version information contained in the manifest file
> of the
> >>> generated artifacts. There is no code changes, just regenerated and
> >>> resigned artifacts.
> >>>
> >>> The full release notes are available at:
> >>>
> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >>> projectId=12310801&version=12335444
> >>>
> >>> **** Please download, test and vote by April 8th 2017, 23:59
> UTC+0. ****
> >>>
> >>> Source files:
> >>> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> >>>
> >>> Maven staging repo:
> >>> https://repository.apache.org/content/groups/staging/org/
> >>> apache/zookeeper/zookeeper/3.5.3-beta/
> >>>
> >>> The tag to be voted upon:
> >>> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> >>> <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> >>>
> >>> ZooKeeper's KEYS file containing PGP keys we use to sign the
> release:
> >>> http://www.apache.org/dist/zookeeper/KEYS
> >>>
> >>> Should we release this candidate?
> >>>
> >>> [1]
> >>> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> >> 201703.mbox/%3CCA%
> >>> 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%
> 40mail.gmail.com%3E
> >>>
> >>> --
> >>> Cheers
> >>> Michael.
> >>>
> >>
>
>
>
>
--
Cheers
Michael.
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by "Kandhare, Arvind" <Ar...@dell.com>.
+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" <fp...@apache.org> wrote:
+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 <sa...@gmail.com> wrote:
>
> +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 <ph...@apache.org> wrote:
>
>> +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 <ha...@cloudera.com> 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
>>> Implementation-Version information contained in the manifest file of the
>>> generated artifacts. There is no code changes, just regenerated and
>>> resigned artifacts.
>>>
>>> The full release notes are available at:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12310801&version=12335444
>>>
>>> **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
>>>
>>> Source files:
>>> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
>>>
>>> Maven staging repo:
>>> https://repository.apache.org/content/groups/staging/org/
>>> apache/zookeeper/zookeeper/3.5.3-beta/
>>>
>>> The tag to be voted upon:
>>> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
>>> <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
>>>
>>> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
>>> http://www.apache.org/dist/zookeeper/KEYS
>>>
>>> Should we release this candidate?
>>>
>>> [1]
>>> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
>> 201703.mbox/%3CCA%
>>> 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
>>>
>>> --
>>> Cheers
>>> Michael.
>>>
>>
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by Flavio Junqueira <fp...@apache.org>.
+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 <sa...@gmail.com> wrote:
>
> +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 <ph...@apache.org> wrote:
>
>> +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 <ha...@cloudera.com> 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
>>> Implementation-Version information contained in the manifest file of the
>>> generated artifacts. There is no code changes, just regenerated and
>>> resigned artifacts.
>>>
>>> The full release notes are available at:
>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>>> projectId=12310801&version=12335444
>>>
>>> **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
>>>
>>> Source files:
>>> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
>>>
>>> Maven staging repo:
>>> https://repository.apache.org/content/groups/staging/org/
>>> apache/zookeeper/zookeeper/3.5.3-beta/
>>>
>>> The tag to be voted upon:
>>> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
>>> <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
>>>
>>> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
>>> http://www.apache.org/dist/zookeeper/KEYS
>>>
>>> Should we release this candidate?
>>>
>>> [1]
>>> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
>> 201703.mbox/%3CCA%
>>> 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
>>>
>>> --
>>> Cheers
>>> Michael.
>>>
>>
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by sandeep shrids <sa...@gmail.com>.
+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 <ph...@apache.org> wrote:
> +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 <ha...@cloudera.com> 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
> > Implementation-Version information contained in the manifest file of the
> > generated artifacts. There is no code changes, just regenerated and
> > resigned artifacts.
> >
> > The full release notes are available at:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > projectId=12310801&version=12335444
> >
> > **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
> >
> > Source files:
> > https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
> >
> > Maven staging repo:
> > https://repository.apache.org/content/groups/staging/org/
> > apache/zookeeper/zookeeper/3.5.3-beta/
> >
> > The tag to be voted upon:
> > *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> > <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
> >
> > ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> > http://www.apache.org/dist/zookeeper/KEYS
> >
> > Should we release this candidate?
> >
> > [1]
> > http://mail-archives.apache.org/mod_mbox/zookeeper-dev/
> 201703.mbox/%3CCA%
> > 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
> >
> > --
> > Cheers
> > Michael.
> >
>
Re: [VOTE] Apache ZooKeeper release 3.5.3-beta candidate 1
Posted by Patrick Hunt <ph...@apache.org>.
+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 <ha...@cloudera.com> 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
> Implementation-Version information contained in the manifest file of the
> generated artifacts. There is no code changes, just regenerated and
> resigned artifacts.
>
> The full release notes are available at:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12310801&version=12335444
>
> **** Please download, test and vote by April 8th 2017, 23:59 UTC+0. ****
>
> Source files:
> https://home.apache.org/~hanm/zookeeper/zookeeper-3.5.3-beta-rc1/
>
> Maven staging repo:
> https://repository.apache.org/content/groups/staging/org/
> apache/zookeeper/zookeeper/3.5.3-beta/
>
> The tag to be voted upon:
> *https://github.com/apache/zookeeper/tree/release-3.5.3-rc1
> <https://github.com/apache/zookeeper/tree/release-3.5.3-rc1>*
>
> ZooKeeper's KEYS file containing PGP keys we use to sign the release:
> http://www.apache.org/dist/zookeeper/KEYS
>
> Should we release this candidate?
>
> [1]
> http://mail-archives.apache.org/mod_mbox/zookeeper-dev/201703.mbox/%3CCA%
> 2Bi0x1LTONuaT6H%2BiOHAT2O1SVPKnQzzQh8vKMzWJVijCrHUrw%40mail.gmail.com%3E
>
> --
> Cheers
> Michael.
>