+1 (binding)

- Built from source
- Checked NOTICE and LICENSE
- Checked digests and signature
- Ran tests and some simple smoke tests
- Checked release notes
- Ran rat and couldn't spot any problem in the report
- Tested that a maven project resolves the dependency fine with the staging repo

-Flavio

> On 01 Sep 2016, at 05:50, Chris Nauroth <[email protected]> wrote:
> 
> +1 (binding)
> 
> -Downloaded tarball and verified signature and checksums.
> -Verified content of LICENSE.txt and NOTICE.txt.
> -Verified correct version information in src/c/include/winconfig.h.
> -All unit tests passed.
> 
> Rakesh, thank you for your hard work on this release.
> 
> --Chris Nauroth
> 
> On 8/23/16, 2:24 AM, "Rakesh Radhakrishnan" <[email protected]> wrote:
> 
>    This is the third release candidate for 3.4.9. This candidate removes the
>    extra *.asc files found in the
>    second candidate.
> 
>    This is a bugfix release candidate for 3.4.9. It fixes 21 issues, including
>    issues that affect ACL cache
>    in DataTree never removes entries, prevent multiple init of login object in
>    each ZKSaslClient instance,
>    ZK service becomes unavailable when leader fails to write transaction log,
>    upgrade netty version due
>    to security vulnerability (CVE-2014-3488) and others.
> 
>    The full release notes are available at:
> 
>    
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310801&version=12334700
> 
>    *** Please download, test and vote by August 30th 2016, 23:59 UTC+0. ***
> 
>    Source files:
>    http://people.apache.org/~rakeshr/zookeeper-3.4.9-candidate-2
> 
>    Maven staging repo:
>    
> https://repository.apache.org/content/groups/staging/org/apache/zookeeper/zookeeper/3.4.9
> 
>    The tag to be voted upon:
>    https://svn.apache.org/repos/asf/zookeeper/tags/release-3.4.9-rc2
> 
>    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?
> 
>    Thanks,
>    Rakesh
> 
> 

Reply via email to