metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Casey Stella <ceste...@gmail.com>
Subject Re: [INCOMING] Metron 0.4.0 release (RC3)
Date Mon, 19 Jun 2017 14:56:03 GMT
Ok METRON-995 is in, so we should be able to release any time from my
perspective.  I think we're just waiting on some resolution for 941 at this
point (that thread seems dead).

On Fri, Jun 9, 2017 at 6:38 PM, Casey Stella <cestella@gmail.com> wrote:

> I'm willing to be shot down about this, but METRON-995 fixes a pretty
> significant bug around using map variables and temporary variables in
> stellar enrichments.  I'd appreciate if it could get in, but I'll
> understand if we think it shouldn't.
>
> On Sat, Jun 3, 2017 at 4:31 AM, Christian Tramnitz <tramnitz@trasec.de>
> wrote:
>
>> I didn’t touch unit tests because it was already broken before.
>> We agreed to put this into a separate ticket (METRON-962) as it applies
>> to other parsers as well.
>>
>> For now, METRON-941 fixes an actual bug (parsing is broken with the
>> current code).
>>
>>
>> BR,
>>    Christian
>>
>>
>> On 02.06.17, 20:36, "Matt Foley" <mfoley@hortonworks.com im Auftrag von
>> mattf@apache.org> wrote:
>>
>>     Hi Christian,
>>     I agree this would be nice to have.  I also agree with
>> @kylerichardson ‘s review comments that the change (with field renames and
>> outputs) is large enough to require consistent changes in the unit test.
>> Could you please revive the unit test for PaloAltoParser?
>>
>>     Thanks,
>>     --Matt
>>
>>     On 6/2/17, 2:03 AM, "Christian Tramnitz" <tramnitz@trasec.de> wrote:
>>
>>         While not a must-have, METRON-941 / PR-579 should be trivial
>> enough to include it.
>>
>>
>>         Thanks,
>>            Christian
>>
>>
>>         On 01.06.17, 23:17, "Matt Foley" <mattf@apache.org> wrote:
>>
>>             Hi all,
>>
>>             Now that METRON-844 is in, I plan to proceed with the 0.4.0
>> release candidate.  I think 844 was the last item we considered a must-have
>> for the 0.4.0 release, and we want to post this release before
>> incorporating several broad changes that should go in the NEXT release not
>> this one (METRON-777, 942, 975, 876, etc.).
>>
>>
>>
>>             Let me know if anything else is considered must-have for
>> 0.4.0, but I’m going to proceed unless I hear otherwise.  Current HEAD is
>> SHA1= 85872bd686 (METRON-858), I’ll go from there.
>>
>>
>>
>>             Thanks,
>>
>>             --Matt
>>
>>
>>
>>
>>
>>
>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message