+1

* Verified checksums and signature files
* Verified that each jar in binary tarball is in the license
* Notice have copyright from 2012, we should update it (not a blocker in my 
mind)
* Checked top level files (NOTICE, ...)
* Run tests

Jarcec

On Wed, May 07, 2014 at 03:28:36PM -0700, Hari Shreedharan wrote:
> This is a vote for the next release of Apache Flume, version 1.5.0. We are
> voting on release candidate RC1.
> 
> It fixes the following issues:
>       http://s.apache.org/4eQ
> 
> *** 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.0-rc1/
> 
> Maven staging repo:
>   https://repository.apache.org/content/repositories/orgapacheflume-1001/
> 
> 
> The tag to be voted on:
> 
> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=8633220df808c4cd0c13d1cf0320454a94f1ea97
> 
> Flume's KEYS file containing PGP keys we use to sign the release:
>   http://www.apache.org/dist/flume/KEYS
> 
> 
> Thanks,
> Hari

Attachment: signature.asc
Description: Digital signature

Reply via email to