Sorry for the delay in voting. -1 on RC2 because the source artifact should match the tag, but it has a .git folder in there:
$ diff -r apache-flume-1.9.0-src src-tag Only in apache-flume-1.9.0-src: .git I am not sure why we don't just use the scripts designed to generate source artifacts (dev-support/generate-source-release.sh) Other than that problem, everything else seems to look good: - Checksums and sigs match - README and LICENSE look good - Binary artifact runs - Source artifact builds and tests pass on Ubuntu bionic Thanks, Mike On Sun, Dec 9, 2018 at 8:26 PM Ferenc Szabo <szabofe...@apache.org> wrote: > Dear Flume Community, > > This is the 12th release for Apache Flume as a top-level project, > version 1.9.0. We are voting on release candidate RC1. > > It fixes the following issues: > > https://raw.githubusercontent.com/apache/flume/release-1.9.0-rc2/CHANGELOG > > *** Please cast your vote within the next 72 hours *** > > The tarball (*.tar.gz), signature (*.asc), and checksums (*.sha512) > for the source and binary artifacts can be found here: > http://people.apache.org/~szaboferee/apache-flume-1.9.0-rc2/ > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapacheflume-1031/ > > The tag to be voted on: > > > https://git-wip-us.apache.org/repos/asf?p=flume.git;a=commit;h=cb8f1f576d365641030499b434d1a0629f46f884 > > Flume's KEYS file containing PGP keys we use to sign the release: > https://svn.apache.org/repos/asf/flume/dist/KEYS > > > Regards, > Ferenc >
