+ for this release candidate I checked the tarballs, compared with the git tag verified the signature License file looks good Ran a full build, tests passed Generated the site, looked ok.
Regards, Ferenc On Fri, Sep 22, 2017 at 10:53 PM, Hari Shreedharan <hshreedha...@apache.org> wrote: > Sorry for not voting yet. I can take a look early next week. If there are > enough binding votes before that, please push the release! > > On Thu, Sep 21, 2017 at 3:56 AM, Mike Percy <mpe...@apache.org> wrote: > > > +1 (binding) > > > > I only checked the source artifact, I didn't check the binary convenience > > artifacts. > > > > - Checksums and sigs match > > - LICENSE file looks good > > - README file looks good > > - Files match git tag > > - Ran a full build and all tests passed > > > > Thanks for managing this release Denes, and to the others that helped! > > > > Best, > > Mike > > > > On Fri, Sep 15, 2017 at 10:52 AM, Denes Arvay <de...@cloudera.com> > 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 > > > > > >
