subject:"\[DISCUSS\] Metron release 0.4.1"

Re: [DISCUSS] Metron release 0.4.1

2017-09-08 Thread Matt Foley

Hi Ryan, yup, got it.  It’s in.

On 9/8/17, 1:25 PM, "Ryan Merriman" <merrim...@gmail.com> 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 <ma...@apache.org> wrote:
> 
> Okay.  Please ping when committed.
> Also, any input on https://issues.apache.org/jira/browse/METRON-1163 ?
> 
> On 9/7/17, 7:39 AM, "Ryan Merriman" <merrim...@gmail.com> wrote:
> 
>Matt,
> 
>We recently found a bug that's breaking certain features in the 
management
>UI.  The fixes are still in review (
>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 <ma...@apache.org> wrote:
>> 
>> I’ve got a blocker bug, https://issues.apache.org/jira/browse/METRON-1163
>> , RAT failures for metron-interface/metron-alerts.  A comment in the jira
>> suggests a way to address it, but someone familiar with the code should
>> look at it.
>> 
>> 
>> 
>> Raghu, would you be able to take a look?
>> 
>> 
>> 
>> Thanks,
>> 
>> --Matt
>> 
>> 
>> 
>> From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley <
>> ma...@apache.org>
>> Date: Tuesday, September 5, 2017 at 10:01 AM
>> To: "dev@metron.apache.org" <dev@metron.apache.org>
>> Subject: Re: [DISCUSS] Metron release 0.4.1
>> 
>> 
>> 
>> Great, working on it!
>> 
>> 
>> 
>> From: Nick Allen <n...@nickallen.org>
>> Date: Tuesday, September 5, 2017 at 8:00 AM
>> To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <
>> zeo...@gmail.com>
>> Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley <
>> mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>
>> Subject: Re: [DISCUSS] Metron release 0.4.1
>> 
>> 
>> 
>> All set here.  Let's get this shipped!
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> wrote:
>> 
>> me too
>> 
>> 
>> 
>> On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com <zeo...@gmail.com>
>> wrote:
>> 
>> All set from my perspective.
>> 
>> 
>> 
>> Jon
>> 
>> 
>> 
>> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
>> asubraman...@hortonworks.com> wrote:
>> 
>> Hello Matt,
>> 
>> Simon's pull request supersedes mine (METRON-1139 /
>> https://github.com/apache/metron/pull/722) and is already merged into
>> master.
>> 
>> Thanks,
>> Anand
>> 
>> 
>> 
>>> On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:
>>> 
>>> Please mark them 0.4.1, as that’s what the community says we want to 
call
>> the upcoming release, and everything that’s there when I throw the switch
>> will be included.
>>> 
>>> Jon and Anand, will they be in by end/day Friday?
>>> Thanks,
>>> --Matt
>>> 
>>> On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
>>> 
>>>   Matt, et al - For JIRAs that are going into master, should we be
>> marking
>>>   these as "Next + 1" or "0.4.1" ?
>>> 
>>>>   On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com <zeo...@gmail.com>
>>> wrote:
>>> 
>>>> Can I advocate to get METRON-1129 in the RC, and throw in a second
>> vote for
>>>> METRON-1134?  Both in an attempt to better support of prod/offline
>> use.
>>>> Happy to provide testing cycles for the former.
>>>> 
>>>> Jon
>>>> 
>>>> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
>>>> asubraman...@hortonworks.com&g

Re: [DISCUSS] Metron release 0.4.1

2017-09-08 Thread Ryan Merriman

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 <ma...@apache.org> wrote:
> 
> Okay.  Please ping when committed.
> Also, any input on https://issues.apache.org/jira/browse/METRON-1163 ?
> 
> On 9/7/17, 7:39 AM, "Ryan Merriman" <merrim...@gmail.com> wrote:
> 
>Matt,
> 
>We recently found a bug that's breaking certain features in the management
>UI.  The fixes are still in review (
>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 <ma...@apache.org> wrote:
>> 
>> I’ve got a blocker bug, https://issues.apache.org/jira/browse/METRON-1163
>> , RAT failures for metron-interface/metron-alerts.  A comment in the jira
>> suggests a way to address it, but someone familiar with the code should
>> look at it.
>> 
>> 
>> 
>> Raghu, would you be able to take a look?
>> 
>> 
>> 
>> Thanks,
>> 
>> --Matt
>> 
>> 
>> 
>> From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley <
>> ma...@apache.org>
>> Date: Tuesday, September 5, 2017 at 10:01 AM
>> To: "dev@metron.apache.org" <dev@metron.apache.org>
>> Subject: Re: [DISCUSS] Metron release 0.4.1
>> 
>> 
>> 
>> Great, working on it!
>> 
>> 
>> 
>> From: Nick Allen <n...@nickallen.org>
>> Date: Tuesday, September 5, 2017 at 8:00 AM
>> To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <
>> zeo...@gmail.com>
>> Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley <
>> mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>
>> Subject: Re: [DISCUSS] Metron release 0.4.1
>> 
>> 
>> 
>> All set here.  Let's get this shipped!
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> wrote:
>> 
>> me too
>> 
>> 
>> 
>> On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com <zeo...@gmail.com>
>> wrote:
>> 
>> All set from my perspective.
>> 
>> 
>> 
>> Jon
>> 
>> 
>> 
>> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
>> asubraman...@hortonworks.com> wrote:
>> 
>> Hello Matt,
>> 
>> Simon's pull request supersedes mine (METRON-1139 /
>> https://github.com/apache/metron/pull/722) and is already merged into
>> master.
>> 
>> Thanks,
>> Anand
>> 
>> 
>> 
>>> On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:
>>> 
>>> Please mark them 0.4.1, as that’s what the community says we want to call
>> the upcoming release, and everything that’s there when I throw the switch
>> will be included.
>>> 
>>> Jon and Anand, will they be in by end/day Friday?
>>> Thanks,
>>> --Matt
>>> 
>>> On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
>>> 
>>>   Matt, et al - For JIRAs that are going into master, should we be
>> marking
>>>   these as "Next + 1" or "0.4.1" ?
>>> 
>>>>   On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com <zeo...@gmail.com>
>>> wrote:
>>> 
>>>> Can I advocate to get METRON-1129 in the RC, and throw in a second
>> vote for
>>>> METRON-1134?  Both in an attempt to better support of prod/offline
>> use.
>>>> Happy to provide testing cycles for the former.
>>>> 
>>>> Jon
>>>> 
>>>> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
>>>> asubraman...@hortonworks.com> wrote:
>>>> 
>>>>> Hi Matt,
>>>>> 
>>>>> This defect needs to be included as a follow-on to METRON-1122:
>>>>> * METRON-1141 (https://github.com/apache/metron/pull/723)
>>>>> 
>>>>> 
>>>>> Thanks,
>>>>> Anand
>>>>> 
>>>>> 
>>>>> 
>>>>> On 8/30/17, 8:57 PM, "Michael Miklavcic" <
>> michael.miklav...@gmail.com>
>>>>> wrote:
>>>>> 
>>>>>> I have some work around fixing how we handle config

Re: [DISCUSS] Metron release 0.4.1

2017-09-08 Thread Matt Foley

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" <ma...@apache.org> wrote:

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" <mfo...@hortonworks.com on behalf of 
ma...@apache.org> wrote:

Okay.  Please ping when committed.
Also, any input on https://issues.apache.org/jira/browse/METRON-1163 ?

On 9/7/17, 7:39 AM, "Ryan Merriman" <merrim...@gmail.com> wrote:

Matt,

We recently found a bug that's breaking certain features in the 
management
UI.  The fixes are still in review (
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 <ma...@apache.org> 
wrote:

> I’ve got a blocker bug, 
https://issues.apache.org/jira/browse/METRON-1163
> , RAT failures for metron-interface/metron-alerts.  A comment in 
the jira
> suggests a way to address it, but someone familiar with the code 
should
> look at it.
>
>
>
> Raghu, would you be able to take a look?
>
>
>
> Thanks,
>
> --Matt
>
>
>
> From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley 
<
> ma...@apache.org>
> Date: Tuesday, September 5, 2017 at 10:01 AM
> To: "dev@metron.apache.org" <dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> Great, working on it!
>
>
>
> From: Nick Allen <n...@nickallen.org>
> Date: Tuesday, September 5, 2017 at 8:00 AM
> To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <
> zeo...@gmail.com>
        > Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley <
> mfo...@hortonworks.com>, "dev@metron.apache.org" 
<dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> All set here.  Let's get this shipped!
>
>
>
>
>
>
>
> On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> 
wrote:
>
> me too
>
>
>
> On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com 
<zeo...@gmail.com>
> wrote:
>
> All set from my perspective.
>
>
>
> Jon
>
>
>
> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
> Hello Matt,
>
> Simon's pull request supersedes mine (METRON-1139 /
> https://github.com/apache/metron/pull/722) and is already merged 
into
> master.
>
> Thanks,
> Anand
>
>
>
> On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:
>
> >Please mark them 0.4.1, as that’s what the community says we 
want to call
> the upcoming release, and everything that’s there when I throw 
the switch
> will be included.
> >
> >Jon and Anand, will they be in by end/day Friday?
> >Thanks,
> >--Matt
> >
> >On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
> >
> >Matt, et al - For JIRAs that are going into master, should 
we be
> marking
> >these as "Next + 1" or "0.4.1" ?
> >
> >On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com 
<zeo...@gm

Re: [DISCUSS] Metron release 0.4.1

2017-09-08 Thread Matt Foley

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" <mfo...@hortonworks.com on behalf of 
ma...@apache.org> wrote:

Okay.  Please ping when committed.
Also, any input on https://issues.apache.org/jira/browse/METRON-1163 ?

On 9/7/17, 7:39 AM, "Ryan Merriman" <merrim...@gmail.com> wrote:

Matt,

We recently found a bug that's breaking certain features in the 
management
UI.  The fixes are still in review (
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 <ma...@apache.org> wrote:

> I’ve got a blocker bug, 
https://issues.apache.org/jira/browse/METRON-1163
> , RAT failures for metron-interface/metron-alerts.  A comment in the 
jira
> suggests a way to address it, but someone familiar with the code 
should
> look at it.
>
>
>
> Raghu, would you be able to take a look?
>
>
>
> Thanks,
>
> --Matt
>
>
>
> From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley <
> ma...@apache.org>
> Date: Tuesday, September 5, 2017 at 10:01 AM
    > To: "dev@metron.apache.org" <dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> Great, working on it!
>
>
>
> From: Nick Allen <n...@nickallen.org>
> Date: Tuesday, September 5, 2017 at 8:00 AM
> To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <
> zeo...@gmail.com>
    > Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley <
> mfo...@hortonworks.com>, "dev@metron.apache.org" 
<dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> All set here.  Let's get this shipped!
>
>
>
>
>
>
>
> On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> 
wrote:
>
> me too
>
>
>
> On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com <zeo...@gmail.com>
> wrote:
>
> All set from my perspective.
>
>
>
> Jon
>
>
>
> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
> Hello Matt,
>
> Simon's pull request supersedes mine (METRON-1139 /
> https://github.com/apache/metron/pull/722) and is already merged into
> master.
>
> Thanks,
> Anand
>
>
>
> On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:
>
> >Please mark them 0.4.1, as that’s what the community says we want to 
call
> the upcoming release, and everything that’s there when I throw the 
switch
> will be included.
> >
> >Jon and Anand, will they be in by end/day Friday?
> >Thanks,
> >--Matt
> >
> >On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
> >
> >Matt, et al - For JIRAs that are going into master, should we be
> marking
> >these as "Next + 1" or "0.4.1" ?
> >
> >On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com 
<zeo...@gmail.com>
> wrote:
> >
> >> Can I advocate to get METRON-1129 in the RC, and throw in a 
second
> vote for
> >> METRON-1134?  Both in an attempt to better support of 
prod/offline
> use.
> >> Happy to provide testing cycles for the former.
> >>
> >> Jon
> >>
> >> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> >> asubraman...@hortonworks.com> wrote:
> >>
> >> > Hi Matt,
> >> &g

Re: [DISCUSS] Metron release 0.4.1

2017-09-07 Thread Matt Foley

Okay.  Please ping when committed.
Also, any input on https://issues.apache.org/jira/browse/METRON-1163 ?

On 9/7/17, 7:39 AM, "Ryan Merriman" <merrim...@gmail.com> wrote:

Matt,

We recently found a bug that's breaking certain features in the management
UI.  The fixes are still in review (
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 <ma...@apache.org> wrote:

> I’ve got a blocker bug, https://issues.apache.org/jira/browse/METRON-1163
> , RAT failures for metron-interface/metron-alerts.  A comment in the jira
> suggests a way to address it, but someone familiar with the code should
> look at it.
>
>
>
> Raghu, would you be able to take a look?
>
>
>
> Thanks,
>
> --Matt
>
>
>
> From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley <
> ma...@apache.org>
> Date: Tuesday, September 5, 2017 at 10:01 AM
> To: "dev@metron.apache.org" <dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> Great, working on it!
>
>
>
> From: Nick Allen <n...@nickallen.org>
> Date: Tuesday, September 5, 2017 at 8:00 AM
> To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <
> zeo...@gmail.com>
    > Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley <
> mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> All set here.  Let's get this shipped!
>
>
>
>
>
>
>
> On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> wrote:
>
> me too
>
>
>
> On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com <zeo...@gmail.com>
> wrote:
>
> All set from my perspective.
>
>
>
> Jon
>
>
>
> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
> Hello Matt,
>
> Simon's pull request supersedes mine (METRON-1139 /
> https://github.com/apache/metron/pull/722) and is already merged into
> master.
>
> Thanks,
> Anand
>
>
>
> On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:
>
> >Please mark them 0.4.1, as that’s what the community says we want to call
> the upcoming release, and everything that’s there when I throw the switch
> will be included.
> >
> >Jon and Anand, will they be in by end/day Friday?
> >Thanks,
> >--Matt
> >
> >On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
> >
> >Matt, et al - For JIRAs that are going into master, should we be
> marking
> >these as "Next + 1" or "0.4.1" ?
> >
> >On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com <zeo...@gmail.com>
> wrote:
> >
> >> Can I advocate to get METRON-1129 in the RC, and throw in a second
> vote for
> >> METRON-1134?  Both in an attempt to better support of prod/offline
> use.
> >> Happy to provide testing cycles for the former.
> >>
> >> Jon
> >>
> >> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> >> asubraman...@hortonworks.com> wrote:
> >>
> >> > Hi Matt,
> >> >
> >> > This defect needs to be included as a follow-on to METRON-1122:
> >> > * METRON-1141 (https://github.com/apache/metron/pull/723)
> >> >
> >> >
> >> > Thanks,
> >> > Anand
> >> >
> >> >
> >> >
> >> > On 8/30/17, 8:57 PM, "Michael Miklavcic" <
> michael.miklav...@gmail.com>
> >> > wrote:
> >> >
> >> > >I have some work around fixing how we handle config with Ambari
> that I'd
> >> > >like to see go in. No PR yet, but coming soon. I exp

Re: [DISCUSS] Metron release 0.4.1

2017-09-07 Thread Ryan Merriman

Matt,

We recently found a bug that's breaking certain features in the management
UI.  The fixes are still in review (
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 <ma...@apache.org> wrote:

> I’ve got a blocker bug, https://issues.apache.org/jira/browse/METRON-1163
> , RAT failures for metron-interface/metron-alerts.  A comment in the jira
> suggests a way to address it, but someone familiar with the code should
> look at it.
>
>
>
> Raghu, would you be able to take a look?
>
>
>
> Thanks,
>
> --Matt
>
>
>
> From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley <
> ma...@apache.org>
> Date: Tuesday, September 5, 2017 at 10:01 AM
> To: "dev@metron.apache.org" <dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> Great, working on it!
>
>
>
> From: Nick Allen <n...@nickallen.org>
> Date: Tuesday, September 5, 2017 at 8:00 AM
> To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <
> zeo...@gmail.com>
> Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley <
> mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> All set here.  Let's get this shipped!
>
>
>
>
>
>
>
> On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> wrote:
>
> me too
>
>
>
> On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com <zeo...@gmail.com>
> wrote:
>
> All set from my perspective.
>
>
>
> Jon
>
>
>
> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
> Hello Matt,
>
> Simon's pull request supersedes mine (METRON-1139 /
> https://github.com/apache/metron/pull/722) and is already merged into
> master.
>
> Thanks,
> Anand
>
>
>
> On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:
>
> >Please mark them 0.4.1, as that’s what the community says we want to call
> the upcoming release, and everything that’s there when I throw the switch
> will be included.
> >
> >Jon and Anand, will they be in by end/day Friday?
> >Thanks,
> >--Matt
> >
> >On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
> >
> >Matt, et al - For JIRAs that are going into master, should we be
> marking
> >these as "Next + 1" or "0.4.1" ?
> >
> >On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com <zeo...@gmail.com>
> wrote:
> >
> >> Can I advocate to get METRON-1129 in the RC, and throw in a second
> vote for
> >> METRON-1134?  Both in an attempt to better support of prod/offline
> use.
> >> Happy to provide testing cycles for the former.
> >>
> >> Jon
> >>
> >> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> >> asubraman...@hortonworks.com> wrote:
> >>
> >> > Hi Matt,
> >> >
> >> > This defect needs to be included as a follow-on to METRON-1122:
> >> > * METRON-1141 (https://github.com/apache/metron/pull/723)
> >> >
> >> >
> >> > Thanks,
> >> > Anand
> >> >
> >> >
> >> >
> >> > On 8/30/17, 8:57 PM, "Michael Miklavcic" <
> michael.miklav...@gmail.com>
> >> > wrote:
> >> >
> >> > >I have some work around fixing how we handle config with Ambari
> that I'd
> >> > >like to see go in. No PR yet, but coming soon. I expect to have
> this by
> >> > the
> >> > >RC deadline.
> >> > >
> >> > >Mike
> >> > >
> >> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen <n...@nickallen.org>
> wrote:
> >> > >
> >> > >> The following PRs are usability enhancements for the
> Profiler.  They
> >> are
> >> > >> fairly simple 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.
> >> > >>
> &g

Re: [DISCUSS] Metron release 0.4.1

2017-09-06 Thread Matt Foley

I’ve got a blocker bug, https://issues.apache.org/jira/browse/METRON-1163 , RAT 
failures for metron-interface/metron-alerts.  A comment in the jira suggests a 
way to address it, but someone familiar with the code should look at it. 

 

Raghu, would you be able to take a look?

 

Thanks,

--Matt

 

From: Matt Foley <mfo...@hortonworks.com> on behalf of Matt Foley 
<ma...@apache.org>
Date: Tuesday, September 5, 2017 at 10:01 AM
To: "dev@metron.apache.org" <dev@metron.apache.org>
Subject: Re: [DISCUSS] Metron release 0.4.1

 

Great, working on it!

 

From: Nick Allen <n...@nickallen.org>
Date: Tuesday, September 5, 2017 at 8:00 AM
To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <zeo...@gmail.com>
Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley 
<mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>
Subject: Re: [DISCUSS] Metron release 0.4.1

 

All set here.  Let's get this shipped! 

 

 

 

On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> wrote:

me too

 

On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com <zeo...@gmail.com> wrote:

All set from my perspective. 

 

Jon

 

On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <asubraman...@hortonworks.com> 
wrote:

Hello Matt,

Simon's pull request supersedes mine (METRON-1139 / 
https://github.com/apache/metron/pull/722) and is already merged into master.

Thanks,
Anand



On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:

>Please mark them 0.4.1, as that’s what the community says we want to call the 
>upcoming release, and everything that’s there when I throw the switch will be 
>included.
>
>Jon and Anand, will they be in by end/day Friday?
>Thanks,
>--Matt
>
>On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
>
>Matt, et al - For JIRAs that are going into master, should we be marking
>these as "Next + 1" or "0.4.1" ?
>
>On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com <zeo...@gmail.com> wrote:
>
>> Can I advocate to get METRON-1129 in the RC, and throw in a second vote 
> for
>> METRON-1134?  Both in an attempt to better support of prod/offline use.
>> Happy to provide testing cycles for the former.
>>
>> Jon
>>
>> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
>> asubraman...@hortonworks.com> wrote:
>>
>> > Hi Matt,
>> >
>> > This defect needs to be included as a follow-on to METRON-1122:
>> > * METRON-1141 (https://github.com/apache/metron/pull/723)
>> >
>> >
>> > Thanks,
>> > Anand
>> >
>> >
>> >
>> > On 8/30/17, 8:57 PM, "Michael Miklavcic" <michael.miklav...@gmail.com>
>> > wrote:
>> >
>> > >I have some work around fixing how we handle config with Ambari that 
> I'd
>> > >like to see go in. No PR yet, but coming soon. I expect to have this 
> by
>> > the
>> > >RC deadline.
>> > >
>> > >Mike
>> > >
>> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen <n...@nickallen.org> 
> wrote:
>> > >
>> > >> The following PRs are usability enhancements for the Profiler.  They
>> are
>> > >> fairly simple 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, I would appreciate some reviews of these PRs.
>> > >> https://github.com/apache/metron/pull/721
>> > >> https://github.com/apache/metron/pull/716
>> > >>
>> > >>
>> > >>
>> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley <ma...@apache.org> wrote:
>> > >>
>> > >> > Okay, just to be clear, you’re requesting we wait until Friday, if
>> > >> > necessary, to cut an RC with 717 in it?
>> > >> > Thanks,
>> > >> > --Matt
>> > >> >
>> > >> > On 8/29/17, 11:45 AM, "Casey Stella" <ceste...@gmail.com> wrote:
>> > >> >
>> > >> > 709 is in and 717 is under concerted review by Otto.  I'd like
>> to
>> > see
>

Re: [DISCUSS] Metron release 0.4.1

2017-09-06 Thread Nick Allen

We won't be able to perform an AWS deployment without this PR.  In the
past, we have used the AWS deployment as RC validation criteria, so I
thought I would mention it.

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



On Tue, Sep 5, 2017 at 1:01 PM Matt Foley <ma...@apache.org> wrote:

> Great, working on it!
>
>
>
> From: Nick Allen <n...@nickallen.org>
> Date: Tuesday, September 5, 2017 at 8:00 AM
> To: Casey Stella <ceste...@gmail.com>, "zeo...@gmail.com" <
> zeo...@gmail.com>
> Cc: Anand Subramanian <asubraman...@hortonworks.com>, Matt Foley <
> mfo...@hortonworks.com>, "dev@metron.apache.org" <dev@metron.apache.org>
> Subject: Re: [DISCUSS] Metron release 0.4.1
>
>
>
> All set here.  Let's get this shipped!
>
>
>
>
>
>
>
> On Tue, Sep 5, 2017 at 10:44 AM Casey Stella <ceste...@gmail.com> wrote:
>
> me too
>
>
>
> On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com <zeo...@gmail.com>
> wrote:
>
> All set from my perspective.
>
>
>
> Jon
>
>
>
> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
> Hello Matt,
>
> Simon's pull request supersedes mine (METRON-1139 /
> https://github.com/apache/metron/pull/722) and is already merged into
> master.
>
> Thanks,
> Anand
>
>
>
> On 9/1/17, 12:41 AM, "Matt Foley" <mfo...@hortonworks.com> wrote:
>
> >Please mark them 0.4.1, as that’s what the community says we want to call
> the upcoming release, and everything that’s there when I throw the switch
> will be included.
> >
> >Jon and Anand, will they be in by end/day Friday?
> >Thanks,
> >--Matt
> >
> >On 8/31/17, 7:45 AM, "Nick Allen" <n...@nickallen.org> wrote:
> >
> >Matt, et al - For JIRAs that are going into master, should we be
> marking
> >these as "Next + 1" or "0.4.1" ?
> >
> >On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com <zeo...@gmail.com>
> wrote:
> >
> >> Can I advocate to get METRON-1129 in the RC, and throw in a second
> vote for
> >> METRON-1134?  Both in an attempt to better support of prod/offline
> use.
> >> Happy to provide testing cycles for the former.
> >>
> >> Jon
> >>
> >> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> >> asubraman...@hortonworks.com> wrote:
> >>
> >> > Hi Matt,
> >> >
> >> > This defect needs to be included as a follow-on to METRON-1122:
> >> > * METRON-1141 (https://github.com/apache/metron/pull/723)
> >> >
> >> >
> >> > Thanks,
> >> > Anand
> >> >
> >> >
> >> >
> >> > On 8/30/17, 8:57 PM, "Michael Miklavcic" <
> michael.miklav...@gmail.com>
> >> > wrote:
> >> >
> >> > >I have some work around fixing how we handle config with Ambari
> that I'd
> >> > >like to see go in. No PR yet, but coming soon. I expect to have
> this by
> >> > the
> >> > >RC deadline.
> >> > >
> >> > >Mike
> >> > >
> >> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen <n...@nickallen.org>
> wrote:
> >> > >
> >> > >> The following PRs are usability enhancements for the
> Profiler.  They
> >> are
> >> > >> fairly simple 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, I would appreciate some reviews of these
> PRs.
> >> > >> https://github.com/apache/metron/pull/721
> >> > >> https://github.com/apache/metron/pull/716
> >> > >>
> >> > >>
> >> > >>
> >> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley <ma...@apache.org>
> wrote:
> >> > >>
> >> > >> > Okay, just to be clear, you’re requesting we wait until
> Friday, if
> >> > >> > necessary, to cut an RC with 717 in it?
> >> > >> > Thanks,
> >> > >> >

Re: [DISCUSS] Metron release 0.4.1

2017-09-05 Thread Casey Stella

me too

On Tue, Sep 5, 2017 at 10:43 AM, zeo...@gmail.com  wrote:

> All set from my perspective.
>
> Jon
>
> On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
>> Hello Matt,
>>
>> Simon's pull request supersedes mine (METRON-1139 /
>> https://github.com/apache/metron/pull/722) and is already merged into
>> master.
>>
>> Thanks,
>> Anand
>>
>>
>>
>> On 9/1/17, 12:41 AM, "Matt Foley"  wrote:
>>
>> >Please mark them 0.4.1, as that’s what the community says we want to
>> call the upcoming release, and everything that’s there when I throw the
>> switch will be included.
>> >
>> >Jon and Anand, will they be in by end/day Friday?
>> >Thanks,
>> >--Matt
>> >
>> >On 8/31/17, 7:45 AM, "Nick Allen"  wrote:
>> >
>> >Matt, et al - For JIRAs that are going into master, should we be
>> marking
>> >these as "Next + 1" or "0.4.1" ?
>> >
>> >On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com 
>> wrote:
>> >
>> >> Can I advocate to get METRON-1129 in the RC, and throw in a second
>> vote for
>> >> METRON-1134?  Both in an attempt to better support of prod/offline
>> use.
>> >> Happy to provide testing cycles for the former.
>> >>
>> >> Jon
>> >>
>> >> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
>> >> asubraman...@hortonworks.com> wrote:
>> >>
>> >> > Hi Matt,
>> >> >
>> >> > This defect needs to be included as a follow-on to METRON-1122:
>> >> > * METRON-1141 (https://github.com/apache/metron/pull/723)
>> >> >
>> >> >
>> >> > Thanks,
>> >> > Anand
>> >> >
>> >> >
>> >> >
>> >> > On 8/30/17, 8:57 PM, "Michael Miklavcic" <
>> michael.miklav...@gmail.com>
>> >> > wrote:
>> >> >
>> >> > >I have some work around fixing how we handle config with Ambari
>> that I'd
>> >> > >like to see go in. No PR yet, but coming soon. I expect to have
>> this by
>> >> > the
>> >> > >RC deadline.
>> >> > >
>> >> > >Mike
>> >> > >
>> >> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen 
>> wrote:
>> >> > >
>> >> > >> The following PRs are usability enhancements for the
>> Profiler.  They
>> >> are
>> >> > >> fairly simple 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, I would appreciate some reviews of
>> these PRs.
>> >> > >> https://github.com/apache/metron/pull/721
>> >> > >> https://github.com/apache/metron/pull/716
>> >> > >>
>> >> > >>
>> >> > >>
>> >> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley 
>> wrote:
>> >> > >>
>> >> > >> > Okay, just to be clear, you’re requesting we wait until
>> Friday, if
>> >> > >> > necessary, to cut an RC with 717 in it?
>> >> > >> > Thanks,
>> >> > >> > --Matt
>> >> > >> >
>> >> > >> > On 8/29/17, 11:45 AM, "Casey Stella" 
>> wrote:
>> >> > >> >
>> >> > >> > 709 is in and 717 is under concerted review by Otto.
>> I'd like
>> >> to
>> >> > see
>> >> > >> > it in
>> >> > >> > by Friday.
>> >> > >> >
>> >> > >> > On Tue, Aug 29, 2017 at 1:35 PM, Matt Foley <
>> ma...@apache.org>
>> >> > >> 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 8/29/17, 9:34 AM, "Casey Stella" <
>> ceste...@gmail.com>
>> >> wrote:
>> >> > >> > >
>> >> > >> > > For my PRs, I'd vote for METRON-1122 being in
>> (commit very
>> >> > >> > imminent).
>> >> > >> > > I'd very much like METRON-1134 to be in as well.
>> >> > >> > >
>> >> > >> > > Beyond that, I'm ok
>> >> > >> > >
>> >> > >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
>> >> > >> n...@nickallen.org>
>> >> > >> > > wrote:
>> >> > >> > >
>> >> > >> > > > Thanks for starting the process, Matt.
>> >> > >> > > >
>> >> > >> > > > These are my own open PRs that I would most
>> like to see
>> >> > get
>> >> > >> in.
>> >> > >> > > They 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
>> >> > >> >

Re: [DISCUSS] Metron release 0.4.1

2017-09-05 Thread zeo...@gmail.com

All set from my perspective.

Jon

On Sat, Sep 2, 2017 at 4:38 AM Anand Subramanian <
asubraman...@hortonworks.com> wrote:

> Hello Matt,
>
> Simon's pull request supersedes mine (METRON-1139 /
> https://github.com/apache/metron/pull/722) and is already merged into
> master.
>
> Thanks,
> Anand
>
>
>
> On 9/1/17, 12:41 AM, "Matt Foley"  wrote:
>
> >Please mark them 0.4.1, as that’s what the community says we want to call
> the upcoming release, and everything that’s there when I throw the switch
> will be included.
> >
> >Jon and Anand, will they be in by end/day Friday?
> >Thanks,
> >--Matt
> >
> >On 8/31/17, 7:45 AM, "Nick Allen"  wrote:
> >
> >Matt, et al - For JIRAs that are going into master, should we be
> marking
> >these as "Next + 1" or "0.4.1" ?
> >
> >On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com 
> wrote:
> >
> >> Can I advocate to get METRON-1129 in the RC, and throw in a second
> vote for
> >> METRON-1134?  Both in an attempt to better support of prod/offline
> use.
> >> Happy to provide testing cycles for the former.
> >>
> >> Jon
> >>
> >> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> >> asubraman...@hortonworks.com> wrote:
> >>
> >> > Hi Matt,
> >> >
> >> > This defect needs to be included as a follow-on to METRON-1122:
> >> > * METRON-1141 (https://github.com/apache/metron/pull/723)
> >> >
> >> >
> >> > Thanks,
> >> > Anand
> >> >
> >> >
> >> >
> >> > On 8/30/17, 8:57 PM, "Michael Miklavcic" <
> michael.miklav...@gmail.com>
> >> > wrote:
> >> >
> >> > >I have some work around fixing how we handle config with Ambari
> that I'd
> >> > >like to see go in. No PR yet, but coming soon. I expect to have
> this by
> >> > the
> >> > >RC deadline.
> >> > >
> >> > >Mike
> >> > >
> >> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen 
> wrote:
> >> > >
> >> > >> The following PRs are usability enhancements for the
> Profiler.  They
> >> are
> >> > >> fairly simple 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, I would appreciate some reviews of these
> PRs.
> >> > >> https://github.com/apache/metron/pull/721
> >> > >> https://github.com/apache/metron/pull/716
> >> > >>
> >> > >>
> >> > >>
> >> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley 
> wrote:
> >> > >>
> >> > >> > Okay, just to be clear, you’re requesting we wait until
> Friday, if
> >> > >> > necessary, to cut an RC with 717 in it?
> >> > >> > Thanks,
> >> > >> > --Matt
> >> > >> >
> >> > >> > On 8/29/17, 11:45 AM, "Casey Stella" 
> wrote:
> >> > >> >
> >> > >> > 709 is in and 717 is under concerted review by Otto.
> I'd like
> >> to
> >> > see
> >> > >> > it in
> >> > >> > by Friday.
> >> > >> >
> >> > >> > On Tue, Aug 29, 2017 at 1:35 PM, Matt Foley <
> ma...@apache.org>
> >> > >> 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 8/29/17, 9:34 AM, "Casey Stella" <
> ceste...@gmail.com>
> >> wrote:
> >> > >> > >
> >> > >> > > For my PRs, I'd vote for METRON-1122 being in
> (commit very
> >> > >> > imminent).
> >> > >> > > I'd very much like METRON-1134 to be in as well.
> >> > >> > >
> >> > >> > > Beyond that, I'm ok
> >> > >> > >
> >> > >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
> >> > >> n...@nickallen.org>
> >> > >> > > wrote:
> >> > >> > >
> >> > >> > > > Thanks for starting the process, Matt.
> >> > >> > > >
> >> > >> > > > These are my own open PRs that I would most like
> to see
> >> > get
> >> > >> in.
> >> > >> > > They 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
> >> > >> > > >
> >> > >> > > >
> >> > >> > > >
> >> > >> > > >
> >> > >> > > >
> >> > >> > > > On Tue, Aug 22, 2017

Re: [DISCUSS] Metron release 0.4.1

2017-09-02 Thread Anand Subramanian

Hello Matt,

Simon's pull request supersedes mine (METRON-1139 / 
https://github.com/apache/metron/pull/722) and is already merged into master. 

Thanks,
Anand



On 9/1/17, 12:41 AM, "Matt Foley"  wrote:

>Please mark them 0.4.1, as that’s what the community says we want to call the 
>upcoming release, and everything that’s there when I throw the switch will be 
>included.
>
>Jon and Anand, will they be in by end/day Friday?
>Thanks,
>--Matt
>
>On 8/31/17, 7:45 AM, "Nick Allen"  wrote:
>
>Matt, et al - For JIRAs that are going into master, should we be marking
>these as "Next + 1" or "0.4.1" ?
>
>On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com  wrote:
>
>> Can I advocate to get METRON-1129 in the RC, and throw in a second vote 
> for
>> METRON-1134?  Both in an attempt to better support of prod/offline use.
>> Happy to provide testing cycles for the former.
>>
>> Jon
>>
>> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
>> asubraman...@hortonworks.com> wrote:
>>
>> > Hi Matt,
>> >
>> > This defect needs to be included as a follow-on to METRON-1122:
>> > * METRON-1141 (https://github.com/apache/metron/pull/723)
>> >
>> >
>> > Thanks,
>> > Anand
>> >
>> >
>> >
>> > On 8/30/17, 8:57 PM, "Michael Miklavcic" 
>> > wrote:
>> >
>> > >I have some work around fixing how we handle config with Ambari that 
> I'd
>> > >like to see go in. No PR yet, but coming soon. I expect to have this 
> by
>> > the
>> > >RC deadline.
>> > >
>> > >Mike
>> > >
>> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen  
> wrote:
>> > >
>> > >> The following PRs are usability enhancements for the Profiler.  They
>> are
>> > >> fairly simple 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, I would appreciate some reviews of these PRs.
>> > >> https://github.com/apache/metron/pull/721
>> > >> https://github.com/apache/metron/pull/716
>> > >>
>> > >>
>> > >>
>> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley  wrote:
>> > >>
>> > >> > Okay, just to be clear, you’re requesting we wait until Friday, if
>> > >> > necessary, to cut an RC with 717 in it?
>> > >> > Thanks,
>> > >> > --Matt
>> > >> >
>> > >> > On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
>> > >> >
>> > >> > 709 is in and 717 is under concerted review by Otto.  I'd like
>> to
>> > see
>> > >> > it in
>> > >> > by Friday.
>> > >> >
>> > >> > On Tue, 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 8/29/17, 9:34 AM, "Casey Stella" 
>> wrote:
>> > >> > >
>> > >> > > For my PRs, I'd vote for METRON-1122 being in (commit 
> very
>> > >> > imminent).
>> > >> > > I'd very much like METRON-1134 to be in as well.
>> > >> > >
>> > >> > > Beyond that, I'm ok
>> > >> > >
>> > >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
>> > >> n...@nickallen.org>
>> > >> > > wrote:
>> > >> > >
>> > >> > > > Thanks for starting the process, Matt.
>> > >> > > >
>> > >> > > > These are my own open PRs that I would most like to 
> see
>> > get
>> > >> in.
>> > >> > > They 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
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > >
>> > >> > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley <
>> > ma...@apache.org
>> > >> >
>> > >> > wrote:
>> > >> > > >
>> > >> > > > > 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
>> > >> >

Re: [DISCUSS] Metron release 0.4.1

2017-09-01 Thread zeo...@gmail.com

Looks like METRON-1134 made it in already and I just gave METRON-1129
a +1.  Just waiting on Ryan's feedback to merge it in.

Jon

On Thu, Aug 31, 2017 at 3:11 PM Matt Foley  wrote:

> Please mark them 0.4.1, as that’s what the community says we want to call
> the upcoming release, and everything that’s there when I throw the switch
> will be included.
>
> Jon and Anand, will they be in by end/day Friday?
> Thanks,
> --Matt
>
> On 8/31/17, 7:45 AM, "Nick Allen"  wrote:
>
> Matt, et al - For JIRAs that are going into master, should we be
> marking
> these as "Next + 1" or "0.4.1" ?
>
> On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com 
> wrote:
>
> > Can I advocate to get METRON-1129 in the RC, and throw in a second
> vote for
> > METRON-1134?  Both in an attempt to better support of prod/offline
> use.
> > Happy to provide testing cycles for the former.
> >
> > Jon
> >
> > On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> > asubraman...@hortonworks.com> wrote:
> >
> > > Hi Matt,
> > >
> > > This defect needs to be included as a follow-on to METRON-1122:
> > > * METRON-1141 (https://github.com/apache/metron/pull/723)
> > >
> > >
> > > Thanks,
> > > Anand
> > >
> > >
> > >
> > > On 8/30/17, 8:57 PM, "Michael Miklavcic" <
> michael.miklav...@gmail.com>
> > > wrote:
> > >
> > > >I have some work around fixing how we handle config with Ambari
> that I'd
> > > >like to see go in. No PR yet, but coming soon. I expect to have
> this by
> > > the
> > > >RC deadline.
> > > >
> > > >Mike
> > > >
> > > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen 
> wrote:
> > > >
> > > >> The following PRs are usability enhancements for the Profiler.
> They
> > are
> > > >> fairly simple 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, I would appreciate some reviews of these
> PRs.
> > > >> https://github.com/apache/metron/pull/721
> > > >> https://github.com/apache/metron/pull/716
> > > >>
> > > >>
> > > >>
> > > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley 
> wrote:
> > > >>
> > > >> > Okay, just to be clear, you’re requesting we wait until
> Friday, if
> > > >> > necessary, to cut an RC with 717 in it?
> > > >> > Thanks,
> > > >> > --Matt
> > > >> >
> > > >> > On 8/29/17, 11:45 AM, "Casey Stella" 
> wrote:
> > > >> >
> > > >> > 709 is in and 717 is under concerted review by Otto.  I'd
> like
> > to
> > > see
> > > >> > it in
> > > >> > by Friday.
> > > >> >
> > > >> > On Tue, Aug 29, 2017 at 1:35 PM, Matt Foley <
> ma...@apache.org>
> > > >> 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 8/29/17, 9:34 AM, "Casey Stella"  >
> > wrote:
> > > >> > >
> > > >> > > For my PRs, I'd vote for METRON-1122 being in
> (commit very
> > > >> > imminent).
> > > >> > > I'd very much like METRON-1134 to be in as well.
> > > >> > >
> > > >> > > Beyond that, I'm ok
> > > >> > >
> > > >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
> > > >> n...@nickallen.org>
> > > >> > > wrote:
> > > >> > >
> > > >> > > > Thanks for starting the process, Matt.
> > > >> > > >
> > > >> > > > These are my own open PRs that I would most like
> to see
> > > get
> > > >> in.
> > > >> > > They 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
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > >
> > > >> > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley <
> > > ma...@apache.org
> > > >> >
> > > >> > wrote:
> > > >> > > >
> > > >> > > > > Hello all,
> > > >> > > > > At the meeting this morning, the community
> expressed
> > the
> > > >> > wish to
> > > >> >

Re: [DISCUSS] Metron release 0.4.1

2017-08-31 Thread Matt Foley

Please mark them 0.4.1, as that’s what the community says we want to call the 
upcoming release, and everything that’s there when I throw the switch will be 
included.

Jon and Anand, will they be in by end/day Friday?
Thanks,
--Matt

On 8/31/17, 7:45 AM, "Nick Allen"  wrote:

Matt, et al - For JIRAs that are going into master, should we be marking
these as "Next + 1" or "0.4.1" ?

On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com  wrote:

> Can I advocate to get METRON-1129 in the RC, and throw in a second vote 
for
> METRON-1134?  Both in an attempt to better support of prod/offline use.
> Happy to provide testing cycles for the former.
>
> Jon
>
> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
> > Hi Matt,
> >
> > This defect needs to be included as a follow-on to METRON-1122:
> > * METRON-1141 (https://github.com/apache/metron/pull/723)
> >
> >
> > Thanks,
> > Anand
> >
> >
> >
> > On 8/30/17, 8:57 PM, "Michael Miklavcic" 
> > wrote:
> >
> > >I have some work around fixing how we handle config with Ambari that 
I'd
> > >like to see go in. No PR yet, but coming soon. I expect to have this by
> > the
> > >RC deadline.
> > >
> > >Mike
> > >
> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen  wrote:
> > >
> > >> The following PRs are usability enhancements for the Profiler.  They
> are
> > >> fairly simple 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, I would appreciate some reviews of these PRs.
> > >> https://github.com/apache/metron/pull/721
> > >> https://github.com/apache/metron/pull/716
> > >>
> > >>
> > >>
> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley  wrote:
> > >>
> > >> > Okay, just to be clear, you’re requesting we wait until Friday, if
> > >> > necessary, to cut an RC with 717 in it?
> > >> > Thanks,
> > >> > --Matt
> > >> >
> > >> > On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
> > >> >
> > >> > 709 is in and 717 is under concerted review by Otto.  I'd like
> to
> > see
> > >> > it in
> > >> > by Friday.
> > >> >
> > >> > On Tue, 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 8/29/17, 9:34 AM, "Casey Stella" 
> wrote:
> > >> > >
> > >> > > For my PRs, I'd vote for METRON-1122 being in (commit 
very
> > >> > imminent).
> > >> > > I'd very much like METRON-1134 to be in as well.
> > >> > >
> > >> > > Beyond that, I'm ok
> > >> > >
> > >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
> > >> n...@nickallen.org>
> > >> > > wrote:
> > >> > >
> > >> > > > Thanks for starting the process, Matt.
> > >> > > >
> > >> > > > These are my own open PRs that I would most like to see
> > get
> > >> in.
> > >> > > They 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
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley <
> > ma...@apache.org
> > >> >
> > >> > wrote:
> > >> > > >
> > >> > > > > 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
> > >> > > > > in in the next few

Re: [DISCUSS] Metron release 0.4.1

2017-08-31 Thread Nick Allen

Matt, et al - For JIRAs that are going into master, should we be marking
these as "Next + 1" or "0.4.1" ?

On Thu, Aug 31, 2017 at 8:17 AM zeo...@gmail.com  wrote:

> Can I advocate to get METRON-1129 in the RC, and throw in a second vote for
> METRON-1134?  Both in an attempt to better support of prod/offline use.
> Happy to provide testing cycles for the former.
>
> Jon
>
> On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
> asubraman...@hortonworks.com> wrote:
>
> > Hi Matt,
> >
> > This defect needs to be included as a follow-on to METRON-1122:
> > * METRON-1141 (https://github.com/apache/metron/pull/723)
> >
> >
> > Thanks,
> > Anand
> >
> >
> >
> > On 8/30/17, 8:57 PM, "Michael Miklavcic" 
> > wrote:
> >
> > >I have some work around fixing how we handle config with Ambari that I'd
> > >like to see go in. No PR yet, but coming soon. I expect to have this by
> > the
> > >RC deadline.
> > >
> > >Mike
> > >
> > >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen  wrote:
> > >
> > >> The following PRs are usability enhancements for the Profiler.  They
> are
> > >> fairly simple 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, I would appreciate some reviews of these PRs.
> > >> https://github.com/apache/metron/pull/721
> > >> https://github.com/apache/metron/pull/716
> > >>
> > >>
> > >>
> > >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley  wrote:
> > >>
> > >> > Okay, just to be clear, you’re requesting we wait until Friday, if
> > >> > necessary, to cut an RC with 717 in it?
> > >> > Thanks,
> > >> > --Matt
> > >> >
> > >> > On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
> > >> >
> > >> > 709 is in and 717 is under concerted review by Otto.  I'd like
> to
> > see
> > >> > it in
> > >> > by Friday.
> > >> >
> > >> > On Tue, 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 8/29/17, 9:34 AM, "Casey Stella" 
> wrote:
> > >> > >
> > >> > > For my PRs, I'd vote for METRON-1122 being in (commit very
> > >> > imminent).
> > >> > > I'd very much like METRON-1134 to be in as well.
> > >> > >
> > >> > > Beyond that, I'm ok
> > >> > >
> > >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
> > >> n...@nickallen.org>
> > >> > > wrote:
> > >> > >
> > >> > > > Thanks for starting the process, Matt.
> > >> > > >
> > >> > > > These are my own open PRs that I would most like to see
> > get
> > >> in.
> > >> > > They 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
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > >
> > >> > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley <
> > ma...@apache.org
> > >> >
> > >> > wrote:
> > >> > > >
> > >> > > > > 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
> > >> > > > > in in the next few days.
> > >> > > > >
> > >> > > > > There have been 74 commits since the 0.4.0 release
> (list
> > >> > appended
> > >> > > to end
> > >> > > > > of this message).
> > >> > > > > I have not yet done a compare to make sure all 74
> > completed
> > >> > > commits have
> > >> > > > > closed their Jiras, but I will follow up with that
> info.
> > >> > > > >
> > >> > > > > There are 35 open PRs, see
> > >> > https://github.com/apache/metron/pulls
> > >> > > ,
> > >> > > > which
> > >> > > > > is getting a little clunky.  Surely not all of them
> can
> > get
> > >> > in in
> > >> > > the
> > >> > > > next
> > >> > > > > few days, but do we want to try to close and include
> > some
> > >> of
> > >> > them?
> > >> >

Re: [DISCUSS] Metron release 0.4.1

2017-08-31 Thread zeo...@gmail.com

Can I advocate to get METRON-1129 in the RC, and throw in a second vote for
METRON-1134?  Both in an attempt to better support of prod/offline use.
Happy to provide testing cycles for the former.

Jon

On Wed, Aug 30, 2017 at 11:41 AM Anand Subramanian <
asubraman...@hortonworks.com> wrote:

> Hi Matt,
>
> This defect needs to be included as a follow-on to METRON-1122:
> * METRON-1141 (https://github.com/apache/metron/pull/723)
>
>
> Thanks,
> Anand
>
>
>
> On 8/30/17, 8:57 PM, "Michael Miklavcic" 
> wrote:
>
> >I have some work around fixing how we handle config with Ambari that I'd
> >like to see go in. No PR yet, but coming soon. I expect to have this by
> the
> >RC deadline.
> >
> >Mike
> >
> >On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen  wrote:
> >
> >> The following PRs are usability enhancements for the Profiler.  They are
> >> fairly simple 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, I would appreciate some reviews of these PRs.
> >> https://github.com/apache/metron/pull/721
> >> https://github.com/apache/metron/pull/716
> >>
> >>
> >>
> >> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley  wrote:
> >>
> >> > Okay, just to be clear, you’re requesting we wait until Friday, if
> >> > necessary, to cut an RC with 717 in it?
> >> > Thanks,
> >> > --Matt
> >> >
> >> > On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
> >> >
> >> > 709 is in and 717 is under concerted review by Otto.  I'd like to
> see
> >> > it in
> >> > by Friday.
> >> >
> >> > On Tue, 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 8/29/17, 9:34 AM, "Casey Stella"  wrote:
> >> > >
> >> > > For my PRs, I'd vote for METRON-1122 being in (commit very
> >> > imminent).
> >> > > I'd very much like METRON-1134 to be in as well.
> >> > >
> >> > > Beyond that, I'm ok
> >> > >
> >> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
> >> n...@nickallen.org>
> >> > > wrote:
> >> > >
> >> > > > Thanks for starting the process, Matt.
> >> > > >
> >> > > > These are my own open PRs that I would most like to see
> get
> >> in.
> >> > > They 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
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > >
> >> > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley <
> ma...@apache.org
> >> >
> >> > wrote:
> >> > > >
> >> > > > > 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
> >> > > > > in in the next few days.
> >> > > > >
> >> > > > > There have been 74 commits since the 0.4.0 release (list
> >> > appended
> >> > > to end
> >> > > > > of this message).
> >> > > > > I have not yet done a compare to make sure all 74
> completed
> >> > > commits have
> >> > > > > closed their Jiras, but I will follow up with that info.
> >> > > > >
> >> > > > > There are 35 open PRs, see
> >> > https://github.com/apache/metron/pulls
> >> > > ,
> >> > > > which
> >> > > > > is getting a little clunky.  Surely not all of them can
> get
> >> > in in
> >> > > the
> >> > > > next
> >> > > > > few days, but do we want to try to close and include
> some
> >> of
> >> > them?
> >> > > > >
> >> > > > > Please respond to the list with your requests to include
> >> > specific
> >> > > > > additional PRs before we cut the 0.4.1 release
> candidate.
> >> > Let’s
> >> > > keep it
> >> > > > > practical so we don’t delay more than a week or so.
> >> > > > >
> >> > > > > TIMEFRAME:  Tentatively I would like to start the
> process
> >> of
> >> > > cutting an
> >> > > > RC
> >> > > > > this coming

Re: [DISCUSS] Metron release 0.4.1

2017-08-30 Thread Michael Miklavcic

I have some work around fixing how we handle config with Ambari that I'd
like to see go in. No PR yet, but coming soon. I expect to have this by the
RC deadline.

Mike

On Wed, Aug 30, 2017 at 8:57 AM, Nick Allen  wrote:

> The following PRs are usability enhancements for the Profiler.  They are
> fairly simple 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, I would appreciate some reviews of these PRs.
> https://github.com/apache/metron/pull/721
> https://github.com/apache/metron/pull/716
>
>
>
> On Tue, Aug 29, 2017 at 8:59 PM Matt Foley  wrote:
>
> > Okay, just to be clear, you’re requesting we wait until Friday, if
> > necessary, to cut an RC with 717 in it?
> > Thanks,
> > --Matt
> >
> > On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
> >
> > 709 is in and 717 is under concerted review by Otto.  I'd like to see
> > it in
> > by Friday.
> >
> > On Tue, 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 8/29/17, 9:34 AM, "Casey Stella"  wrote:
> > >
> > > For my PRs, I'd vote for METRON-1122 being in (commit very
> > imminent).
> > > I'd very much like METRON-1134 to be in as well.
> > >
> > > Beyond that, I'm ok
> > >
> > > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen <
> n...@nickallen.org>
> > > wrote:
> > >
> > > > Thanks for starting the process, Matt.
> > > >
> > > > These are my own open PRs that I would most like to see get
> in.
> > > They 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
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley  >
> > wrote:
> > > >
> > > > > 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
> > > > > in in the next few days.
> > > > >
> > > > > There have been 74 commits since the 0.4.0 release (list
> > appended
> > > to end
> > > > > of this message).
> > > > > I have not yet done a compare to make sure all 74 completed
> > > commits have
> > > > > closed their Jiras, but I will follow up with that info.
> > > > >
> > > > > There are 35 open PRs, see
> > https://github.com/apache/metron/pulls
> > > ,
> > > > which
> > > > > is getting a little clunky.  Surely not all of them can get
> > in in
> > > the
> > > > next
> > > > > few days, but do we want to try to close and include some
> of
> > them?
> > > > >
> > > > > Please respond to the list with your requests to include
> > specific
> > > > > additional PRs before we cut the 0.4.1 release candidate.
> > Let’s
> > > keep it
> > > > > practical so we don’t delay more than a week or so.
> > > > >
> > > > > TIMEFRAME:  Tentatively I would like to start the process
> of
> > > cutting an
> > > > RC
> > > > > this coming Monday 28 August.  If we have too many PRs
> > required to
> > > be in,
> > > > > we may have to slip that.  Likewise, if there is need for
> > urgency,
> > > I can
> > > > > start as soon as tomorrow.  We will be guided by your
> > responses.
> > > > >
> > > > > Thanks,
> > > > > --Matt
> > > > > (Release Manager)
> > > > >
> > > > > COMPLETED PRs as of 22 Aug 2017:
> > > > > METRON-1115 Jackson is not properly serializing
> > readMetadata
> > > and
> > > > > mergeMetadata SensorParserConfig properties  (merrimanr)
> > closes
> > > > > apache/metron#703
> > > > > METRON-1047 REST should use core-site.xml for Hadoop
> > > configuration
> > > > > (merrimanr) closes apache/metron#672
> > > > > METRON- Mislabeled Configuration Property in Ambari
> > > (nickwallen)
> > >

Re: [DISCUSS] Metron release 0.4.1

2017-08-30 Thread Casey Stella

Yeah, I'm not sure we need to hold up the release necessarily, but I think
it'd be a nice capability.  I expect it'll get done prior to friday as it's
pretty close.

On Tue, Aug 29, 2017 at 8:59 PM, Matt Foley  wrote:

> Okay, just to be clear, you’re requesting we wait until Friday, if
> necessary, to cut an RC with 717 in it?
> Thanks,
> --Matt
>
> On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
>
> 709 is in and 717 is under concerted review by Otto.  I'd like to see
> it in
> by Friday.
>
> On Tue, 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 8/29/17, 9:34 AM, "Casey Stella"  wrote:
> >
> > For my PRs, I'd vote for METRON-1122 being in (commit very
> imminent).
> > I'd very much like METRON-1134 to be in as well.
> >
> > Beyond that, I'm ok
> >
> > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen 
> > wrote:
> >
> > > Thanks for starting the process, Matt.
> > >
> > > These are my own open PRs that I would most like to see get in.
> > They 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
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley 
> wrote:
> > >
> > > > 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
> > > > in in the next few days.
> > > >
> > > > There have been 74 commits since the 0.4.0 release (list
> appended
> > to end
> > > > of this message).
> > > > I have not yet done a compare to make sure all 74 completed
> > commits have
> > > > closed their Jiras, but I will follow up with that info.
> > > >
> > > > There are 35 open PRs, see https://github.com/apache/
> metron/pulls
> > ,
> > > which
> > > > is getting a little clunky.  Surely not all of them can get
> in in
> > the
> > > next
> > > > few days, but do we want to try to close and include some of
> them?
> > > >
> > > > Please respond to the list with your requests to include
> specific
> > > > additional PRs before we cut the 0.4.1 release candidate.
> Let’s
> > keep it
> > > > practical so we don’t delay more than a week or so.
> > > >
> > > > TIMEFRAME:  Tentatively I would like to start the process of
> > cutting an
> > > RC
> > > > this coming Monday 28 August.  If we have too many PRs
> required to
> > be in,
> > > > we may have to slip that.  Likewise, if there is need for
> urgency,
> > I can
> > > > start as soon as tomorrow.  We will be guided by your
> responses.
> > > >
> > > > Thanks,
> > > > --Matt
> > > > (Release Manager)
> > > >
> > > > COMPLETED PRs as of 22 Aug 2017:
> > > > METRON-1115 Jackson is not properly serializing
> readMetadata
> > and
> > > > mergeMetadata SensorParserConfig properties  (merrimanr)
> closes
> > > > apache/metron#703
> > > > METRON-1047 REST should use core-site.xml for Hadoop
> > configuration
> > > > (merrimanr) closes apache/metron#672
> > > > METRON- Mislabeled Configuration Property in Ambari
> > (nickwallen)
> > > > closes apache/metron#698
> > > > METRON-1113 UpdateControllerIntegrationTest fails with
> 500
> > error
> > > > (merrimanr) closes apache/metron#701
> > > > METRON-711 StellarShell assigns variables even if an
> exception
> > was
> > > > thrown in the statement. (ottobackwards) closes
> apache/metron#686
> > > > METRON-1110 REST jvm flags property is being overwritten
> when
> > > Kerberos
> > > > is enabled (merrimanr) closes apache/metron#697
> > > > METRON-739 Create Local Profile Runner (nickwallen)
> closes
> > > > apache/metron#693
> > > > METRON-1109 Indexing topology fails to start after
> Kerberos is
>

Re: [DISCUSS] Metron release 0.4.1

2017-08-30 Thread Nick Allen

The following PRs are usability enhancements for the Profiler.  They are
fairly simple 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, I would appreciate some reviews of these PRs.
https://github.com/apache/metron/pull/721
https://github.com/apache/metron/pull/716



On Tue, Aug 29, 2017 at 8:59 PM Matt Foley  wrote:

> Okay, just to be clear, you’re requesting we wait until Friday, if
> necessary, to cut an RC with 717 in it?
> Thanks,
> --Matt
>
> On 8/29/17, 11:45 AM, "Casey Stella"  wrote:
>
> 709 is in and 717 is under concerted review by Otto.  I'd like to see
> it in
> by Friday.
>
> On Tue, 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 8/29/17, 9:34 AM, "Casey Stella"  wrote:
> >
> > For my PRs, I'd vote for METRON-1122 being in (commit very
> imminent).
> > I'd very much like METRON-1134 to be in as well.
> >
> > Beyond that, I'm ok
> >
> > On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen 
> > wrote:
> >
> > > Thanks for starting the process, Matt.
> > >
> > > These are my own open PRs that I would most like to see get in.
> > They 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
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley 
> wrote:
> > >
> > > > 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
> > > > in in the next few days.
> > > >
> > > > There have been 74 commits since the 0.4.0 release (list
> appended
> > to end
> > > > of this message).
> > > > I have not yet done a compare to make sure all 74 completed
> > commits have
> > > > closed their Jiras, but I will follow up with that info.
> > > >
> > > > There are 35 open PRs, see
> https://github.com/apache/metron/pulls
> > ,
> > > which
> > > > is getting a little clunky.  Surely not all of them can get
> in in
> > the
> > > next
> > > > few days, but do we want to try to close and include some of
> them?
> > > >
> > > > Please respond to the list with your requests to include
> specific
> > > > additional PRs before we cut the 0.4.1 release candidate.
> Let’s
> > keep it
> > > > practical so we don’t delay more than a week or so.
> > > >
> > > > TIMEFRAME:  Tentatively I would like to start the process of
> > cutting an
> > > RC
> > > > this coming Monday 28 August.  If we have too many PRs
> required to
> > be in,
> > > > we may have to slip that.  Likewise, if there is need for
> urgency,
> > I can
> > > > start as soon as tomorrow.  We will be guided by your
> responses.
> > > >
> > > > Thanks,
> > > > --Matt
> > > > (Release Manager)
> > > >
> > > > COMPLETED PRs as of 22 Aug 2017:
> > > > METRON-1115 Jackson is not properly serializing
> readMetadata
> > and
> > > > mergeMetadata SensorParserConfig properties  (merrimanr)
> closes
> > > > apache/metron#703
> > > > METRON-1047 REST should use core-site.xml for Hadoop
> > configuration
> > > > (merrimanr) closes apache/metron#672
> > > > METRON- Mislabeled Configuration Property in Ambari
> > (nickwallen)
> > > > closes apache/metron#698
> > > > METRON-1113 UpdateControllerIntegrationTest fails with
> 500
> > error
> > > > (merrimanr) closes apache/metron#701
> > > > METRON-711 StellarShell assigns variables even if an
> exception
> > was
> > > > thrown in the statement. (ottobackwards) closes
> apache/metron#686
> > > > METRON-1110 REST jvm flags property is being overwritten
> when
> > > Kerberos
> > > > is enabled (merrimanr) closes

Re: [DISCUSS] Metron release 0.4.1

2017-08-29 Thread Matt Foley

Okay, just to be clear, you’re requesting we wait until Friday, if necessary, 
to cut an RC with 717 in it? 
Thanks,
--Matt

On 8/29/17, 11:45 AM, "Casey Stella"  wrote:

709 is in and 717 is under concerted review by Otto.  I'd like to see it in
by Friday.

On Tue, 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 8/29/17, 9:34 AM, "Casey Stella"  wrote:
>
> For my PRs, I'd vote for METRON-1122 being in (commit very imminent).
> I'd very much like METRON-1134 to be in as well.
>
> Beyond that, I'm ok
>
> On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen 
> wrote:
>
> > Thanks for starting the process, Matt.
> >
> > These are my own open PRs that I would most like to see get in.
> They 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
> >
> >
> >
> >
> >
> > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley  wrote:
> >
> > > 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
> > > in in the next few days.
> > >
> > > There have been 74 commits since the 0.4.0 release (list appended
> to end
> > > of this message).
> > > I have not yet done a compare to make sure all 74 completed
> commits have
> > > closed their Jiras, but I will follow up with that info.
> > >
> > > There are 35 open PRs, see https://github.com/apache/metron/pulls
> ,
> > which
> > > is getting a little clunky.  Surely not all of them can get in in
> the
> > next
> > > few days, but do we want to try to close and include some of them?
> > >
> > > Please respond to the list with your requests to include specific
> > > additional PRs before we cut the 0.4.1 release candidate.  Let’s
> keep it
> > > practical so we don’t delay more than a week or so.
> > >
> > > TIMEFRAME:  Tentatively I would like to start the process of
> cutting an
> > RC
> > > this coming Monday 28 August.  If we have too many PRs required to
> be in,
> > > we may have to slip that.  Likewise, if there is need for urgency,
> I can
> > > start as soon as tomorrow.  We will be guided by your responses.
> > >
> > > Thanks,
> > > --Matt
> > > (Release Manager)
> > >
> > > COMPLETED PRs as of 22 Aug 2017:
> > > METRON-1115 Jackson is not properly serializing readMetadata
> and
> > > mergeMetadata SensorParserConfig properties  (merrimanr) closes
> > > apache/metron#703
> > > METRON-1047 REST should use core-site.xml for Hadoop
> configuration
> > > (merrimanr) closes apache/metron#672
> > > METRON- Mislabeled Configuration Property in Ambari
> (nickwallen)
> > > closes apache/metron#698
> > > METRON-1113 UpdateControllerIntegrationTest fails with 500
> error
> > > (merrimanr) closes apache/metron#701
> > > METRON-711 StellarShell assigns variables even if an exception
> was
> > > thrown in the statement. (ottobackwards) closes apache/metron#686
> > > METRON-1110 REST jvm flags property is being overwritten when
> > Kerberos
> > > is enabled (merrimanr) closes apache/metron#697
> > > METRON-739 Create Local Profile Runner (nickwallen) closes
> > > apache/metron#693
> > > METRON-1109 Indexing topology fails to start after Kerberos is
> > enabled
> > > (merrimanr) closes apache/metron#696
> > > METRON-1108 Metron configuration tabs are not showing up in
> Ambari
> > > this closes apache/incubator-metron#695
> > > METRON-1078 Metron Indexing fails to stop during Stop 
All
> > > Services (dlyle65535) closes apache/metron#680
> > > METRON-1104 Build Failure - Due to Bootstrap version change
> > > (iraghumitra via justinleet) closes apache/metron#691

Re: [DISCUSS] Metron release 0.4.1

2017-08-29 Thread Casey Stella

709 is in and 717 is under concerted review by Otto.  I'd like to see it in
by Friday.

On Tue, 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 8/29/17, 9:34 AM, "Casey Stella"  wrote:
>
> For my PRs, I'd vote for METRON-1122 being in (commit very imminent).
> I'd very much like METRON-1134 to be in as well.
>
> Beyond that, I'm ok
>
> On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen 
> wrote:
>
> > Thanks for starting the process, Matt.
> >
> > These are my own open PRs that I would most like to see get in.
> They 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
> >
> >
> >
> >
> >
> > On Tue, Aug 22, 2017 at 4:17 PM Matt Foley  wrote:
> >
> > > 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
> > > in in the next few days.
> > >
> > > There have been 74 commits since the 0.4.0 release (list appended
> to end
> > > of this message).
> > > I have not yet done a compare to make sure all 74 completed
> commits have
> > > closed their Jiras, but I will follow up with that info.
> > >
> > > There are 35 open PRs, see https://github.com/apache/metron/pulls
> ,
> > which
> > > is getting a little clunky.  Surely not all of them can get in in
> the
> > next
> > > few days, but do we want to try to close and include some of them?
> > >
> > > Please respond to the list with your requests to include specific
> > > additional PRs before we cut the 0.4.1 release candidate.  Let’s
> keep it
> > > practical so we don’t delay more than a week or so.
> > >
> > > TIMEFRAME:  Tentatively I would like to start the process of
> cutting an
> > RC
> > > this coming Monday 28 August.  If we have too many PRs required to
> be in,
> > > we may have to slip that.  Likewise, if there is need for urgency,
> I can
> > > start as soon as tomorrow.  We will be guided by your responses.
> > >
> > > Thanks,
> > > --Matt
> > > (Release Manager)
> > >
> > > COMPLETED PRs as of 22 Aug 2017:
> > > METRON-1115 Jackson is not properly serializing readMetadata
> and
> > > mergeMetadata SensorParserConfig properties  (merrimanr) closes
> > > apache/metron#703
> > > METRON-1047 REST should use core-site.xml for Hadoop
> configuration
> > > (merrimanr) closes apache/metron#672
> > > METRON- Mislabeled Configuration Property in Ambari
> (nickwallen)
> > > closes apache/metron#698
> > > METRON-1113 UpdateControllerIntegrationTest fails with 500
> error
> > > (merrimanr) closes apache/metron#701
> > > METRON-711 StellarShell assigns variables even if an exception
> was
> > > thrown in the statement. (ottobackwards) closes apache/metron#686
> > > METRON-1110 REST jvm flags property is being overwritten when
> > Kerberos
> > > is enabled (merrimanr) closes apache/metron#697
> > > METRON-739 Create Local Profile Runner (nickwallen) closes
> > > apache/metron#693
> > > METRON-1109 Indexing topology fails to start after Kerberos is
> > enabled
> > > (merrimanr) closes apache/metron#696
> > > METRON-1108 Metron configuration tabs are not showing up in
> Ambari
> > > this closes apache/incubator-metron#695
> > > METRON-1078 Metron Indexing fails to stop during Stop All
> > > Services (dlyle65535) closes apache/metron#680
> > > METRON-1104 Build Failure - Due to Bootstrap version change
> > > (iraghumitra via justinleet) closes apache/metron#691
> > > METRON-1094 MaaS will not start due to classpath error
> relating to
> > > Yarn closes apache/incubator-metron#688
> > > METRON-1102 Add support for ingesting cybox URI observables
> from
> > taxii
> > > feeds closes apache/incubator-metron#689
> > > METRON-838 Incorrect set of ts in FireEye parser (bjigmp via
> > > justinleet) closes apache/metron#528
> > > METRON-322 Global Batching and Flushing (mattf-horton) closes
> > > apache/metron#481
> > > METRON-988 UI for viewing alerts generated by Metron
> (iraghumitra
> > via
> > > nickwallen) closes apache/metron#620
>

Re: [DISCUSS] Metron release 0.4.1

2017-08-29 Thread Matt Foley

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 8/29/17, 9:34 AM, "Casey Stella"  wrote:

For my PRs, I'd vote for METRON-1122 being in (commit very imminent).
I'd very much like METRON-1134 to be in as well.

Beyond that, I'm ok

On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen  wrote:

> Thanks for starting the process, Matt.
>
> These are my own open PRs that I would most like to see get in.  They 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
>
>
>
>
>
> On Tue, Aug 22, 2017 at 4:17 PM Matt Foley  wrote:
>
> > 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
> > in in the next few days.
> >
> > There have been 74 commits since the 0.4.0 release (list appended to end
> > of this message).
> > I have not yet done a compare to make sure all 74 completed commits have
> > closed their Jiras, but I will follow up with that info.
> >
> > There are 35 open PRs, see https://github.com/apache/metron/pulls ,
> which
> > is getting a little clunky.  Surely not all of them can get in in the
> next
> > few days, but do we want to try to close and include some of them?
> >
> > Please respond to the list with your requests to include specific
> > additional PRs before we cut the 0.4.1 release candidate.  Let’s keep it
> > practical so we don’t delay more than a week or so.
> >
> > TIMEFRAME:  Tentatively I would like to start the process of cutting an
> RC
> > this coming Monday 28 August.  If we have too many PRs required to be 
in,
> > we may have to slip that.  Likewise, if there is need for urgency, I can
> > start as soon as tomorrow.  We will be guided by your responses.
> >
> > Thanks,
> > --Matt
> > (Release Manager)
> >
> > COMPLETED PRs as of 22 Aug 2017:
> > METRON-1115 Jackson is not properly serializing readMetadata and
> > mergeMetadata SensorParserConfig properties  (merrimanr) closes
> > apache/metron#703
> > METRON-1047 REST should use core-site.xml for Hadoop configuration
> > (merrimanr) closes apache/metron#672
> > METRON- Mislabeled Configuration Property in Ambari (nickwallen)
> > closes apache/metron#698
> > METRON-1113 UpdateControllerIntegrationTest fails with 500 error
> > (merrimanr) closes apache/metron#701
> > METRON-711 StellarShell assigns variables even if an exception was
> > thrown in the statement. (ottobackwards) closes apache/metron#686
> > METRON-1110 REST jvm flags property is being overwritten when
> Kerberos
> > is enabled (merrimanr) closes apache/metron#697
> > METRON-739 Create Local Profile Runner (nickwallen) closes
> > apache/metron#693
> > METRON-1109 Indexing topology fails to start after Kerberos is
> enabled
> > (merrimanr) closes apache/metron#696
> > METRON-1108 Metron configuration tabs are not showing up in Ambari
> > this closes apache/incubator-metron#695
> > METRON-1078 Metron Indexing fails to stop during Stop All
> > Services (dlyle65535) closes apache/metron#680
> > METRON-1104 Build Failure - Due to Bootstrap version change
> > (iraghumitra via justinleet) closes apache/metron#691
> > METRON-1094 MaaS will not start due to classpath error relating to
> > Yarn closes apache/incubator-metron#688
> > METRON-1102 Add support for ingesting cybox URI observables from
> taxii
> > feeds closes apache/incubator-metron#689
> > METRON-838 Incorrect set of ts in FireEye parser (bjigmp via
> > justinleet) closes apache/metron#528
> > METRON-322 Global Batching and Flushing (mattf-horton) closes
> > apache/metron#481
> > METRON-988 UI for viewing alerts generated by Metron  (iraghumitra
> via
> > nickwallen) closes apache/metron#620
> > METRON-1084 Management UI web server license should be Apache
> > (merrimanr) closes apache/metron#683
> > METRON-1026 threatintel_taxii_load.sh throws exception closes
> > apache/incubator-metron#643
> > METRON-1051 Enable the ability to update indexed messages closes
> > apache/incubator-metron#666
> > METRON-1069 Ambari MPack documentation

Re: [DISCUSS] Metron release 0.4.1

2017-08-29 Thread Casey Stella

For my PRs, I'd vote for METRON-1122 being in (commit very imminent).
I'd very much like METRON-1134 to be in as well.

Beyond that, I'm ok

On Tue, Aug 22, 2017 at 4:37 PM, Nick Allen  wrote:

> Thanks for starting the process, Matt.
>
> These are my own open PRs that I would most like to see get in.  They 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
>
>
>
>
>
> On Tue, Aug 22, 2017 at 4:17 PM Matt Foley  wrote:
>
> > 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
> > in in the next few days.
> >
> > There have been 74 commits since the 0.4.0 release (list appended to end
> > of this message).
> > I have not yet done a compare to make sure all 74 completed commits have
> > closed their Jiras, but I will follow up with that info.
> >
> > There are 35 open PRs, see https://github.com/apache/metron/pulls ,
> which
> > is getting a little clunky.  Surely not all of them can get in in the
> next
> > few days, but do we want to try to close and include some of them?
> >
> > Please respond to the list with your requests to include specific
> > additional PRs before we cut the 0.4.1 release candidate.  Let’s keep it
> > practical so we don’t delay more than a week or so.
> >
> > TIMEFRAME:  Tentatively I would like to start the process of cutting an
> RC
> > this coming Monday 28 August.  If we have too many PRs required to be in,
> > we may have to slip that.  Likewise, if there is need for urgency, I can
> > start as soon as tomorrow.  We will be guided by your responses.
> >
> > Thanks,
> > --Matt
> > (Release Manager)
> >
> > COMPLETED PRs as of 22 Aug 2017:
> > METRON-1115 Jackson is not properly serializing readMetadata and
> > mergeMetadata SensorParserConfig properties  (merrimanr) closes
> > apache/metron#703
> > METRON-1047 REST should use core-site.xml for Hadoop configuration
> > (merrimanr) closes apache/metron#672
> > METRON- Mislabeled Configuration Property in Ambari (nickwallen)
> > closes apache/metron#698
> > METRON-1113 UpdateControllerIntegrationTest fails with 500 error
> > (merrimanr) closes apache/metron#701
> > METRON-711 StellarShell assigns variables even if an exception was
> > thrown in the statement. (ottobackwards) closes apache/metron#686
> > METRON-1110 REST jvm flags property is being overwritten when
> Kerberos
> > is enabled (merrimanr) closes apache/metron#697
> > METRON-739 Create Local Profile Runner (nickwallen) closes
> > apache/metron#693
> > METRON-1109 Indexing topology fails to start after Kerberos is
> enabled
> > (merrimanr) closes apache/metron#696
> > METRON-1108 Metron configuration tabs are not showing up in Ambari
> > this closes apache/incubator-metron#695
> > METRON-1078 Metron Indexing fails to stop during Stop All
> > Services (dlyle65535) closes apache/metron#680
> > METRON-1104 Build Failure - Due to Bootstrap version change
> > (iraghumitra via justinleet) closes apache/metron#691
> > METRON-1094 MaaS will not start due to classpath error relating to
> > Yarn closes apache/incubator-metron#688
> > METRON-1102 Add support for ingesting cybox URI observables from
> taxii
> > feeds closes apache/incubator-metron#689
> > METRON-838 Incorrect set of ts in FireEye parser (bjigmp via
> > justinleet) closes apache/metron#528
> > METRON-322 Global Batching and Flushing (mattf-horton) closes
> > apache/metron#481
> > METRON-988 UI for viewing alerts generated by Metron  (iraghumitra
> via
> > nickwallen) closes apache/metron#620
> > METRON-1084 Management UI web server license should be Apache
> > (merrimanr) closes apache/metron#683
> > METRON-1026 threatintel_taxii_load.sh throws exception closes
> > apache/incubator-metron#643
> > METRON-1051 Enable the ability to update indexed messages closes
> > apache/incubator-metron#666
> > METRON-1069 Ambari MPack documentation around development strategies
> > (justinleet) closes apache/metron#1069
> > METRON-1069 Ambari MPack documentation around development strategies
> > (merrimanr via justinleet) closes apache/metron#1069
> > METRON-1069 Ambari MPack documentation around development strategies
> > (justinleet) closes apache/metron#1069
> > METRON-1076 Management UI status check always reports the service as
> > running (merrimanr) closes apache/metron#678
> > METRON-1075 Add faceted search capabilities (merrimanr) closes
> > apache/metron#679
> > METRON-379 Stellar - No Error When Adding Variables That Do Not Exist
> > (ottobackwards)

[DISCUSS] Metron release 0.4.1

2017-08-22 Thread Matt Foley

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 in in the 
next few days.

There have been 74 commits since the 0.4.0 release (list appended to end of 
this message).
I have not yet done a compare to make sure all 74 completed commits have closed 
their Jiras, but I will follow up with that info.

There are 35 open PRs, see https://github.com/apache/metron/pulls , which is 
getting a little clunky.  Surely not all of them can get in in the next few 
days, but do we want to try to close and include some of them? 

Please respond to the list with your requests to include specific additional 
PRs before we cut the 0.4.1 release candidate.  Let’s keep it practical so we 
don’t delay more than a week or so.

TIMEFRAME:  Tentatively I would like to start the process of cutting an RC this 
coming Monday 28 August.  If we have too many PRs required to be in, we may 
have to slip that.  Likewise, if there is need for urgency, I can start as soon 
as tomorrow.  We will be guided by your responses.

Thanks,
--Matt
(Release Manager)

COMPLETED PRs as of 22 Aug 2017:
METRON-1115 Jackson is not properly serializing readMetadata and 
mergeMetadata SensorParserConfig properties  (merrimanr) closes 
apache/metron#703
METRON-1047 REST should use core-site.xml for Hadoop configuration 
(merrimanr) closes apache/metron#672
METRON- Mislabeled Configuration Property in Ambari (nickwallen) closes 
apache/metron#698
METRON-1113 UpdateControllerIntegrationTest fails with 500 error 
(merrimanr) closes apache/metron#701
METRON-711 StellarShell assigns variables even if an exception was thrown 
in the statement. (ottobackwards) closes apache/metron#686
METRON-1110 REST jvm flags property is being overwritten when Kerberos is 
enabled (merrimanr) closes apache/metron#697
METRON-739 Create Local Profile Runner (nickwallen) closes apache/metron#693
METRON-1109 Indexing topology fails to start after Kerberos is enabled 
(merrimanr) closes apache/metron#696
METRON-1108 Metron configuration tabs are not showing up in Ambari this 
closes apache/incubator-metron#695
METRON-1078 Metron Indexing fails to stop during Stop All 
Services (dlyle65535) closes apache/metron#680
METRON-1104 Build Failure - Due to Bootstrap version change (iraghumitra 
via justinleet) closes apache/metron#691
METRON-1094 MaaS will not start due to classpath error relating to Yarn 
closes apache/incubator-metron#688
METRON-1102 Add support for ingesting cybox URI observables from taxii 
feeds closes apache/incubator-metron#689
METRON-838 Incorrect set of ts in FireEye parser (bjigmp via justinleet) 
closes apache/metron#528
METRON-322 Global Batching and Flushing (mattf-horton) closes 
apache/metron#481
METRON-988 UI for viewing alerts generated by Metron  (iraghumitra via 
nickwallen) closes apache/metron#620
METRON-1084 Management UI web server license should be Apache (merrimanr) 
closes apache/metron#683
METRON-1026 threatintel_taxii_load.sh throws exception closes 
apache/incubator-metron#643
METRON-1051 Enable the ability to update indexed messages closes 
apache/incubator-metron#666
METRON-1069 Ambari MPack documentation around development strategies 
(justinleet) closes apache/metron#1069
METRON-1069 Ambari MPack documentation around development strategies 
(merrimanr via justinleet) closes apache/metron#1069
METRON-1069 Ambari MPack documentation around development strategies 
(justinleet) closes apache/metron#1069
METRON-1076 Management UI status check always reports the service as 
running (merrimanr) closes apache/metron#678
METRON-1075 Add faceted search capabilities (merrimanr) closes 
apache/metron#679
METRON-379 Stellar - No Error When Adding Variables That Do Not Exist 
(ottobackwards) closes apache/metron#675
METRON-1038 Stellar should have a better collection of basic math 
operations closes apache/incubator-metron#650
METRON-1072 Cleanup Maven build warnings (mmiklavc) closes apache/metron#676
METRON-1056 Get field types from Elasticsearch (merrimanr) closes 
apache/metron#662
METRON-1011 Stellar ENRICHMENT functions should enforce submission of 4 
parameters (jasper-k via ottobackwards) closes apache/metron#628
METRON-975 Normalize logging and switch to common idiom with SLF4J 
(mmiklavc) closes apache/metron#599
METRON-681 CSVConverter should trim values (basvdl via ottobackwards) 
closes apache/metron#674
METRON-746 Build Custom Checkstyle and IDE formatting settings (justinleet 
via mmiklavc) closes apache/metron#577
METRON-1060 Add performance timing logging to enrichment topology 
(mmiklavc) closes apache/metron#665
METRON-982 REST STORM Support for

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

Re: [DISCUSS] Metron release 0.4.1

[DISCUSS] Metron release 0.4.1

23 matches

Site Navigation

Mail list logo

Footer information