This vote is now closed.

I will send out the results in a separate email.

Thanks to all who voted!


Thank you,

Donat

On Mon, Oct 17, 2016 at 3:31 AM, Brock Noland <br...@apache.org> wrote:
> +1 (binding)
>
> Checked sigs and hashes, manual inspection of various other aspects.
>
> On Thu, Oct 13, 2016 at 12:54 PM, Hari Shreedharan <hshreedha...@apache.org>
> wrote:
>
>> +1 (binding)
>>
>> Signatures and checksums look good
>> Top level files are all good.
>> Build runs fine, simple agent with Seq source, memory channel and HDFS
>> sink run fine as well.
>>
>> On Thu, Oct 13, 2016 at 8:42 AM, Mike Percy <mpe...@apache.org> wrote:
>> > +1 (binding)
>> >
>> > There are some flaky tests which are listed below but I don't think they
>> > are release blockers.
>> >
>> > I performed the following checks:
>> >
>> > Binary convenience artifact:
>> > * Signature and checksums match
>> > * LICENSE, NOTICE, and README.md files in the binary convenience artifact
>> > look accurate and complete relative to the jars in lib/
>> > * Ran a very quick test with the binary artifact and it
>> > worked: ./bin/flume-ng agent -c conf -f
>> > conf/flume-conf.properties.template -n
>> > agent -Dflume.root.logger=DEBUG,console
>> > * Checked that the documentation in docs/ renders: Flume User Guide and
>> > Flume Dev Guide are OK. Also spot-checked that the new Kafka security
>> > documentation was included in the User Guide
>> >
>> > Source artifact:
>> > * Signature and checksums match
>> > * Built Flume from the source artifact using Oracle 1.7.0_80 on Ubuntu
>> > Linux 16.04, sanity tested the resulting binary using the above method
>> and
>> > it worked
>> > * RAT checks passed
>> > * Built a new source artifact out of the official source artifact and
>> > compiled it
>> > * I ran the unit tests. Most passed but the below two failed. These are
>> > flaky tests (we have a bunch of them in Flume) so I think it's fine not
>> to
>> > block the release on them.
>> >   * TestExecSource.testMonitoredCounterGroup - looks like a racy test
>> >   * TestSpillableMemoryChannel - didn't investigate
>> >
>> > RC2 looks good to me.
>> >
>> > Thanks for running this release, Donat!
>> >
>> > Mike
>> >
>> > On Wed, Oct 12, 2016 at 9:29 PM, Balazs Donat Bessenyei <
>> bes...@cloudera.com
>> >> wrote:
>> >
>> >> Hi All,
>> >>
>> >> This is the tenth release for Apache Flume as a top-level project,
>> >> version 1.7.0. We are voting on release candidate RC2.
>> >>
>> >> It fixes the following issues:
>> >>   https://raw.githubusercontent.com/apache/flume/flume-1.7/CHANGELOG
>> >>
>> >> *** 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:
>> >>   http://people.apache.org/~bessbd/apache-flume-1.7.0-rc2/
>> >>
>> >> Maven staging repo:
>> >>   https://repository.apache.org/content/repositories/
>> orgapacheflume-1020/
>> >>
>> >> The tag to be voted on:
>> >>   https://git-wip-us.apache.org/repos/asf?p=flume.git;a=
>> commit;h=511d868
>> >>
>> >> Flume's KEYS file containing PGP keys we use to sign the release:
>> >>   https://www.apache.org/dist/flume/KEYS
>> >>
>> >>
>> >> Thank you,
>> >>
>> >> Donat
>> >>
>>

Reply via email to