Thank you to all voters. 

With 4 binding +1 votes and 1 non-binding +1 vote this vote passes. I'll cut 
this release tonight.

Thanks,
Abe

On Mon, Apr 23, 2018, at 08:24, Flavio Junqueira wrote:
> +1, verified the following:
> 
> - checksums and signature
> - build passes
> - rat tool output does not indicate any problem
> - LICENSE and NOTICE look both ok
> - local simple smoke tests work
> 
> -Flavio
> 
> 
> > On 2 Apr 2018, at 02:01, Michael Han <h...@apache.org> wrote:
> > 
> > +1
> > 
> > - verified xsum/sig.
> > - release notes looks good.
> > - verified cluster with different sizes.
> > - verified with few 4lw commands.
> > - verified data / log dir swap was fixed.
> > - all unit test passed.
> > 
> > 
> > On Wed, Mar 28, 2018 at 11:55 AM, Patrick Hunt <ph...@apache.org> wrote:
> > 
> >> +1. sig/xsum verified, RAT ran OK. I tested a few operational scenarios
> >> which seemed fine. Ran the tests and they passed. LGTM.
> >> 
> >> Patrick
> >> 
> >> On Mon, Mar 26, 2018 at 10:05 PM, Abraham Fine <af...@apache.org> wrote:
> >> 
> >>> This is a bugfix release candidate for 3.4.12. It fixes 22 issues,
> >>> including issues that
> >>> affect incorrect handling of the dataDir and the dataLogDir.
> >>> 
> >>> This candidate fixes an issue in the release notes of candidate 0.
> >>> 
> >>> The full release notes are available at:
> >>> 
> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> >>> projectId=12310801&version=12342040
> >>> 
> >>> *** Please download, test and vote by March 31st 2018, 23:59 UTC+0. ***
> >>> 
> >>> Source files:
> >>> http://people.apache.org/~afine/zookeeper-3.4.12-candidate-1/
> >>> 
> >>> Maven staging repo:
> >>> https://repository.apache.org/content/groups/staging/org/
> >>> apache/zookeeper/zookeeper/3.4.12/
> >>> 
> >>> The release candidate tag in git to be voted upon: release-3.4.12-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?
> >>> 
> >> 
> 

Reply via email to