Github user cestella commented on the pull request:
https://github.com/apache/incubator-metron/pull/64#issuecomment-203428699
* Removed extraneous LICENSE files and COPYING files
* Fixed the verbiage for the cisco contribution in the LICENSE file
* Added link to the license file
Github user dlyle65535 commented on the pull request:
https://github.com/apache/incubator-metron/pull/64#issuecomment-203450229
+1 works great with EC2 deployment.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your p
Github user asfgit closed the pull request at:
https://github.com/apache/incubator-metron/pull/64
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the featur
Taylor, I noticed that you have uploading to repository.apache.org in the
template for the release vote. First, is that strictly required? Second,
if so, are there instructions? I'm having some problems uploading the
bundle created by the mvn repository plugin to a staging repo due to a
missing
This is a call to vote on releasing Apache Metron 0.1BETA-RC6
Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC6-incubating/CHANGES
The tag/commit to be voted upon is Metron_0.1BETA_rc6:
https://git-wip-us.apache.org/repos/asf?p=incubator-m
+ 1 (binding)
On 3/30/16, 8:58 AM, "James Sirota" wrote:
>This is a call to vote on releasing Apache Metron 0.1BETA-RC6
>
>Full list of changes in this release:
>
>https://dist.apache.org/repos/dist/dev/incubator/metron/0.1BETA-RC6-incubating/CHANGES
>
>The tag/commit to be voted upon is Met
+1 (binding)
On 3/30/16, 11:00 AM, "James Sirota" wrote:
>+ 1 (binding)
>
>
>
>
>On 3/30/16, 8:58 AM, "James Sirota" wrote:
>
>>This is a call to vote on releasing Apache Metron 0.1BETA-RC6
>>
>>Full list of changes in this release:
>>
>>https://dist.apache.org/repos/dist/dev/incubator/metron/
It's optional. Here are the instructions for publishing maven artifacts:
http://www.apache.org/dev/publishing-maven-artifacts.html
On Wed, Mar 30, 2016 at 8:52 AM, Casey Stella wrote:
> Taylor, I noticed that you have uploading to repository.apache.org in the
> template for the release vote. Fi
+1 binding
On Wed, Mar 30, 2016 at 12:01 Ryan Merriman
wrote:
> +1 (binding)
>
> On 3/30/16, 11:00 AM, "James Sirota" wrote:
>
> >+ 1 (binding)
> >
> >
> >
> >
> >On 3/30/16, 8:58 AM, "James Sirota" wrote:
> >
> >>This is a call to vote on releasing Apache Metron 0.1BETA-RC6
> >>
> >>Full list
I checked:
- DISCLAIMER exists
- NOTICE looks good
- LICENSE looks good (see notes below)
- signature is valid
- Apache license headers in source files (see notes below)
NOTES:
- In the LICENSE file, you don’t need to include the entire content of the
Mozilla Public License, the following text
Thanks, Taylor. Created Jira to address for next release:
https://issues.apache.org/jira/browse/METRON-90
On 3/30/16, 12:19 PM, "P. Taylor Goetz" wrote:
>I checked:
>
>- DISCLAIMER exists
>- NOTICE looks good
>- LICENSE looks good (see notes below)
>- signature is valid
>- Apache license h
+1 (binding)
* checked LICENSE, NOTICE
* verified signature
* built from source
* spun up vagrant instance
* verified status with documented instructions
Note on build problems with rc5 - they were due to some of my local maven
repo being owned by root - once I fixed that it worked fine.
It does
12 matches
Mail list logo