Hi All,

I'd like to encourage everybody to check the RC2 and provide feedback about
it. It's quite simple, just do the following steps:
- Download the artifacts from the people.apache.org link I've sent in the
initial email (see below)
- Check the md5/sha1 checksums
- Verify the signature: import the KEYS file (link below, howto in the KEYS
file), then verify with gpg --verify apache-flume-1.8.0-src.tar.gz.asc
and gpg --verify apache-flume-1.8.0-bin.tar.gz.asc
- Check that the downloaded artifacts match the ones in the maven staging
repo (org.apache.flume:flume-ng-dist:1.8.0, link to the repo below)
- Extract the source tarball, compile and run the unit tests (note: some
flaky tests might break, you might want to use
the surefire.rerunFailingTestsCount flag)
- Extract the binary tarball. You should be able to run it with one of the
bin/flume-ng* scripts. (e.g. ./bin/flume-ng agent -c conf -f
conf/flume-conf.properties.template -n agent
-Dflume.root.logger=DEBUG,console)
- Check the generated documents in the doc/ directory in the binary
artifact.
- Check the CHANGELOG and RELEASE-NOTES files.
- Check that all the 3rd party jars are listed in the LICENSE file (the
jars can be found in the binary package's lib/ directory)

Of course if you do only a subset of these checks that'd be also a great
help.

Thank you,
Denes


On Fri, Sep 15, 2017 at 7: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
>

Reply via email to