lunteer to take over for a while.
> > > > >
> > > > > Thanks to Matt for all the help through the last couple releases!
> > > > >
> > > > > Justin
> > > > >
> > > > > On Thu, May 10, 2018 at 11:06 AM,
e.org" , Matt Foley
Subject: Re: [DISCUSS] Using JSON Path to support more complex documents with
the JSONMap Parser
Sure it helps, but I am not sure I answered __your__ questions?
As I mentioned, we already use
Map rawMap
= JSONUtils.INSTANCE.load(originalString,
new
TypeReference>() {
NiFi used this approach, I believe that
JSONPath provides a flexible mechanism for defining
the targets within the document, and would make this more usable across
various document structures.
We already do full document with simple json btw.
On January 25, 2018 a
Hi Otto,
Oddly, I had reason a couple weeks ago to try to figure out a streaming parser
for very large json objects -- altho it was in Python rather than Java.
Search showed two basic approaches, both unsurprisingly modeled on xml
processing:
- SAX-like parsing
- XPath-like parsing
Both are capa
tarballs.
For your reading pleasure, the change list is appended to this message.
Best regards,
--Matt Foley
release manager
Metron CHANGES (in reverse chron order):
METRON-1373 RAT failure for metron-interface/metron-alerts (mattf-horton)
closes apache/metron#875
METRON-1313 Update metron
Bravo.
On 1/2/18, 8:43 AM, "Justin Leet" wrote:
The PR is merged into master, and all relevant PRs have a comment noting
that adding the header is required.
As a reminder, this means Apache headers are required on all markdown files
and this will be enforced by rat.
t;> * Validated the list of changes
> >> * Checksums
> >> * Sigs
> >> * Build
> >> * Tests
> >> * Full Dev
> >>
> >> On Tue, Dec 19, 2017 at 6:23 AM, Matt Foley wrote:
> >>
> >> >
Colleagues,
This is a call to vote on releasing Apache Metron 0.4.2 and its associated
metron-bro-plugin-kafka 0.1.0.
The release candidate is available at
https://dist.apache.org/repos/dist/dev/metron/0.4.2-RC2/
Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/metro
Perhaps under “build_utils” we should add a subdirectory for “release_utils”.
From: Casey Stella
Date: Friday, December 15, 2017 at 10:50 AM
To: "dev@metron.apache.org"
Cc: Matt Foley
Subject: Re: [DISCUSS] Upcoming Release
That script seems great, nick! Perhaps we should adjus
ached to the release originate
from? Does it get pulled out of JIRA or do they come from the commit log?
My apologies for not staying on top of my JIRAs.
On Tue, Dec 12, 2017 at 2:21 PM, Matt Foley wrote:
> Thanks to Jon, Otto, and Nick for looking o
+1 from me too, Justin. Great idea.
On 12/14/17, 12:44 PM, "zeo...@gmail.com" wrote:
A huge +1 from me. This would be great
On Thu, Dec 14, 2017 at 3:39 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> +1 from me, great idea Justin. I did a bit of digging
viewed the other artifacts like release notes.
Running the RAT check on a 'clean' Metron does not produce any errors for
me. It is only after building Metron, which pulls in additional Node
dependencies, does the RAT check fail.
On Sun, Dec 10, 2017 at 4:41
Yes, but let’s see if anyone else find other issues.
From: Otto Fowler
Date: Saturday, December 9, 2017 at 6:16 AM
To: Matt Foley , "dev@metron.apache.org"
Subject: Re: [DISCUSS] Upcoming Release
So RC2 then?
On December 8, 2017 at 20:43:21, Matt Foley (mfo...@hortonworks.
name has changed from
a0b6b99c10d9a13dc67e to f56deed131e58bd7ee04. Sigh. Did the version of Font
Awesome fonts change?
On 12/8/17, 5:26 PM, "Matt Foley" wrote:
I remember having trouble with this bundle.css file on the last release,
but I can’t remember what we did about it
alerts/dist/styles.f56deed131e58bd7ee04.bundle.css
*
On December 8, 2017 at 04:34:24, Matt Foley (ma...@apache.org) wrote:
Colleagues,
I’ve posted Metron-0.4.2-RC1 and Metron-bro-plugin-kafka-0.1 to
https://dist.apache.org/repos/dist/dev/
a documentation
update that fixes a few broken Stellar docs that already has aa +1, I just
need to merge it.
Jon
On Mon, Dec 4, 2017, 17:01 Casey Stella wrote:
> I would be in favor of a release at this point.
>
> On Mon, Dec 4, 2017 at 4:
Good, I’ll build the RC tonight. Thanks Jon.
--Matt
From: "zeo...@gmail.com"
Date: Thursday, December 7, 2017 at 12:27 PM
To: Matt Foley
Subject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'
Otto, your understanding is correct, but given Mattf'
> Jon
>
> On Thu, Dec 7, 2017 at 2:32 PM Matt Foley wrote:
>
>> I can start the release process tonight.
>>
>>
>>
>> Jon, you mentioned you want to commit
>>
>> > https://github.com/apache/metron/
Allen
Date: Thursday, December 7, 2017 at 10:13 AM
To: "dev@metron.apache.org"
Cc: Matt Foley
Subject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'
I am more interested in getting a release cut. If me moving to the (a) camp
gets us to consensus and c
r projects like NiFi
handle things as well.
On December 4, 2017 at 17:14:41, Matt Foley (ma...@apache.org) wrote:
Okay, looking at this from the perspective of making a release:
We have two choices:
a) I can simply make a 0.1 (or 1.0 or 0.4.
iterative work on the plugin, which would
then make the decision to spin it out now premature.
Then again, I might be wrong ;)
On November 27, 2017 at 19:58:11, Matt Foley (ma...@apache.org) wrote:
[Please pardon me that the below is a little labored. I’m trying to
understand the implication
include a release of the
current state of the metron-bro-plugin-kafka. I will continue the discussion
in that thread as to the process for accomplishing that, but plan on it
happening.
Regards,
--Matt
On 11/26/17, 6:26 PM, "Matt Foley" wrote:
Hope everyone (at least in the U.S.) h
[Please pardon me that the below is a little labored. I’m trying to understand
the implications for both release and use, which requires some explanation as
well as the two questions needed. Q1 and Q2 below are probably the same
question, asked in slightly different contexts. Please consider
Hope everyone (at least in the U.S.) had a great Thanksgiving holiday.
Regarding status of the release effort, still pending METRON-1252, so not
making the release branch yet.
Regards,
--Matt
On 11/17/17, 1:32 PM, "Matt Foley" wrote:
(With release manager hat on)
The
version be 0.4.3?
Ryan
On Fri, Nov 17, 2017 at 3:31 PM, Matt Foley wrote:
> (With release manager hat on)
>
> The community has proposed a release of Metron in the near future,
> focusing on Meta-alerts running in Elasticsearch.
> Congrats
(With release manager hat on)
The community has proposed a release of Metron in the near future, focusing on
Meta-alerts running in Elasticsearch.
Congrats on getting so many of the below already done. At this point, only
METRON-1252, and the discussion of how to handle joint release of the Met
There’s two issues, I think:
(1) We’d like to be able to version and evolve the main body of Metron and the
metron-bro-plugin-kafka separately.
(2) We want to be able to assure that each release of Metron has a
known-working version of metron-bro-plugin-kafka
At a very simple level, we can ach
There’s two issues, I think:
(1) We’d like to be able to version and evolve the main body of Metron and the
metron-bro-plugin-kafka separately.
(2) We want to be able to assure that each release of Metron has a
known-working version of metron-bro-plugin-kafka
At a very simple level, we can ac
I’ve been listening. Looks like there are still a number of major issues to be
committed first, right?
The discussion on this thread constitutes sufficient engagement, I think,
especially given the Subject line :-)
Would the folks working on the 6 issues listed by Nick care to suggest a
cut-off
that this is a clean approach so I rolled back
the wiki changes. Thanks,
Jon
On Tue, Oct 24, 2017 at 2:34 PM Matt Foley wrote:
> The release wouldn’t have been made if the build didn’t succeed.
> And the Release Manager doesn’t need one more fiddly m
oesn't make
sense
> in the published release documentation. No sense in fixing
retrospectively.
>
> -Kyle
>
> On Mon, Oct 23, 2017 at 3:13 PM Matt Foley wrote:
>
> > I agree with Justin. This micro-feature is intended as a github widge
I agree with Justin. This micro-feature is intended as a github widget, which
causes the top-level README to give all viewers an immediate flag whether the
build is healthy or not. It does not belong in a rendered site-book.
Removing the widget during site-book build, can be done with a one-li
Oct 11, 2017 at 9:54 PM, Matt Foley wrote:
> You can avoid the permission issues by attaching it to an Apache jira.
>
> On 10/11/17, 6:10 PM, "James Sirota" wrote:
>
> I can't see it. You probably want to link to a google drive
You can avoid the permission issues by attaching it to an Apache jira.
On 10/11/17, 6:10 PM, "James Sirota" wrote:
I can't see it. You probably want to link to a google drive
11.10.2017, 18:01, "Michael Miklavcic" :
> I attached a PDF - shows up on my end. Is that not coming th
Hi all,
Otto and I had an off-line discussion about this, and we think we have a
constructive suggestion that will allow chunking the feature branch to some
extent, which will of course make it easier to review. Otto is willing to make
a series of PRs, each of which must be reviewed and committ
Many thanks to all who contributed, and enjoy your new release!
Warm regards,
--Matt Foley
release manager
James Sirota" wrote:
+1
14.09.2017, 11:37, "Casey Stella" :
> I ran it up and forgot to vote. +1 binding
> - ran in full-dev
> - verified signatures
> - stellar works
>
> On Thu, Sep 14, 2017 at 9:52 AM, Matt Foley wrote:
&g
date, we have only one
binding vote so far (thank you Nick) altho we also have 3 votes in favor from
non-PMC committers.
The rules permit the vote to remain open, so could a couple more PMC members
please review and vote?
Thanks,
--Matt
On 9/13/17, 1:24 PM, "Matt Foley" wrote:
at 2:08 PM
To: Matt Foley
Cc: Laurens Vets , "dev@metron.apache.org"
Subject: Re: Elasticsearch masters_also_are_datanodes doesn't work.
Here's what I found. Data is flowing into ES indexes. I can change the
"masters_also_are_datanodes" property and it is reflec
topics and write indices [PASS]
> > * Add squid telemetry, ingest into kafka topic and write indices [PASS]
> > * Management UI and REST Swagger UI sanity check [PASS]
> >
> > Regards,
> > Anand
> >
> >
> >
> >
&g
Sorry, you’ve beat me.
Mike, what have you found in full-dev? Does ES work correctly there?
From: Laurens Vets
Date: Wednesday, September 13, 2017 at 1:14 PM
To: Matt Foley
Cc: "dev@metron.apache.org" , Michael Miklavcic
Subject: Re: Elasticsearch masters_also_are_datanodes do
user id that has
privs to change this config? Did you use non-default user configuration with
Ambari, and if so are you running with an admin-priv ambari account?
From: Laurens Vets
Date: Tuesday, September 12, 2017 at 8:32 PM
To: "dev@metron.apache.org"
Cc: Michael Miklavcic ,
sticsearch expert, so if someone else knows different,
please say so.
Hope this helps more than obfuscates.
--Matt
From: Michael Miklavcic
Date: Tuesday, September 12, 2017 at 4:54 PM
To: "dev@metron.apache.org"
Cc: Matt Foley
Subject: Re: Elasticsearch masters_also_a
Laurens, please open a jira. Altho it may seem obvious, please include full
repro.
This may be a showstopper, as it presumably (?) prevents ES from working on a
single-node deployment?
On 9/10/17, 4:01 PM, "Laurens Vets" wrote:
Another issue I noticed. Setting "masters_also_are_datanodes"
Colleagues,
This is a call to vote on releasing Apache Metron 0.4.1.
The release candidate is available at
https://dist.apache.org/repos/dist/dev/metron/0.4.1-RC4/
Full list of changes in this release:
https://dist.apache.org/repos/dist/dev/metron/0.4.1-RC4/CHANGES
The github tag to be voted up
C whenever
we're ready.
On Fri, Sep 8, 2017 at 8:24 PM, Casey Stella wrote:
> Yeah, I fixed the dependencies_with_url problem in METRON-1169. Let's
> pull that one in and the rat check one and cut a new RC. I'm -1
>
> On Fri, Sep
t; +
sys.argv[1])
ValueError: Unable to find these components:
ch.hsr:geohash:jar:1.3.0:compile
org.locationtech.spatial4j:spatial4j:jar:0.6:compile
in the acceptable list of components: ./dependencies_with_url.csv
I suspect GeoHash requires an update in the “dependencies_with_url.csv” file.
T
Colleagues,
This is a call to vote on releasing Apache Metron 0.4.1.
The release candidate is available at
https://dist.apache.org/repos/dist/dev/metron/0.4.1-RC3/
The candidate is RC3 because along the way I committed tags for two previous
versions that were later invalidated before they were
Hi Ryan, yup, got it. It’s in.
On 9/8/17, 1:25 PM, "Ryan Merriman" wrote:
Matt,
This was committed a few hours. I think you saw it but just wanted to make
sure.
Ryan
> On Sep 7, 2017, at 11:26 AM, Matt Foley wrote:
>
> Okay. Please
Looks like everything’s in now. Thanks very much everyone for the efforts!
I’m spinning the RC and will have it out for vote shortly.
--Matt
On 9/7/17, 11:41 PM, "Matt Foley" wrote:
METRON-1163 turns out to be invalid, due to a bad maven settings file. It
is no longe
METRON-1163 turns out to be invalid, due to a bad maven settings file. It is
no longer an issue.
Just waiting for the last couple items.
On 9/7/17, 9:26 AM, "Matt Foley" wrote:
Okay. Please ping when committed.
Also, any input on https://issues.apache.org/jira/browse/M
Hi,
You may have seen notification for a change I made in the “Release Process”
wiki page. The purpose of the change is to delay pushing the RC# tag to the
public repo until AFTER one goes thru the verification steps on the release
candidate.
The reason is that on this release I’ve already gon
iew (
https://github.com/apache/metron/pull/729 and
https://github.com/apache/metron/pull/730) and should make it in soon. It
would be good to include these if possible.
Ryan
On Thu, Sep 7, 2017 at 12:23 AM, Matt Foley wrote:
> I’ve got a
,
--Matt
From: Matt Foley on behalf of Matt Foley
Date: Tuesday, September 5, 2017 at 10:01 AM
To: "dev@metron.apache.org"
Subject: Re: [DISCUSS] Metron release 0.4.1
Great, working on it!
From: Nick Allen
Date: Tuesday, September 5, 2017 at 8:00 AM
To: Casey Stella , "z
Great, working on it!
From: Nick Allen
Date: Tuesday, September 5, 2017 at 8:00 AM
To: Casey Stella , "zeo...@gmail.com"
Cc: Anand Subramanian , Matt Foley
, "dev@metron.apache.org"
Subject: Re: [DISCUSS] Metron release 0.4.1
All set here. Let's get this s
mple and I think are very helpful for troubleshooting. I
> don't
> > >> want to hold up the release, but it would be a "nice to have" to get
> > these
> > >> in.
> > >>
> > >> If anyone has cycles
Aug 29, 2017 at 1:35 PM, Matt Foley wrote:
> Hi all,
> Thanks for your inputs. The three PRs Nick mentioned have been
> successfully closed.
> Casey, do you have an ETA for these two PRs? (PR#709 and 717)
> Thanks,
> --Matt
>
> On
y all
> relate to the Profiler. My other outstanding PRs are less important.
>
>- https://github.com/apache/metron/pull/705
>- https://github.com/apache/metron/pull/707
>- https://github.com/apache/metron/pull/708
>
>
>
>
Hello all,
At the meeting this morning, the community expressed the wish to create a new
release, to be a point release and not including METRON-777.
Therefore, I propose to create release 0.4.1 from Metron master branch, with
whatever additional commits the community considers vital and can get
Eesh, sorry, please ignore. This was incorrect, due to reading two diff blocks
as contiguous.
On 8/16/17, 9:58 PM, "mattf-horton" wrote:
Github user mattf-horton commented on a diff in the pull request:
https://github.com/apache/metron/pull/530#discussion_r133623540
life easier too. At that point, I'll just kill the existing PR and put out
new ones when I have some free time.
On Fri, Aug 11, 2017 at 2:42 PM, Matt Foley wrote:
> We can wait until 777 goes in, but any smaller PRs should just roll with
> it.
> I’
Justin do the commit, and all
open PRs immediately do an update merge – which in the vast majority of cases
will be fully automatic in the merge, and unnecessary to review in the PR.
--Matt
From: Otto Fowler
Date: Friday, August 11, 2017 at 11:23 AM
To: Matt Foley , "dev@metron.apache.org"
Regarding METRON-1087, I’m in favor of freezing commits for a day, to let
Justin re-run the script for METRON-1087 over all of current master, and commit
it.
Perhaps, for assurance, this commit should only include the fully-automated
“vast majority”; the couple dozen files that needed manual fix
Good eye, Otto!
From: Otto Fowler
Date: Wednesday, August 2, 2017 at 2:12 PM
To: Matt Foley , "dev@metron.apache.org"
, "u...@metron.apache.org"
Subject: Re: profiler Syntax error
Can you try the rule without ‘in’ as a key?
“in” is a reserved word in Stellar.
What that
Hi Dima,
Is it possible that the input parser is giving an unreasonable value for
“destination_ip”? Or perhaps fails to provide an end quote for that value?
Does this profile fail on the first message to be consumed, or does it get a
ways into the data stream and then choke? In either case, c
On Wed, Jul 26, 2017 at 6:31 PM, Matt Foley wrote:
> There’s a couple other places you could put config info (but maybe not
> saved searches):
> - Zookeeper
> - metron-alerts-ui/config.xml or config.json file
> - the Ambari database, w
Hi Justin,
Technically, acceptance into the code base with appropriate review and +1’s
signifies lazy consensus of all committers (since any committer can blackball a
PR with a single justified -1).
If you (or any community member) is concerned that people didn’t have
sufficient opportunity to
Well, Linux in general at least. CentOS 7 is known to work fine. Ubuntu has
worked most of the time; Ryan’s PR#669 today was to stabilize another bit of it.
On 7/28/17, 9:13 AM, "Laurens Vets" wrote:
I highly suspect the fact that you're trying to compile Metron on
Windows is the pro
Really good discussion thread, thanks for opening it Justin.
I’m a fan of adding javadocs to the publicly available doc set. It’s not the
most important of the items listed below, but it is easy, and will push people
to be more attentive to dev documentation.
METRON-759 is open for that, and I
There’s a couple other places you could put config info (but maybe not saved
searches):
- Zookeeper
- metron-alerts-ui/config.xml or config.json file
- the Ambari database, whichever it happens to be
Questions that influence the decision include:
1. Should there be one configuration shared am
r as a standard entity [RFC6901] but not as
part of the JSON spec.]
From: Otto Fowler
Date: Friday, July 14, 2017 at 10:42 AM
To: Matt Foley , "dev@metron.apache.org"
Subject: Re: [DISCUSSION] METRON-1046 -> Stellar Files for multiple statement
execution
I think the ‘files
In the abstract, this is a good idea. I see it as related to METRON-987, which
was the first step in allowing sequences of Stellar statements (aka "programs"
:-) ) instead of just unrelated groups of single statements. Your proposal
lets us really work with programs as first-class entities.
H
I think PR#481, for the first two-thirds of METRON322 (sub-tasks 2, 3, 4, and
7), is ready for review and inclusion. If folks have time to review it would
be appreciated.
Thanks,
--Matt
changes, please
bring it up and we’ll correct.
Thanks,
--Matt
On 7/5/17, 2:47 PM, "Matt Foley" wrote:
(The below proposal is also stated in
https://issues.apache.org/jira/browse/METRON-1020 )
The following proposed changes are small, but not just editorial in nature,
x27;t
overlooked.
Jon
On Wed, Jul 5, 2017 at 4:40 AM Matt Foley wrote:
> Now that METRON-877 is in, I would like to proceed with Steps 3-6 of the
> remaining work to separate out Stellar functionality as an independent
> module. A couple people have suggested
Vote passes with
+1 : 4 votes (3 binding, 1 non-binding)
0 : none
-1 : none
I’ll edit the doc to reflect the change.
Thanks,
--Matt
On 7/6/17, 10:53 AM, "Matt Foley" wrote:
Thanks, all. That’s 3 binding +1’s, so I’m going to proceed with
METRON-1021.
Vote needs to stay ope
On Fri, Jul 7, 2017 at 2:47 PM, Otto Fowler
wrote:
> This was my original inclination and Casey’s as well when we spoke. I
> think Nick has some good points however, so I created this thread.
>
> Thanks for replying!
>
>
> On July 7, 2
e logic is more cohesive, simplifies
testing. That's what we've done in most places.
On 7/7/17, 11:48 AM, "Otto Fowler" wrote:
Wait, Matt are you saying the answer is ‘neither’ and we should have a 3rd
layer? That both call?
On Fri, Jul 7, 2017
Hi all,
At the risk of getting suddenly unpopular (:-) I would like to argue the other
side.
Architecturally I disagree with having REST invoke Stellar, or in general
making Stellar the single point of contact for management functionality.
Several reasons:
1. The architectural component proper
t of sense.
On Wed, Jul 5, 2017 at 5:47 PM, Matt Foley wrote:
> (The below proposal is also stated in https://issues.apache.org/
> jira/browse/METRON-1020 )
>
> The following proposed changes are small, but not just editorial in
> nature, hence will require
(The below proposal is also stated in
https://issues.apache.org/jira/browse/METRON-1020 )
The following proposed changes are small, but not just editorial in nature,
hence will require vote of the community to change. Our bylaws don’t have an
action type of Modifying Policy, but it’s probably f
BTW, if you’ve recently accessed any URIs under http://metron.apache.org/, you
may need to hit “refresh” in your browser to see the new updated versions.
On 7/5/17, 1:35 PM, "Matt Foley" wrote:
Friends and Colleagues,
I’m happy to announce the completion and release of Apa
Friends and Colleagues,
I’m happy to announce the completion and release of Apache Metron 0.4.0.
Besides a bunch of great new features, this is also our first release as a TLP.
The public website at http://metron.apache.org/ has been updated and has
correct links to the new downloads and docs.
F
And another way suggested by Jon’s statement, is to not squash the commit, but
leave at least one of each committer’s contributions intact. That might not be
too hard to add to the prepare-commit script, it’s just an invocation of
interactive rebase/squash.
On 7/5/17, 10:32 AM, "Matt
uash merge into
the speculative
branch). Not a big issue though, I guess, just need to make sure it isn't
overlooked.
Jon
On Wed, Jul 5, 2017 at 4:40 AM Matt Foley wrote:
> Now that METRON-877 is in, I would like to proceed with Steps 3-6 of the
Okay, I’ll undertake to add to the committer’s guide before the first PR.
From: Otto Fowler
Date: Wednesday, July 5, 2017 at 6:28 AM
To: "dev@metron.apache.org" , Matt Foley
Subject: Re: [Request for Consensus Approval] dev branch for Stellar additional
work
Just want
Now that METRON-877 is in, I would like to proceed with Steps 3-6 of the
remaining work to separate out Stellar functionality as an independent module.
A couple people have suggested that this further development should be done in
a Metron “dev branch”, where:
a) changes are more visible than i
in Kibana
On Fri, Jun 30, 2017 at 12:24 PM, Matt Foley wrote:
> 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 mem
o at this point. Any objections, Matt?
On Mon, Jul 3, 2017 at 2:39 PM, Matt Foley wrote:
> https://issues.apache.org/jira/browse/INFRA-14502 has been opened.
>
> On 7/3/17, 11:25 AM, "Matt Foley" wrote:
>
> It seems propagation from g
https://issues.apache.org/jira/browse/INFRA-14502 has been opened.
On 7/3/17, 11:25 AM, "Matt Foley" wrote:
It seems propagation from git-wip-us.apache.org/repos/asf/metron to
github.com/apache/metron is currently broken. If you browse
https://git1-us-west.apache.org/r
It seems propagation from git-wip-us.apache.org/repos/asf/metron to
github.com/apache/metron is currently broken. If you browse
https://git1-us-west.apache.org/repos/asf?p=metron.git you see that commit
a5b13777a, for METRON-877, was committed yesterday but is still not present in
github: http
Yes, it could cause problems. Not sure what to do about it. Should we open an
INFRA ticket, or does our PMC have auth to poke it?
One can browse the (real) Apache repo and see it, it hasn't been pushed from
there.
--Matt
On Mon, Jul 3, 2017 at 4:16 AM -0700, "Otto Fowler"
mailto:ottobackwa.
YAF data [PASS]
>> > * Management UI and REST Swagger UI sanity check [PASS]
>> >
>> >
>> > -Anand
>> >
>> >
>> >
>> >
>> >
>> > On 6
d signature!
gpg: There is no indication that the signature belongs to the
owner.
Primary key fingerprint: 7854 36A7 8258 6B71 829C 67A0 4169 AA27 ECB3 1663
On June 27, 2017 at 14:36:07, Matt Foley (ma...@apache.org) wrote:
This is a call to vote on r
Sorry, small typo in “Other release files..found here” link, corrected below.
On 6/27/17, 11:36 AM, "Matt Foley" 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
anot
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/
> > On Mon, Jun 26, 2017 at 9:50 PM, Matt Foley wrote:
> >
> > The Release Process document at https://cwiki.apache.org/
> > confluence/display/METRON/Release+Process
> > currently states that a file named DISCLAIMER is a required artifa
The Release Process document at
https://cwiki.apache.org/confluence/display/METRON/Release+Process
currently states that a file named DISCLAIMER is a required artifact in the
release package. The contents of this file are:
===
Apache Metron is an effort undergoing incubation at The Apache Softwa
,
METRON-701, METRON-503, METRON-503, METRON-503, METRON-743, METRON-646,
METRON-686, METRON-742, METRON-741, METRON-740, METRON-728, METRON-733,
METRON-690)
On 6/26/17, 10:17 AM, "Matt Foley" wrote:
Hi all,
I am proceeding with building the 0.4.0 release candidate, from curren
unit tests.
Thanks much,
--Matt
On 6/2/17, 11:36 AM, "Matt Foley" wrote:
Hi Christian,
I agree this would be nice to have. I also agree with @kylerichardson ‘s
review comments that the change (with field renames and outputs) is large
enough to require consistent changes in the
1 - 100 of 143 matches
Mail list logo
