Hey all, we need more votes!

So far we have 6 +1’s (including mine) and no 0’s or -1’s.
BUT, only two are binding, ie from PMC members.
Rules require 3 or more PMC member +1’s.  Could one more 
member please step up and vote?

Thanks!
--Matt

On 6/29/17, 3:00 PM, "James Sirota" <[email protected]> wrote:

    +1 (Binding)
    
    * Verified Keys
    * Verified mvn clean install completed successfully
    * Verified AWS install of core via Mpack
    
    
    29.06.2017, 09:14, "Justin Leet" <[email protected]>:
    > +1 (Non-binding)
    >
    > * Verified Keys
    > * Verified mvn clean install completed successfully
    > * Ran full dev: saw data flow through, ran a couple of the REST APIs, and
    > opened up and clicked through a bit of the Management API.
    > * Examined site-book and didn't see any issues
    >
    > On Thu, Jun 29, 2017 at 11:46 AM, Casey Stella <[email protected]> wrote:
    >
    >>  +1 (binding)
    >>  * Verified keys
    >>  * Verified mvn build
    >>  * Verified unit and integration tests run
    >>  * Verified license check runs
    >>  * Verified fulldev spun up with smoketest
    >>
    >>  On Wed, Jun 28, 2017 at 8:10 PM, Anand Subramanian <
    >>  [email protected]> wrote:
    >>
    >>  > +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" <[email protected]> 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) <[email protected]>
    >>  > >
    >>  > >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)
    >>  > >
    >>  > >
    >>  > >
    >>  >
    
    ------------------- 
    Thank you,
    
    James Sirota
    PPMC- Apache Metron (Incubating)
    jsirota AT apache DOT org
    
    

Reply via email to