+1 (non-binding)

* Brought up Metron stack on 12-node CentOS7 openstack cluster
* Verify all services come up fine [PASS]
* Bro, YAF and snort - ingest into respective kafka topics and write indices 
[PASS]
* Add squid telemetry, ingest into kafka topic and write indices [PASS]
* Metron YAF Zeppelin dashboard with sample ingested YAF data [PASS]
* Management UI and REST Swagger UI sanity check [PASS]


-Anand 





On 6/28/17, 12:06 AM, "Matt Foley" <ma...@apache.org> wrote:

>This is a call to vote on releasing this rc4 as “Apache Metron 0.4.0”.
>(Note: this is rc4 because the release candidate needed to be modified with 
>another commit after the rc3 tag was pushed to public.)
>
>Full list of changes in this release:
>https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/RELEASE_NOTES
>
>The tag/commit to be voted upon is:
>d52f574f8294e453ecad3871526858a0c3c2033d (tag apache-metron-0.4.0-rc4)
>
>The source archive being voted upon can be found here:
>https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/apache-metron-0.4.0-rc4.tar.gz
>and in github at:
>https://github.com/apache/metron/tree/Metron_0.4.0 
>
>Other release files, signatures and digests can be found here:
>https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/KEYS
>
>The release artifacts are signed with the following key:
>https://dist.apache.org/repos/dist/dev/metron/0.4.0-RC4/KEYS
>pub   rsa4096/4169AA27ECB31663 2011-07-31 [SCEA]
>Key fingerprint = 7854 36A7 8258 6B71 829C  67A0 4169 AA27 ECB3 1663
>uid = Matthew Foley (CODE SIGNING KEY) <ma...@apache.org>
>
>Please vote on releasing this package as Apache Metron 0.4.0.
>When voting, please list the actions taken to verify the release.
>
>Recommended build validation and verification instructions are posted here:
>https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds
>
>This vote will be open for at least 72 hours.  Please vote one of the 
>following responses:
>+1 Release this package as Apache Metron 0.4.0-RC4
>0 No opinion
>-1 Do not release this package because...
> 
>Thank you,
>--Matt
>(your friendly release manager)
>
>
>

Reply via email to