+1

* Verified checksums and signature files
* Verified that each jar in binary tarball is in the license
* Checked top level files (NOTICE, ...)
* Run tests

Jarcec

> On Nov 6, 2014, at 3:17 PM, Hari Shreedharan <hshreedha...@cloudera.com> 
> wrote:
> 
> This is the seventh release for Apache Flume as a top-level project,
> version 1.5.1. We are voting on release candidate RC1.
> 
> It fixes the following issues:
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob_plain;f=CHANGELOG;hb=c74804226bcee59823c0cbc09cdf803a3d9e6920
> 
> *** Please cast your vote within the next 72 hours ***
> 
> The tarball (*.tar.gz), signature (*.asc), and checksums (*.md5, *.sha1)
> for the source and binary artifacts can be found here:
>  https://people.apache.org/~hshreedharan/apache-flume-1.5.1-rc1/
> 
> Maven staging repo:
>  https://repository.apache.org/content/repositories/orgapacheflume-1006/
> 
> The tag to be voted on:
>  
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=c74804226bcee59823c0cbc09cdf803a3d9e6920
> 
> Flume's KEYS file containing PGP keys we use to sign the release:
>  http://www.apache.org/dist/flume/KEYS
> 
> Thanks,
> Hari

Reply via email to