+1 (non-binding)

- Built a 12 node cluster on Openstack VMs using Metron 0.3.1 Ambari Mpack and 
RPMs.
- Ran a sample bro topology test to validate enrichments and indexing are 
working fine. No issues found.

Thanks,
Anand




On 2/8/17, 8:45 AM, "Nick Allen" <[email protected]> wrote:

>+1 binding
>
>Valid checksums
>Build successful
>Integration tests successful
>Deploy of "Quick Dev" successful
>Deploy of "Full Dev" successful
>
>
>On Tue, Feb 7, 2017 at 11:18 AM, Casey Stella <[email protected]> wrote:
>
>> This is a call to vote on releasing Apache Metron 0.3.1-RC1 incubating
>>
>>
>> Full list of changes in this release:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.
>> 1-RC2-incubating/CHANGES
>>
>>
>> The tag/commit to be voted upon is apache-metron-0.3.0-rc1-incubating:
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.
>> git;a=shortlog;h=refs/tags/apache-metron-0.3.1-rc2-incubating
>>
>> The source archive being voted upon can be found here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.
>> 1-RC2-incubating/apache-metron-0.3.1-rc1-incubating.tar.gz
>>
>> Other release files, signatures and digests can be found here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/metron/0.3.
>> 1-RC2-incubating/
>>
>> The release artifacts are signed with the following key:
>>
>> https://git-wip-us.apache.org/repos/asf?p=incubator-metron.
>> git;a=blob;f=KEYS;h=8381e96d64c249a0c1b489bc0c234d9c260ba55e;hb=refs/tags/
>> apache-metron-0.3.1-rc2-incubating
>>
>>
>> Please vote on releasing this package as Apache Metron 0.3.1-RC2 incubating
>>
>>
>> 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.
>>
>>
>> [ ] +1 Release this package as Apache Metron 0.3.1-RC2 incubating
>>
>> [ ]  0 No opinion
>>
>> [ ] -1 Do not release this package because...
>>

Reply via email to