[GitHub] metron pull request #1028: METRON-1575: Add leet gpg public key to the KEYS ...

[justinleet <gi...@git.apache.org>]

GitHub user justinleet opened a pull request:

    https://github.com/apache/metron/pull/1028

    METRON-1575: Add leet gpg public key to the KEYS file

    ## Contributor Comments
    Added public key to keyfile.  Make sure nothing seems wrong.
    
    ## Pull Request Checklist
    
    Thank you for submitting a contribution to Apache Metron.  
    Please refer to our [Development Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235) for the complete guide to follow for contributions.  
    Please refer also to our [Build Verification Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview) for complete smoke testing guides.  
    
    
    In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
    
    ### For all changes:
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at [Metron Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically master)?
    
    
    ### For code changes:
    - [ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
      ```
      mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh 
      ```
    
    #### Note:
    Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
    It is also recommended that [travis-ci](https://travis-ci.org) is set up for your personal repository such that your branches are built there before submitting a pull request.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/justinleet/metron leetKey

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/metron/pull/1028.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1028
    
----
commit 108a253c027b602c860112693cc19fe308b076c8
Author: justinjleet <ju...@...>
Date:   2018-05-23T18:43:30Z

    Adding public key to the file

----


---

[GitHub] metron issue #1028: METRON-1575: Add leet gpg public key to the KEYS file

[cestella <gi...@git.apache.org>]

Github user cestella commented on the issue:

    https://github.com/apache/metron/pull/1028
  
    +1 by inspection


---

[GitHub] metron pull request #1028: METRON-1575: Add leet gpg public key to the KEYS ...

[asfgit <gi...@git.apache.org>]

Github user asfgit closed the pull request at:

    https://github.com/apache/metron/pull/1028


---