I tried to address all of the issues discussed in the 1.5.1 release vote 
(Except the snappy issue — I didn’t want to upgrade Avro in a maintenance 
release, lets do it in 1.6?). 




If you find something out of place, let me know - we can spin another RC.


Thanks,
Hari

On Wed, Nov 12, 2014 at 1:15 PM, Hari Shreedharan
<[email protected]> wrote:

> This is the eighth release for Apache Flume as a top-level project,
> version 1.5.2. We are voting on release candidate RC1.
> This release fixes an incompatibility with Java 6 based clients found
> in Apache Flume 1.5.1 Release.
> It fixes the following
> issues:https://git-wip-us.apache.org/repos/asf?p=flume.git;a=blob;f=CHANGELOG;h=cc7321361d0b702ba870de20d6a3d2106987186a;hb=229442aa6835ee0faa17e3034bcab42754c460f5
> *** 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.2-rc1/
> <https://people.apache.org/~hshreedharan/apache-flume-1.5.2-rc1/>*
> Maven staging repo:
>   *https://repository.apache.org/content/repositories/orgapacheflume-1008/
> <https://repository.apache.org/content/repositories/orgapacheflume-1008/>*
> The tag to be voted on:
>   
> *https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=229442aa6835ee0faa17e3034bcab42754c460f5
> <https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=229442aa6835ee0faa17e3034bcab42754c460f5>*
> 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