+1 on this Release Candidate Please see inline below the checks performed.
Cheers, Attila *Attila Simon* Software Engineer Email: s...@cloudera.com [image: Cloudera Inc.] On Mon, Sep 18, 2017 at 2:46 PM, Denes Arvay <de...@cloudera.com> wrote: > 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) > downloaded > - Check the md5/sha1 checksums > checked and verified > - 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 > gpg: assuming signed data in 'apache-flume-1.8.0-src.tar.gz' gpg: Signature made Fri Sep 15 15:04:39 2017 CEST using RSA key ID 4199ACFF gpg: Good signature from "Denes Arvay <de...@apache.org>" [unknown] gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 4CF1 5CF1 525F CE29 F66C 08FA 302C B2A8 4199 ACFF Fingerprint matches with your key from the KEY file obtained via a trusted https connection. - 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) > checked (besides file name mismatch the content is identical) > - 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) > mvn clean install -Dsurefire.rerunFailingTestsCount=10 -> passes [INFO] ------------------------------------------------------------ ------------ [INFO] Reactor Summary: [INFO] [INFO] Flume checkstyle project ........................... SUCCESS [ 1.301 s] [INFO] Apache Flume ....................................... SUCCESS [ 1.443 s] [INFO] Flume NG SDK ....................................... SUCCESS [01:15 min] [INFO] Flume NG Configuration ............................. SUCCESS [ 2.722 s] [INFO] Flume Auth ......................................... SUCCESS [ 7.071 s] [INFO] Flume NG Core ...................................... SUCCESS [08:17 min] [INFO] Flume NG Sinks ..................................... SUCCESS [ 0.231 s] [INFO] Flume NG HDFS Sink ................................. SUCCESS [02:40 min] [INFO] Flume NG IRC Sink .................................. SUCCESS [ 2.977 s] [INFO] Flume NG Channels .................................. SUCCESS [ 0.432 s] [INFO] Flume NG JDBC channel .............................. SUCCESS [ 35.675 s] [INFO] Flume NG file-based channel ........................ SUCCESS [05:26 min] [INFO] Flume NG Spillable Memory channel .................. SUCCESS [ 56.480 s] [INFO] Flume NG Node ...................................... SUCCESS [ 41.525 s] [INFO] Flume NG Embedded Agent ............................ SUCCESS [ 23.380 s] [INFO] Flume NG HBase Sink ................................ SUCCESS [04:54 min] [INFO] Flume NG ElasticSearch Sink ........................ SUCCESS [01:03 min] [INFO] Flume NG Morphline Solr Sink ....................... SUCCESS [ 16.488 s] [INFO] Flume Shared Utils ................................. SUCCESS [ 0.186 s] [INFO] Flume Shared Kafka Test Utils ...................... SUCCESS [ 0.749 s] [INFO] Flume Kafka Sink ................................... SUCCESS [ 41.873 s] [INFO] Flume HTTP/S Sink .................................. SUCCESS [ 12.705 s] [INFO] Flume NG Kite Dataset Sink ......................... SUCCESS [ 11.923 s] [INFO] Flume NG Hive Sink ................................. SUCCESS [ 40.225 s] [INFO] Flume Sources ...................................... SUCCESS [ 0.204 s] [INFO] Flume Scribe Source ................................ SUCCESS [ 5.345 s] [INFO] Flume JMS Source ................................... SUCCESS [ 23.410 s] [INFO] Flume Twitter Source ............................... SUCCESS [ 1.390 s] [INFO] Flume Kafka Source ................................. SUCCESS [02:09 min] [INFO] Flume Taildir Source ............................... SUCCESS [ 17.342 s] [INFO] flume-kafka-channel ................................ SUCCESS [03:36 min] [INFO] Flume legacy Sources ............................... SUCCESS [ 0.194 s] [INFO] Flume legacy Avro source ........................... SUCCESS [ 2.025 s] [INFO] Flume legacy Thrift Source ......................... SUCCESS [ 1.828 s] [INFO] Flume NG Clients ................................... SUCCESS [ 0.178 s] [INFO] Flume NG Log4j Appender ............................ SUCCESS [ 36.688 s] [INFO] Flume NG Tools ..................................... SUCCESS [ 2.793 s] [INFO] Flume NG distribution .............................. SUCCESS [ 16.495 s] [INFO] Flume NG Integration Tests ......................... SUCCESS [01:52 min] [INFO] ------------------------------------------------------------ ------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------ ------------ [INFO] Total time: 38:01 min [INFO] Finished at: 2017-09-19T13:03:37+02:00 [INFO] Final Memory: 552M/1821M [INFO] ------------------------------------------------------------ ------------ > - 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) > passes - Check the generated documents in the doc/ directory in the binary > artifact. > The directory called docs. Besides this, the content - userguide: no compilation errors, scrolling through looks ok - devguide: no compilation errors, scrolling through looks ok -javadoc: opening up clicking randomly around: looks ok - index.html: looks ok links seem to point to the right location - Although not referenced from index.html these seem to have content which looks good: - license.html, mail-lists.html, project-info.html -project-reports.html seems like garbage but not linked from any of these pages > - Check the CHANGELOG and RELEASE-NOTES files. > - CHANGELOG sanity checked, changes touched by me are included - RELEASE-NOTES: it says Flume 1.8.0 I don't know what else has to be checked there, so looks good to me. > - 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) > Checked. (possible licence change of these libs hans't checked) > > 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 <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/orgapach > eflume-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 > > >
