➢ Should this bother us?
Yes and no. The important message is “Good signature from ”.
To validate my key, compare it’s fingerprint with this authoritative database:
https://people.apache.org/keys/committer/ .
Compare the full 40-character key fingerprint, not just the last 8 characters.
+1
* verified keys
* ran :
mvn -q -T 2C -DskipTests install && \
] 6:04 PM
mvn -q -T 2C org.jacoco:jacoco-maven-plugin:prepare-agent
surefire:test@unit-tests && mvn -q \
org.jacoco:jacoco-maven-plugin:prepare-agent surefire:test@integration-tests
&& mvn -q \
Github user JonZeolla closed the pull request at:
https://github.com/apache/metron/pull/586
---
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 feature is
Github user asfgit closed the pull request at:
https://github.com/apache/metron/pull/625
---
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 feature is
Github user mattf-horton commented on the issue:
https://github.com/apache/metron/pull/625
This has been +1'ed in email by the following reviewers:
@nickwallen : +1 Yes, definitely cruft. Good find.
@cestella : +1 to removing it. Other top level projects do not
GitHub user mattf-horton opened a pull request:
https://github.com/apache/metron/pull/625
METRON-1006 Remove Incubator DISCLAIMER file and fix Release Process doc
## Contributor Comments
The Release Process document at
Right, I looked and found nothing that seemed comparable for TLPs.
Thanks, I’ll proceed.
--Matt
On 6/27/17, 2:31 AM, "Casey Stella" wrote:
+1 to removing it. Other top level projects do not have a disclaimer (see,
for example, hbase:
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
OK, IWOMM.
I'm on irc if you want to jump on
---
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
Github user mmiklavc commented on the issue:
https://github.com/apache/metron/pull/530
Looking into it now, but building locally I see this:
```
$ mvn clean install -DskipTests -T 2C
...
[INFO] elasticsearch-shaded ... SKIPPED
[INFO]
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
Most recent commit, as @ottobackwards points out, merits some explanation.
Specifically it turns off the jacoco:prepare-agent from the Travis build
and allows us to just run the tests
Github user justinleet commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124317746
--- Diff: .travis.yml ---
@@ -17,7 +17,7 @@ before_install:
- export PATH=$M2_HOME/bin:$PATH
script:
- |
--- End diff --
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124314669
--- Diff: .travis.yml ---
@@ -17,7 +17,7 @@ before_install:
- export PATH=$M2_HOME/bin:$PATH
script:
- |
--- End diff --
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/metron/pull/624#discussion_r124314003
--- Diff:
metron-platform/metron-pcap-backend/src/test/java/org/apache/metron/pcap/integration/PcapTopologyIntegrationTest.java
---
@@ -90,23 +90,6
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
I have added more documentation and I'm working on documenting where things
are deployed
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user wardbekker commented on the issue:
https://github.com/apache/metron/pull/619
hey @cestella, @simonellistonball, see updated contributor notes. It's not
ready for a official pull request, but this gives a good idea on the impact on
the code for a working ES5.x
Github user justinleet commented on the issue:
https://github.com/apache/metron/pull/624
As a note, what I have is currently the first steps towards reusing infra.
It's not perfect, and it's not reused across classes.
There was an attempt to use the build matrix to split
Github user cestella commented on the issue:
https://github.com/apache/metron/pull/624
I submitted PRs against this branch to incorporate the suggested changes
above for:
* Selective shading for non-leaf projects to cut the build times
dramatically.
* `TaxiiIntegrationTest`
Github user ottobackwards commented on the issue:
https://github.com/apache/metron/pull/530
Thank you @mattf-horton, I was able to fix the links.
So, @mmiklavc et. al., can we frame our documentation discussion around
filling out and improving these documents?
---
If
+1
On June 27, 2017 at 05:31:22, Casey Stella (ceste...@gmail.com) wrote:
+1 to removing it. Other top level projects do not have a disclaimer (see,
for example, hbase: http://www-eu.apache.org/dist/hbase/stable)
On Tue, Jun 27, 2017 at 4:40 AM, Otto Fowler
wrote:
>
19 matches
Mail list logo