Thank you Donat for your vote, I'm going to send out the results as we have three PMC +1s. Thanks for pointing out the checksum problem, I think it is generated during maven deploy. I have created a ticket to track this issue: https://issues.apache.org/jira/browse/FLUME-3183
Denes On Sun, Oct 1, 2017 at 1:00 PM Bessenyei Balázs Donát <[email protected]> wrote: > +1 > > Please, note that I have only found .sha1 checksums, but as per > http://www.apache.org/dev/release-distribution#sigs-and-sums it is > recommended that "The checksum SHOULD be generated using SHA-512." > > > Donat > > > 2017-09-29 12:35 GMT+02:00 <[email protected]>: > > +1 > > > > My apologies for the late vote. > > > > Jarcec > > > >> On Sep 15, 2017, at 1:52 PM, Denes Arvay <[email protected]> wrote: > >> > >> Hi Flume Community, > >> > >> This is the eleventh release for Apache Flume as a top-level project, > >> version 1.8.0. We are voting on release candidate RC2. > >> > >> It fixes the following issues: > >> > https://raw.githubusercontent.com/apache/flume/release-1.8.0-rc2/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/~denes/apache-flume-1.8.0-rc2/ > >> > >> Maven staging repo: > >> > https://repository.apache.org/content/repositories/orgapacheflume-1026/ > >> > >> The tag to be voted on: > >> https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=43a3c40 > >> > >> Flume's KEYS file containing PGP keys we use to sign the release: > >> https://www.apache.org/dist/flume/KEYS > >> > >> Thank you, > >> Denes > > >
