Re: [DISCUSS] Next Release - Life After 0.7.1

[Michael Miklavcic]

https://github.com/apache/metron/pull/1552 is now merged.

On Thu, Jan 16, 2020 at 10:22 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:

> Thanks for the suggestion, Casey. Good find, Justin. Per the
> recommendations in the legal thread, I'm going to merge this PR now. I
> don't think we need to spin up another duplicate here.
>
> On Wed, Jan 15, 2020 at 10:00 PM Justin Leet 
> wrote:
>
>> I mentioned it earlier in the thread, but Casey is right about dependabot
>> per https://issues.apache.org/jira/browse/LEGAL-491.
>>
>> On Wed, Jan 15, 2020 at 8:13 PM Casey Stella  wrote:
>>
>> > I'd recommend pulling this into a separate thread and tagging the
>> question
>> > with [MENTORS].  FWIW, I'm of the opinion that you should just denote in
>> > the commit that it was a dependabot contribution, squash like we
>> normally
>> > do and not rewrite the user for attribution.  dependabot does not
>> appear to
>> > have a username, so I think that's ok.
>> >
>> > On Wed, Jan 15, 2020 at 6:18 PM Michael Miklavcic <
>> > michael.miklav...@gmail.com> wrote:
>> >
>> > > Ok, I've tested and +1'ed https://github.com/apache/metron/pull/1552.
>> > > Anyone have any idea how to properly merge and attribute a PR like
>> this?
>> > > Did a quick search on "apache attribution dependabot" and nothing
>> useful
>> > > showed up on that pass.
>> > >
>> > > M
>> > >
>> > > On Tue, Jan 14, 2020 at 11:36 AM Otto Fowler > >
>> > > wrote:
>> > >
>> > > > yes
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On January 14, 2020 at 13:05:17, Michael Miklavcic (
>> > > > michael.miklav...@gmail.com) wrote:
>> > > >
>> > > > We should probably also get this resolved for this release.
>> > > > https://issues.apache.org/jira/browse/METRON-2340. Thoughts?
>> > > >
>> > > > On Mon, Dec 16, 2019 at 2:19 PM Shane Ardell <
>> shane.m.ard...@gmail.com
>> > >
>> > > > wrote:
>> > > >
>> > > > > Both PR #1527  and
>> #1533
>> > > > >  are now merged into
>> > > master.
>> > > > >
>> > > > > On Fri, Dec 13, 2019 at 3:57 PM Justin Leet <
>> justinjl...@gmail.com>
>> > > > wrote:
>> > > > >
>> > > > > > I also brought up https://github.com/apache/metron/pull/1282
>> and
>> > > > > > https://github.com/apache/metron/pull/1552 if anyone has any
>> > > thoughts
>> > > > > on
>> > > > > > them.
>> > > > > >
>> > > > > > On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell <
>> > > > shane.m.ard...@gmail.com>
>> > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Quick update from my end: I just left a +1 on
>> > > > > > > https://github.com/apache/metron/pull/1527 and will merge it
>> > into
>> > > > > master
>> > > > > > > shortly. We are actively looking into the cause of the bug I
>> > > > > encountered
>> > > > > > in
>> > > > > > > https://github.com/apache/metron/pull/1533. It would be nice
>> to
>> > > have
>> > > > > > this
>> > > > > > > in the release, but I would not categorize it as critical like
>> > > #1527.
>> > > > > I'm
>> > > > > > > optimistic we will have this resolved and merged into master
>> by
>> > > this
>> > > > > > > weekend, but I'm fine reducing scope to not include it.
>> > > > > > >
>> > > > > > > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen <
>> n...@nickallen.org>
>> > > > > wrote:
>> > > > > > >
>> > > > > > > > Are we just waiting on the following PRs as release
>> blockers?
>> > Any
>> > > > > > > others?
>> > > > > > > >
>> > > > > > > > - https://github.com/apache/metron/pull/1533
>> > > > > > > > - https://github.com/apache/metron/pull/1527
>> > > > > > > >
>> > > > > > > > Being towards the end of the year, people are going to be on
>> > > > holiday.
>> > > > > > It
>> > > > > > > > would be great if we could focus on reducing scope and
>> getting
>> > a
>> > > > > > release
>> > > > > > > > cut.
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet <
>> > > justinjl...@gmail.com
>> > > > >
>> > > > > > > wrote:
>> > > > > > > >
>> > > > > > > > > https://github.com/apache/metron/pull/1568 and
>> > > > > > > > > https://github.com/apache/metron/pull/1554 are in master
>> > now.
>> > > > > > > > >
>> > > > > > > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet <
>> > > > justinjl...@gmail.com>
>> > > >
>> > > > > > > > wrote:
>> > > > > > > > >
>> > > > > > > > > > I'd like to throw
>> > https://github.com/apache/metron/pull/1552
>> > > > on
>> > > > > > the
>> > > > > > > > > pile.
>> > > > > > > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we
>> > > should
>> > > > > > just
>> > > > > > > > note
>> > > > > > > > > > the contribution comes from dependabot. Would someone
>> more
>> > > > > familiar
>> > > > > > > > with
>> > > > > > > > > > the implications of upgrading that be able to review
>> it, or
>> > > > give
>> > > > > > some
>> > > > > > > > > > advice on what we should be looking for in the review?
>> > > > > > > > > >
>> > > > > > > > > > On Thu, Dec 5, 2019 at 12:06 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Michael Miklavcic]

Thanks for the suggestion, Casey. Good find, Justin. Per the
recommendations in the legal thread, I'm going to merge this PR now. I
don't think we need to spin up another duplicate here.

On Wed, Jan 15, 2020 at 10:00 PM Justin Leet  wrote:

> I mentioned it earlier in the thread, but Casey is right about dependabot
> per https://issues.apache.org/jira/browse/LEGAL-491.
>
> On Wed, Jan 15, 2020 at 8:13 PM Casey Stella  wrote:
>
> > I'd recommend pulling this into a separate thread and tagging the
> question
> > with [MENTORS].  FWIW, I'm of the opinion that you should just denote in
> > the commit that it was a dependabot contribution, squash like we normally
> > do and not rewrite the user for attribution.  dependabot does not appear
> to
> > have a username, so I think that's ok.
> >
> > On Wed, Jan 15, 2020 at 6:18 PM Michael Miklavcic <
> > michael.miklav...@gmail.com> wrote:
> >
> > > Ok, I've tested and +1'ed https://github.com/apache/metron/pull/1552.
> > > Anyone have any idea how to properly merge and attribute a PR like
> this?
> > > Did a quick search on "apache attribution dependabot" and nothing
> useful
> > > showed up on that pass.
> > >
> > > M
> > >
> > > On Tue, Jan 14, 2020 at 11:36 AM Otto Fowler 
> > > wrote:
> > >
> > > > yes
> > > >
> > > >
> > > >
> > > >
> > > > On January 14, 2020 at 13:05:17, Michael Miklavcic (
> > > > michael.miklav...@gmail.com) wrote:
> > > >
> > > > We should probably also get this resolved for this release.
> > > > https://issues.apache.org/jira/browse/METRON-2340. Thoughts?
> > > >
> > > > On Mon, Dec 16, 2019 at 2:19 PM Shane Ardell <
> shane.m.ard...@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Both PR #1527  and
> #1533
> > > > >  are now merged into
> > > master.
> > > > >
> > > > > On Fri, Dec 13, 2019 at 3:57 PM Justin Leet  >
> > > > wrote:
> > > > >
> > > > > > I also brought up https://github.com/apache/metron/pull/1282 and
> > > > > > https://github.com/apache/metron/pull/1552 if anyone has any
> > > thoughts
> > > > > on
> > > > > > them.
> > > > > >
> > > > > > On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell <
> > > > shane.m.ard...@gmail.com>
> > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Quick update from my end: I just left a +1 on
> > > > > > > https://github.com/apache/metron/pull/1527 and will merge it
> > into
> > > > > master
> > > > > > > shortly. We are actively looking into the cause of the bug I
> > > > > encountered
> > > > > > in
> > > > > > > https://github.com/apache/metron/pull/1533. It would be nice
> to
> > > have
> > > > > > this
> > > > > > > in the release, but I would not categorize it as critical like
> > > #1527.
> > > > > I'm
> > > > > > > optimistic we will have this resolved and merged into master by
> > > this
> > > > > > > weekend, but I'm fine reducing scope to not include it.
> > > > > > >
> > > > > > > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen <
> n...@nickallen.org>
> > > > > wrote:
> > > > > > >
> > > > > > > > Are we just waiting on the following PRs as release blockers?
> > Any
> > > > > > > others?
> > > > > > > >
> > > > > > > > - https://github.com/apache/metron/pull/1533
> > > > > > > > - https://github.com/apache/metron/pull/1527
> > > > > > > >
> > > > > > > > Being towards the end of the year, people are going to be on
> > > > holiday.
> > > > > > It
> > > > > > > > would be great if we could focus on reducing scope and
> getting
> > a
> > > > > > release
> > > > > > > > cut.
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet <
> > > justinjl...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > https://github.com/apache/metron/pull/1568 and
> > > > > > > > > https://github.com/apache/metron/pull/1554 are in master
> > now.
> > > > > > > > >
> > > > > > > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet <
> > > > justinjl...@gmail.com>
> > > >
> > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > I'd like to throw
> > https://github.com/apache/metron/pull/1552
> > > > on
> > > > > > the
> > > > > > > > > pile.
> > > > > > > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we
> > > should
> > > > > > just
> > > > > > > > note
> > > > > > > > > > the contribution comes from dependabot. Would someone
> more
> > > > > familiar
> > > > > > > > with
> > > > > > > > > > the implications of upgrading that be able to review it,
> or
> > > > give
> > > > > > some
> > > > > > > > > > advice on what we should be looking for in the review?
> > > > > > > > > >
> > > > > > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > > > > > > shane.m.ard...@gmail.com
> > > > > > > > >
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > >> Speaking on the UI-related PRs that Justin mentioned, I
> > also
> > > > > would
> > > > > > > > like
> > > > > > > > > to
> > > > > > > > > >> see both of them merged before a release. At the 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Justin Leet]

I mentioned it earlier in the thread, but Casey is right about dependabot
per https://issues.apache.org/jira/browse/LEGAL-491.

On Wed, Jan 15, 2020 at 8:13 PM Casey Stella  wrote:

> I'd recommend pulling this into a separate thread and tagging the question
> with [MENTORS].  FWIW, I'm of the opinion that you should just denote in
> the commit that it was a dependabot contribution, squash like we normally
> do and not rewrite the user for attribution.  dependabot does not appear to
> have a username, so I think that's ok.
>
> On Wed, Jan 15, 2020 at 6:18 PM Michael Miklavcic <
> michael.miklav...@gmail.com> wrote:
>
> > Ok, I've tested and +1'ed https://github.com/apache/metron/pull/1552.
> > Anyone have any idea how to properly merge and attribute a PR like this?
> > Did a quick search on "apache attribution dependabot" and nothing useful
> > showed up on that pass.
> >
> > M
> >
> > On Tue, Jan 14, 2020 at 11:36 AM Otto Fowler 
> > wrote:
> >
> > > yes
> > >
> > >
> > >
> > >
> > > On January 14, 2020 at 13:05:17, Michael Miklavcic (
> > > michael.miklav...@gmail.com) wrote:
> > >
> > > We should probably also get this resolved for this release.
> > > https://issues.apache.org/jira/browse/METRON-2340. Thoughts?
> > >
> > > On Mon, Dec 16, 2019 at 2:19 PM Shane Ardell  >
> > > wrote:
> > >
> > > > Both PR #1527  and #1533
> > > >  are now merged into
> > master.
> > > >
> > > > On Fri, Dec 13, 2019 at 3:57 PM Justin Leet 
> > > wrote:
> > > >
> > > > > I also brought up https://github.com/apache/metron/pull/1282 and
> > > > > https://github.com/apache/metron/pull/1552 if anyone has any
> > thoughts
> > > > on
> > > > > them.
> > > > >
> > > > > On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell <
> > > shane.m.ard...@gmail.com>
> > >
> > > > > wrote:
> > > > >
> > > > > > Quick update from my end: I just left a +1 on
> > > > > > https://github.com/apache/metron/pull/1527 and will merge it
> into
> > > > master
> > > > > > shortly. We are actively looking into the cause of the bug I
> > > > encountered
> > > > > in
> > > > > > https://github.com/apache/metron/pull/1533. It would be nice to
> > have
> > > > > this
> > > > > > in the release, but I would not categorize it as critical like
> > #1527.
> > > > I'm
> > > > > > optimistic we will have this resolved and merged into master by
> > this
> > > > > > weekend, but I'm fine reducing scope to not include it.
> > > > > >
> > > > > > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen 
> > > > wrote:
> > > > > >
> > > > > > > Are we just waiting on the following PRs as release blockers?
> Any
> > > > > > others?
> > > > > > >
> > > > > > > - https://github.com/apache/metron/pull/1533
> > > > > > > - https://github.com/apache/metron/pull/1527
> > > > > > >
> > > > > > > Being towards the end of the year, people are going to be on
> > > holiday.
> > > > > It
> > > > > > > would be great if we could focus on reducing scope and getting
> a
> > > > > release
> > > > > > > cut.
> > > > > > >
> > > > > > >
> > > > > > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet <
> > justinjl...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >
> > > > > > > > https://github.com/apache/metron/pull/1568 and
> > > > > > > > https://github.com/apache/metron/pull/1554 are in master
> now.
> > > > > > > >
> > > > > > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet <
> > > justinjl...@gmail.com>
> > >
> > > > > > > wrote:
> > > > > > > >
> > > > > > > > > I'd like to throw
> https://github.com/apache/metron/pull/1552
> > > on
> > > > > the
> > > > > > > > pile.
> > > > > > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we
> > should
> > > > > just
> > > > > > > note
> > > > > > > > > the contribution comes from dependabot. Would someone more
> > > > familiar
> > > > > > > with
> > > > > > > > > the implications of upgrading that be able to review it, or
> > > give
> > > > > some
> > > > > > > > > advice on what we should be looking for in the review?
> > > > > > > > >
> > > > > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > > > > > shane.m.ard...@gmail.com
> > > > > > > >
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >> Speaking on the UI-related PRs that Justin mentioned, I
> also
> > > > would
> > > > > > > like
> > > > > > > > to
> > > > > > > > >> see both of them merged before a release. At the moment,
> > #1527
> > > > > does
> > > > > > > not
> > > > > > > > >> address a few "stale data state" message inconsistencies
> > that
> > > > > become
> > > > > > > > >> apparent as a result of that PR's work (you can read more
> > > about
> > > > it
> > > > > > in
> > > > > > > > the
> > > > > > > > >> PR comments). That said, I think those inconsistencies can
> > be
> > > > > > tracked
> > > > > > > > and
> > > > > > > > >> addressed separately from the current PR.
> > > > > > > > >>
> > > > > > > > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > > > > > > > >> 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Casey Stella]

I'd recommend pulling this into a separate thread and tagging the question
with [MENTORS].  FWIW, I'm of the opinion that you should just denote in
the commit that it was a dependabot contribution, squash like we normally
do and not rewrite the user for attribution.  dependabot does not appear to
have a username, so I think that's ok.

On Wed, Jan 15, 2020 at 6:18 PM Michael Miklavcic <
michael.miklav...@gmail.com> wrote:

> Ok, I've tested and +1'ed https://github.com/apache/metron/pull/1552.
> Anyone have any idea how to properly merge and attribute a PR like this?
> Did a quick search on "apache attribution dependabot" and nothing useful
> showed up on that pass.
>
> M
>
> On Tue, Jan 14, 2020 at 11:36 AM Otto Fowler 
> wrote:
>
> > yes
> >
> >
> >
> >
> > On January 14, 2020 at 13:05:17, Michael Miklavcic (
> > michael.miklav...@gmail.com) wrote:
> >
> > We should probably also get this resolved for this release.
> > https://issues.apache.org/jira/browse/METRON-2340. Thoughts?
> >
> > On Mon, Dec 16, 2019 at 2:19 PM Shane Ardell 
> > wrote:
> >
> > > Both PR #1527  and #1533
> > >  are now merged into
> master.
> > >
> > > On Fri, Dec 13, 2019 at 3:57 PM Justin Leet 
> > wrote:
> > >
> > > > I also brought up https://github.com/apache/metron/pull/1282 and
> > > > https://github.com/apache/metron/pull/1552 if anyone has any
> thoughts
> > > on
> > > > them.
> > > >
> > > > On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell <
> > shane.m.ard...@gmail.com>
> >
> > > > wrote:
> > > >
> > > > > Quick update from my end: I just left a +1 on
> > > > > https://github.com/apache/metron/pull/1527 and will merge it into
> > > master
> > > > > shortly. We are actively looking into the cause of the bug I
> > > encountered
> > > > in
> > > > > https://github.com/apache/metron/pull/1533. It would be nice to
> have
> > > > this
> > > > > in the release, but I would not categorize it as critical like
> #1527.
> > > I'm
> > > > > optimistic we will have this resolved and merged into master by
> this
> > > > > weekend, but I'm fine reducing scope to not include it.
> > > > >
> > > > > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen 
> > > wrote:
> > > > >
> > > > > > Are we just waiting on the following PRs as release blockers? Any
> > > > > others?
> > > > > >
> > > > > > - https://github.com/apache/metron/pull/1533
> > > > > > - https://github.com/apache/metron/pull/1527
> > > > > >
> > > > > > Being towards the end of the year, people are going to be on
> > holiday.
> > > > It
> > > > > > would be great if we could focus on reducing scope and getting a
> > > > release
> > > > > > cut.
> > > > > >
> > > > > >
> > > > > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet <
> justinjl...@gmail.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > https://github.com/apache/metron/pull/1568 and
> > > > > > > https://github.com/apache/metron/pull/1554 are in master now.
> > > > > > >
> > > > > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet <
> > justinjl...@gmail.com>
> >
> > > > > > wrote:
> > > > > > >
> > > > > > > > I'd like to throw https://github.com/apache/metron/pull/1552
> > on
> > > > the
> > > > > > > pile.
> > > > > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we
> should
> > > > just
> > > > > > note
> > > > > > > > the contribution comes from dependabot. Would someone more
> > > familiar
> > > > > > with
> > > > > > > > the implications of upgrading that be able to review it, or
> > give
> > > > some
> > > > > > > > advice on what we should be looking for in the review?
> > > > > > > >
> > > > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > > > > shane.m.ard...@gmail.com
> > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> Speaking on the UI-related PRs that Justin mentioned, I also
> > > would
> > > > > > like
> > > > > > > to
> > > > > > > >> see both of them merged before a release. At the moment,
> #1527
> > > > does
> > > > > > not
> > > > > > > >> address a few "stale data state" message inconsistencies
> that
> > > > become
> > > > > > > >> apparent as a result of that PR's work (you can read more
> > about
> > > it
> > > > > in
> > > > > > > the
> > > > > > > >> PR comments). That said, I think those inconsistencies can
> be
> > > > > tracked
> > > > > > > and
> > > > > > > >> addressed separately from the current PR.
> > > > > > > >>
> > > > > > > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > > > > > > >> michael.miklav...@gmail.com> wrote:
> > > > > > > >>
> > > > > > > >> > I think the junit upgrade should go in also. I'm almost
> > > finished
> > > > > > > >> reviewing
> > > > > > > >> > that.
> > > > > > > >> >
> > > > > > > >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet <
> > > justinjl...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > >> >
> > > > > > > >> > > If we're going to do a bug fix release, I'd like to see
> > > some
> > > > of
> > > > > > the
> > > > > 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Michael Miklavcic]

Ok, I've tested and +1'ed https://github.com/apache/metron/pull/1552.
Anyone have any idea how to properly merge and attribute a PR like this?
Did a quick search on "apache attribution dependabot" and nothing useful
showed up on that pass.

M

On Tue, Jan 14, 2020 at 11:36 AM Otto Fowler 
wrote:

> yes
>
>
>
>
> On January 14, 2020 at 13:05:17, Michael Miklavcic (
> michael.miklav...@gmail.com) wrote:
>
> We should probably also get this resolved for this release.
> https://issues.apache.org/jira/browse/METRON-2340. Thoughts?
>
> On Mon, Dec 16, 2019 at 2:19 PM Shane Ardell 
> wrote:
>
> > Both PR #1527  and #1533
> >  are now merged into master.
> >
> > On Fri, Dec 13, 2019 at 3:57 PM Justin Leet 
> wrote:
> >
> > > I also brought up https://github.com/apache/metron/pull/1282 and
> > > https://github.com/apache/metron/pull/1552 if anyone has any thoughts
> > on
> > > them.
> > >
> > > On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell <
> shane.m.ard...@gmail.com>
>
> > > wrote:
> > >
> > > > Quick update from my end: I just left a +1 on
> > > > https://github.com/apache/metron/pull/1527 and will merge it into
> > master
> > > > shortly. We are actively looking into the cause of the bug I
> > encountered
> > > in
> > > > https://github.com/apache/metron/pull/1533. It would be nice to have
> > > this
> > > > in the release, but I would not categorize it as critical like #1527.
> > I'm
> > > > optimistic we will have this resolved and merged into master by this
> > > > weekend, but I'm fine reducing scope to not include it.
> > > >
> > > > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen 
> > wrote:
> > > >
> > > > > Are we just waiting on the following PRs as release blockers? Any
> > > > others?
> > > > >
> > > > > - https://github.com/apache/metron/pull/1533
> > > > > - https://github.com/apache/metron/pull/1527
> > > > >
> > > > > Being towards the end of the year, people are going to be on
> holiday.
> > > It
> > > > > would be great if we could focus on reducing scope and getting a
> > > release
> > > > > cut.
> > > > >
> > > > >
> > > > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet  >
> > > > wrote:
> > > > >
> > > > > > https://github.com/apache/metron/pull/1568 and
> > > > > > https://github.com/apache/metron/pull/1554 are in master now.
> > > > > >
> > > > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet <
> justinjl...@gmail.com>
>
> > > > > wrote:
> > > > > >
> > > > > > > I'd like to throw https://github.com/apache/metron/pull/1552
> on
> > > the
> > > > > > pile.
> > > > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we should
> > > just
> > > > > note
> > > > > > > the contribution comes from dependabot. Would someone more
> > familiar
> > > > > with
> > > > > > > the implications of upgrading that be able to review it, or
> give
> > > some
> > > > > > > advice on what we should be looking for in the review?
> > > > > > >
> > > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > > > shane.m.ard...@gmail.com
> > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Speaking on the UI-related PRs that Justin mentioned, I also
> > would
> > > > > like
> > > > > > to
> > > > > > >> see both of them merged before a release. At the moment, #1527
> > > does
> > > > > not
> > > > > > >> address a few "stale data state" message inconsistencies that
> > > become
> > > > > > >> apparent as a result of that PR's work (you can read more
> about
> > it
> > > > in
> > > > > > the
> > > > > > >> PR comments). That said, I think those inconsistencies can be
> > > > tracked
> > > > > > and
> > > > > > >> addressed separately from the current PR.
> > > > > > >>
> > > > > > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > > > > > >> michael.miklav...@gmail.com> wrote:
> > > > > > >>
> > > > > > >> > I think the junit upgrade should go in also. I'm almost
> > finished
> > > > > > >> reviewing
> > > > > > >> > that.
> > > > > > >> >
> > > > > > >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet <
> > justinjl...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > >> >
> > > > > > >> > > If we're going to do a bug fix release, I'd like to see
> > some
> > > of
> > > > > the
> > > > > > >> low
> > > > > > >> > > hanging fix PRs get finished and merged prior to the
> > release.
> > > > > We've
> > > > > > >> been
> > > > > > >> > > lax about getting them cleaned up, so I'd like to use a
> > > release
> > > > as
> > > > > > an
> > > > > > >> > > opportunity to whittle the PRs down and put out a really
> > solid
> > > > > > >> release.
> > > > > > >> > >
> > > > > > >> > > https://github.com/apache/metron/pull/1568 should be in
> > > before
> > > > > > >> release.
> > > > > > >> > It
> > > > > > >> > > addresses an issue with our validation of
> > > > > dependencies_with_url.csv
> > > > > > >> and
> > > > > > >> > > it's validation.
> > > > > > >> > > Should https://github.com/apache/metron/pull/1282 be in?
> > > Seems

Re: [DISCUSS] Next Release - Life After 0.7.1

[Otto Fowler]

yes




On January 14, 2020 at 13:05:17, Michael Miklavcic (
michael.miklav...@gmail.com) wrote:

We should probably also get this resolved for this release.
https://issues.apache.org/jira/browse/METRON-2340. Thoughts?

On Mon, Dec 16, 2019 at 2:19 PM Shane Ardell 
wrote:

> Both PR #1527  and #1533
>  are now merged into master.
>
> On Fri, Dec 13, 2019 at 3:57 PM Justin Leet 
wrote:
>
> > I also brought up https://github.com/apache/metron/pull/1282 and
> > https://github.com/apache/metron/pull/1552 if anyone has any thoughts
> on
> > them.
> >
> > On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell 

> > wrote:
> >
> > > Quick update from my end: I just left a +1 on
> > > https://github.com/apache/metron/pull/1527 and will merge it into
> master
> > > shortly. We are actively looking into the cause of the bug I
> encountered
> > in
> > > https://github.com/apache/metron/pull/1533. It would be nice to have
> > this
> > > in the release, but I would not categorize it as critical like #1527.
> I'm
> > > optimistic we will have this resolved and merged into master by this
> > > weekend, but I'm fine reducing scope to not include it.
> > >
> > > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen 
> wrote:
> > >
> > > > Are we just waiting on the following PRs as release blockers? Any
> > > others?
> > > >
> > > > - https://github.com/apache/metron/pull/1533
> > > > - https://github.com/apache/metron/pull/1527
> > > >
> > > > Being towards the end of the year, people are going to be on
holiday.
> > It
> > > > would be great if we could focus on reducing scope and getting a
> > release
> > > > cut.
> > > >
> > > >
> > > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet 
> > > wrote:
> > > >
> > > > > https://github.com/apache/metron/pull/1568 and
> > > > > https://github.com/apache/metron/pull/1554 are in master now.
> > > > >
> > > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet 

> > > > wrote:
> > > > >
> > > > > > I'd like to throw https://github.com/apache/metron/pull/1552 on
> > the
> > > > > pile.
> > > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we should
> > just
> > > > note
> > > > > > the contribution comes from dependabot. Would someone more
> familiar
> > > > with
> > > > > > the implications of upgrading that be able to review it, or
give
> > some
> > > > > > advice on what we should be looking for in the review?
> > > > > >
> > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > > shane.m.ard...@gmail.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > >> Speaking on the UI-related PRs that Justin mentioned, I also
> would
> > > > like
> > > > > to
> > > > > >> see both of them merged before a release. At the moment, #1527
> > does
> > > > not
> > > > > >> address a few "stale data state" message inconsistencies that
> > become
> > > > > >> apparent as a result of that PR's work (you can read more
about
> it
> > > in
> > > > > the
> > > > > >> PR comments). That said, I think those inconsistencies can be
> > > tracked
> > > > > and
> > > > > >> addressed separately from the current PR.
> > > > > >>
> > > > > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > > > > >> michael.miklav...@gmail.com> wrote:
> > > > > >>
> > > > > >> > I think the junit upgrade should go in also. I'm almost
> finished
> > > > > >> reviewing
> > > > > >> > that.
> > > > > >> >
> > > > > >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet <
> justinjl...@gmail.com
> > >
> > > > > wrote:
> > > > > >> >
> > > > > >> > > If we're going to do a bug fix release, I'd like to see
> some
> > of
> > > > the
> > > > > >> low
> > > > > >> > > hanging fix PRs get finished and merged prior to the
> release.
> > > > We've
> > > > > >> been
> > > > > >> > > lax about getting them cleaned up, so I'd like to use a
> > release
> > > as
> > > > > an
> > > > > >> > > opportunity to whittle the PRs down and put out a really
> solid
> > > > > >> release.
> > > > > >> > >
> > > > > >> > > https://github.com/apache/metron/pull/1568 should be in
> > before
> > > > > >> release.
> > > > > >> > It
> > > > > >> > > addresses an issue with our validation of
> > > > dependencies_with_url.csv
> > > > > >> and
> > > > > >> > > it's validation.
> > > > > >> > > Should https://github.com/apache/metron/pull/1282 be in?
> > Seems
> > > > like
> > > > > >> that
> > > > > >> > > should have been merged awhile ago.
> > > > > >> > >
> > > > > >> > > There's also a couple UI performance / bug fixes PRs (e.g.
> > > > > >> > > https://github.com/apache/metron/pull/1533 and
> > > > > >> > > https://github.com/apache/metron/pull/1527) that have been
> > > > sitting
> > > > > >> > awhile.
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > On Thu, Dec 5, 2019 at 10:32 AM Nick Allen <
> > n...@nickallen.org>
> > > > > >> wrote:
> > > > > >> > >
> > > > > >> > > > Hello Metron'ers -
> > > > > >> > > >
> > > > > >> > > > I would like to make the case that 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Michael Miklavcic]

We should probably also get this resolved for this release.
https://issues.apache.org/jira/browse/METRON-2340. Thoughts?

On Mon, Dec 16, 2019 at 2:19 PM Shane Ardell 
wrote:

> Both PR #1527  and #1533
>  are now merged into master.
>
> On Fri, Dec 13, 2019 at 3:57 PM Justin Leet  wrote:
>
> > I also brought up https://github.com/apache/metron/pull/1282 and
> > https://github.com/apache/metron/pull/1552  if anyone has any thoughts
> on
> > them.
> >
> > On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell 
> > wrote:
> >
> > > Quick update from my end: I just left a +1 on
> > > https://github.com/apache/metron/pull/1527 and will merge it into
> master
> > > shortly. We are actively looking into the cause of the bug I
> encountered
> > in
> > > https://github.com/apache/metron/pull/1533. It would be nice to have
> > this
> > > in the release, but I would not categorize it as critical like #1527.
> I'm
> > > optimistic we will have this resolved and merged into master by this
> > > weekend, but I'm fine reducing scope to not include it.
> > >
> > > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen 
> wrote:
> > >
> > > > Are we just waiting on the following PRs as release blockers?  Any
> > > others?
> > > >
> > > >- https://github.com/apache/metron/pull/1533
> > > >- https://github.com/apache/metron/pull/1527
> > > >
> > > > Being towards the end of the year, people are going to be on holiday.
> > It
> > > > would be great if we could focus on reducing scope and getting a
> > release
> > > > cut.
> > > >
> > > >
> > > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet 
> > > wrote:
> > > >
> > > > > https://github.com/apache/metron/pull/1568 and
> > > > > https://github.com/apache/metron/pull/1554 are in master now.
> > > > >
> > > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet 
> > > > wrote:
> > > > >
> > > > > > I'd like to throw https://github.com/apache/metron/pull/1552 on
> > the
> > > > > pile.
> > > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we should
> > just
> > > > note
> > > > > > the contribution comes from dependabot. Would someone more
> familiar
> > > > with
> > > > > > the implications of upgrading that be able to review it, or give
> > some
> > > > > > advice on what we should be looking for in the review?
> > > > > >
> > > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > > shane.m.ard...@gmail.com
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > >> Speaking on the UI-related PRs that Justin mentioned, I also
> would
> > > > like
> > > > > to
> > > > > >> see both of them merged before a release. At the moment, #1527
> > does
> > > > not
> > > > > >> address a few "stale data state" message inconsistencies that
> > become
> > > > > >> apparent as a result of that PR's work (you can read more about
> it
> > > in
> > > > > the
> > > > > >> PR comments). That said, I think those inconsistencies can be
> > > tracked
> > > > > and
> > > > > >> addressed separately from the current PR.
> > > > > >>
> > > > > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > > > > >> michael.miklav...@gmail.com> wrote:
> > > > > >>
> > > > > >> > I think the junit upgrade should go in also. I'm almost
> finished
> > > > > >> reviewing
> > > > > >> > that.
> > > > > >> >
> > > > > >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet <
> justinjl...@gmail.com
> > >
> > > > > wrote:
> > > > > >> >
> > > > > >> > >  If we're going to do a bug fix release, I'd like to see
> some
> > of
> > > > the
> > > > > >> low
> > > > > >> > > hanging fix PRs get finished and merged prior to the
> release.
> > > > We've
> > > > > >> been
> > > > > >> > > lax about getting them cleaned up, so I'd like to use a
> > release
> > > as
> > > > > an
> > > > > >> > > opportunity to whittle the PRs down and put out a really
> solid
> > > > > >> release.
> > > > > >> > >
> > > > > >> > > https://github.com/apache/metron/pull/1568 should be in
> > before
> > > > > >> release.
> > > > > >> > It
> > > > > >> > > addresses an issue with our validation of
> > > > dependencies_with_url.csv
> > > > > >> and
> > > > > >> > > it's validation.
> > > > > >> > > Should https://github.com/apache/metron/pull/1282 be in?
> > Seems
> > > > like
> > > > > >> that
> > > > > >> > > should have been merged awhile ago.
> > > > > >> > >
> > > > > >> > > There's also a couple UI performance / bug fixes PRs (e.g.
> > > > > >> > > https://github.com/apache/metron/pull/1533 and
> > > > > >> > > https://github.com/apache/metron/pull/1527) that have been
> > > > sitting
> > > > > >> > awhile.
> > > > > >> > >
> > > > > >> > >
> > > > > >> > >
> > > > > >> > > On Thu, Dec 5, 2019 at 10:32 AM Nick Allen <
> > n...@nickallen.org>
> > > > > >> wrote:
> > > > > >> > >
> > > > > >> > > > Hello Metron'ers -
> > > > > >> > > >
> > > > > >> > > > I would like to make the case that it is time for us to
> cut
> > > the
> > > > > next
> > > > > >> > > Apache
> > > > > >> > 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Michael Miklavcic]

Justin, I commented on https://github.com/apache/metron/pull/1282 - just
want to be sure we get the final +1 as a matter of community traditions.
I'm looking at 1552 right now.


On Fri, Dec 13, 2019 at 1:57 PM Justin Leet  wrote:

> I also brought up https://github.com/apache/metron/pull/1282 and
> https://github.com/apache/metron/pull/1552  if anyone has any thoughts on
> them.
>
> On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell 
> wrote:
>
> > Quick update from my end: I just left a +1 on
> > https://github.com/apache/metron/pull/1527 and will merge it into master
> > shortly. We are actively looking into the cause of the bug I encountered
> in
> > https://github.com/apache/metron/pull/1533. It would be nice to have
> this
> > in the release, but I would not categorize it as critical like #1527. I'm
> > optimistic we will have this resolved and merged into master by this
> > weekend, but I'm fine reducing scope to not include it.
> >
> > On Fri, Dec 13, 2019 at 11:24 AM Nick Allen  wrote:
> >
> > > Are we just waiting on the following PRs as release blockers?  Any
> > others?
> > >
> > >- https://github.com/apache/metron/pull/1533
> > >- https://github.com/apache/metron/pull/1527
> > >
> > > Being towards the end of the year, people are going to be on holiday.
> It
> > > would be great if we could focus on reducing scope and getting a
> release
> > > cut.
> > >
> > >
> > > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet 
> > wrote:
> > >
> > > > https://github.com/apache/metron/pull/1568 and
> > > > https://github.com/apache/metron/pull/1554 are in master now.
> > > >
> > > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet 
> > > wrote:
> > > >
> > > > > I'd like to throw https://github.com/apache/metron/pull/1552 on
> the
> > > > pile.
> > > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we should
> just
> > > note
> > > > > the contribution comes from dependabot. Would someone more familiar
> > > with
> > > > > the implications of upgrading that be able to review it, or give
> some
> > > > > advice on what we should be looking for in the review?
> > > > >
> > > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> > shane.m.ard...@gmail.com
> > > >
> > > > > wrote:
> > > > >
> > > > >> Speaking on the UI-related PRs that Justin mentioned, I also would
> > > like
> > > > to
> > > > >> see both of them merged before a release. At the moment, #1527
> does
> > > not
> > > > >> address a few "stale data state" message inconsistencies that
> become
> > > > >> apparent as a result of that PR's work (you can read more about it
> > in
> > > > the
> > > > >> PR comments). That said, I think those inconsistencies can be
> > tracked
> > > > and
> > > > >> addressed separately from the current PR.
> > > > >>
> > > > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > > > >> michael.miklav...@gmail.com> wrote:
> > > > >>
> > > > >> > I think the junit upgrade should go in also. I'm almost finished
> > > > >> reviewing
> > > > >> > that.
> > > > >> >
> > > > >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet  >
> > > > wrote:
> > > > >> >
> > > > >> > >  If we're going to do a bug fix release, I'd like to see some
> of
> > > the
> > > > >> low
> > > > >> > > hanging fix PRs get finished and merged prior to the release.
> > > We've
> > > > >> been
> > > > >> > > lax about getting them cleaned up, so I'd like to use a
> release
> > as
> > > > an
> > > > >> > > opportunity to whittle the PRs down and put out a really solid
> > > > >> release.
> > > > >> > >
> > > > >> > > https://github.com/apache/metron/pull/1568 should be in
> before
> > > > >> release.
> > > > >> > It
> > > > >> > > addresses an issue with our validation of
> > > dependencies_with_url.csv
> > > > >> and
> > > > >> > > it's validation.
> > > > >> > > Should https://github.com/apache/metron/pull/1282 be in?
> Seems
> > > like
> > > > >> that
> > > > >> > > should have been merged awhile ago.
> > > > >> > >
> > > > >> > > There's also a couple UI performance / bug fixes PRs (e.g.
> > > > >> > > https://github.com/apache/metron/pull/1533 and
> > > > >> > > https://github.com/apache/metron/pull/1527) that have been
> > > sitting
> > > > >> > awhile.
> > > > >> > >
> > > > >> > >
> > > > >> > >
> > > > >> > > On Thu, Dec 5, 2019 at 10:32 AM Nick Allen <
> n...@nickallen.org>
> > > > >> wrote:
> > > > >> > >
> > > > >> > > > Hello Metron'ers -
> > > > >> > > >
> > > > >> > > > I would like to make the case that it is time for us to cut
> > the
> > > > next
> > > > >> > > Apache
> > > > >> > > > Metron release.
> > > > >> > > >
> > > > >> > > >- Our last release was 0.7.1 on May 15th
> > > > >> > > ><
> > > > >> > > >
> > > > >> > >
> > > > >> >
> > > > >>
> > > >
> > >
> >
> https://lists.apache.org/thread.html/e2e532cbb63be757d0875718b082c069a268f57a9087510f196be09b%40%3Cdev.metron.apache.org%3E
> > > > >> > > > >.
> > > > >> > > >It has been *~6 months* since this release.
> > > > >> > > >
> > > > >> > > >
> > > > >> > > >- We 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Justin Leet]

I also brought up https://github.com/apache/metron/pull/1282 and
https://github.com/apache/metron/pull/1552  if anyone has any thoughts on
them.

On Fri, Dec 13, 2019 at 11:58 AM Shane Ardell 
wrote:

> Quick update from my end: I just left a +1 on
> https://github.com/apache/metron/pull/1527 and will merge it into master
> shortly. We are actively looking into the cause of the bug I encountered in
> https://github.com/apache/metron/pull/1533. It would be nice to have this
> in the release, but I would not categorize it as critical like #1527. I'm
> optimistic we will have this resolved and merged into master by this
> weekend, but I'm fine reducing scope to not include it.
>
> On Fri, Dec 13, 2019 at 11:24 AM Nick Allen  wrote:
>
> > Are we just waiting on the following PRs as release blockers?  Any
> others?
> >
> >- https://github.com/apache/metron/pull/1533
> >- https://github.com/apache/metron/pull/1527
> >
> > Being towards the end of the year, people are going to be on holiday. It
> > would be great if we could focus on reducing scope and getting a release
> > cut.
> >
> >
> > On Sat, Dec 7, 2019 at 10:04 AM Justin Leet 
> wrote:
> >
> > > https://github.com/apache/metron/pull/1568 and
> > > https://github.com/apache/metron/pull/1554 are in master now.
> > >
> > > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet 
> > wrote:
> > >
> > > > I'd like to throw https://github.com/apache/metron/pull/1552 on the
> > > pile.
> > > > Per https://issues.apache.org/jira/browse/LEGAL-491, we should just
> > note
> > > > the contribution comes from dependabot. Would someone more familiar
> > with
> > > > the implications of upgrading that be able to review it, or give some
> > > > advice on what we should be looking for in the review?
> > > >
> > > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell <
> shane.m.ard...@gmail.com
> > >
> > > > wrote:
> > > >
> > > >> Speaking on the UI-related PRs that Justin mentioned, I also would
> > like
> > > to
> > > >> see both of them merged before a release. At the moment, #1527 does
> > not
> > > >> address a few "stale data state" message inconsistencies that become
> > > >> apparent as a result of that PR's work (you can read more about it
> in
> > > the
> > > >> PR comments). That said, I think those inconsistencies can be
> tracked
> > > and
> > > >> addressed separately from the current PR.
> > > >>
> > > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > > >> michael.miklav...@gmail.com> wrote:
> > > >>
> > > >> > I think the junit upgrade should go in also. I'm almost finished
> > > >> reviewing
> > > >> > that.
> > > >> >
> > > >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet 
> > > wrote:
> > > >> >
> > > >> > >  If we're going to do a bug fix release, I'd like to see some of
> > the
> > > >> low
> > > >> > > hanging fix PRs get finished and merged prior to the release.
> > We've
> > > >> been
> > > >> > > lax about getting them cleaned up, so I'd like to use a release
> as
> > > an
> > > >> > > opportunity to whittle the PRs down and put out a really solid
> > > >> release.
> > > >> > >
> > > >> > > https://github.com/apache/metron/pull/1568 should be in before
> > > >> release.
> > > >> > It
> > > >> > > addresses an issue with our validation of
> > dependencies_with_url.csv
> > > >> and
> > > >> > > it's validation.
> > > >> > > Should https://github.com/apache/metron/pull/1282 be in? Seems
> > like
> > > >> that
> > > >> > > should have been merged awhile ago.
> > > >> > >
> > > >> > > There's also a couple UI performance / bug fixes PRs (e.g.
> > > >> > > https://github.com/apache/metron/pull/1533 and
> > > >> > > https://github.com/apache/metron/pull/1527) that have been
> > sitting
> > > >> > awhile.
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > On Thu, Dec 5, 2019 at 10:32 AM Nick Allen 
> > > >> wrote:
> > > >> > >
> > > >> > > > Hello Metron'ers -
> > > >> > > >
> > > >> > > > I would like to make the case that it is time for us to cut
> the
> > > next
> > > >> > > Apache
> > > >> > > > Metron release.
> > > >> > > >
> > > >> > > >- Our last release was 0.7.1 on May 15th
> > > >> > > ><
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://lists.apache.org/thread.html/e2e532cbb63be757d0875718b082c069a268f57a9087510f196be09b%40%3Cdev.metron.apache.org%3E
> > > >> > > > >.
> > > >> > > >It has been *~6 months* since this release.
> > > >> > > >
> > > >> > > >
> > > >> > > >- We have *102 changes* in master since the last release.
> > This
> > > >> > figure
> > > >> > > >excludes the two feature branches currently undergoing
> active
> > > >> > > > development.
> > > >> > > >
> > > >> > > >
> > > >> > > >- We should cut a release *prior to merging in any other
> > > >> significant
> > > >> > > >changes* from either feature branch.  The two active
> feature
> > > >> > branches
> > > >> > > >include ~47 other changes at this point in time.
> > > >> > > >
> > > >> > > >
> > > >> > > >- These 102 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Shane Ardell]

Quick update from my end: I just left a +1 on
https://github.com/apache/metron/pull/1527 and will merge it into master
shortly. We are actively looking into the cause of the bug I encountered in
https://github.com/apache/metron/pull/1533. It would be nice to have this
in the release, but I would not categorize it as critical like #1527. I'm
optimistic we will have this resolved and merged into master by this
weekend, but I'm fine reducing scope to not include it.

On Fri, Dec 13, 2019 at 11:24 AM Nick Allen  wrote:

> Are we just waiting on the following PRs as release blockers?  Any others?
>
>- https://github.com/apache/metron/pull/1533
>- https://github.com/apache/metron/pull/1527
>
> Being towards the end of the year, people are going to be on holiday. It
> would be great if we could focus on reducing scope and getting a release
> cut.
>
>
> On Sat, Dec 7, 2019 at 10:04 AM Justin Leet  wrote:
>
> > https://github.com/apache/metron/pull/1568 and
> > https://github.com/apache/metron/pull/1554 are in master now.
> >
> > On Fri, Dec 6, 2019 at 7:16 PM Justin Leet 
> wrote:
> >
> > > I'd like to throw https://github.com/apache/metron/pull/1552 on the
> > pile.
> > > Per https://issues.apache.org/jira/browse/LEGAL-491, we should just
> note
> > > the contribution comes from dependabot. Would someone more familiar
> with
> > > the implications of upgrading that be able to review it, or give some
> > > advice on what we should be looking for in the review?
> > >
> > > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell  >
> > > wrote:
> > >
> > >> Speaking on the UI-related PRs that Justin mentioned, I also would
> like
> > to
> > >> see both of them merged before a release. At the moment, #1527 does
> not
> > >> address a few "stale data state" message inconsistencies that become
> > >> apparent as a result of that PR's work (you can read more about it in
> > the
> > >> PR comments). That said, I think those inconsistencies can be tracked
> > and
> > >> addressed separately from the current PR.
> > >>
> > >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> > >> michael.miklav...@gmail.com> wrote:
> > >>
> > >> > I think the junit upgrade should go in also. I'm almost finished
> > >> reviewing
> > >> > that.
> > >> >
> > >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet 
> > wrote:
> > >> >
> > >> > >  If we're going to do a bug fix release, I'd like to see some of
> the
> > >> low
> > >> > > hanging fix PRs get finished and merged prior to the release.
> We've
> > >> been
> > >> > > lax about getting them cleaned up, so I'd like to use a release as
> > an
> > >> > > opportunity to whittle the PRs down and put out a really solid
> > >> release.
> > >> > >
> > >> > > https://github.com/apache/metron/pull/1568 should be in before
> > >> release.
> > >> > It
> > >> > > addresses an issue with our validation of
> dependencies_with_url.csv
> > >> and
> > >> > > it's validation.
> > >> > > Should https://github.com/apache/metron/pull/1282 be in? Seems
> like
> > >> that
> > >> > > should have been merged awhile ago.
> > >> > >
> > >> > > There's also a couple UI performance / bug fixes PRs (e.g.
> > >> > > https://github.com/apache/metron/pull/1533 and
> > >> > > https://github.com/apache/metron/pull/1527) that have been
> sitting
> > >> > awhile.
> > >> > >
> > >> > >
> > >> > >
> > >> > > On Thu, Dec 5, 2019 at 10:32 AM Nick Allen 
> > >> wrote:
> > >> > >
> > >> > > > Hello Metron'ers -
> > >> > > >
> > >> > > > I would like to make the case that it is time for us to cut the
> > next
> > >> > > Apache
> > >> > > > Metron release.
> > >> > > >
> > >> > > >- Our last release was 0.7.1 on May 15th
> > >> > > ><
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://lists.apache.org/thread.html/e2e532cbb63be757d0875718b082c069a268f57a9087510f196be09b%40%3Cdev.metron.apache.org%3E
> > >> > > > >.
> > >> > > >It has been *~6 months* since this release.
> > >> > > >
> > >> > > >
> > >> > > >- We have *102 changes* in master since the last release.
> This
> > >> > figure
> > >> > > >excludes the two feature branches currently undergoing active
> > >> > > > development.
> > >> > > >
> > >> > > >
> > >> > > >- We should cut a release *prior to merging in any other
> > >> significant
> > >> > > >changes* from either feature branch.  The two active feature
> > >> > branches
> > >> > > >include ~47 other changes at this point in time.
> > >> > > >
> > >> > > >
> > >> > > >- These 102 changes include some very nice *bug fixes and
> > >> usability
> > >> > > >improvements*. I would propose that we treat this as a
> bug-fix
> > >> > release
> > >> > > >and label it as *Metron 0.7.2*.
> > >> > > >
> > >> > > > Please let me know if you agree or disagree with this call for a
> > >> > release.
> > >> > > >
> > >> > > > For those interested, here are the 102 unreleased changes in
> > master.
> > >> > > >
> > >> > > > METRON-2323 Increase unit test coverage for Alerts List
> (sardell)
> > 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Nick Allen]

Are we just waiting on the following PRs as release blockers?  Any others?

   - https://github.com/apache/metron/pull/1533
   - https://github.com/apache/metron/pull/1527

Being towards the end of the year, people are going to be on holiday. It
would be great if we could focus on reducing scope and getting a release
cut.


On Sat, Dec 7, 2019 at 10:04 AM Justin Leet  wrote:

> https://github.com/apache/metron/pull/1568 and
> https://github.com/apache/metron/pull/1554 are in master now.
>
> On Fri, Dec 6, 2019 at 7:16 PM Justin Leet  wrote:
>
> > I'd like to throw https://github.com/apache/metron/pull/1552 on the
> pile.
> > Per https://issues.apache.org/jira/browse/LEGAL-491, we should just note
> > the contribution comes from dependabot. Would someone more familiar with
> > the implications of upgrading that be able to review it, or give some
> > advice on what we should be looking for in the review?
> >
> > On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell 
> > wrote:
> >
> >> Speaking on the UI-related PRs that Justin mentioned, I also would like
> to
> >> see both of them merged before a release. At the moment, #1527 does not
> >> address a few "stale data state" message inconsistencies that become
> >> apparent as a result of that PR's work (you can read more about it in
> the
> >> PR comments). That said, I think those inconsistencies can be tracked
> and
> >> addressed separately from the current PR.
> >>
> >> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
> >> michael.miklav...@gmail.com> wrote:
> >>
> >> > I think the junit upgrade should go in also. I'm almost finished
> >> reviewing
> >> > that.
> >> >
> >> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet 
> wrote:
> >> >
> >> > >  If we're going to do a bug fix release, I'd like to see some of the
> >> low
> >> > > hanging fix PRs get finished and merged prior to the release. We've
> >> been
> >> > > lax about getting them cleaned up, so I'd like to use a release as
> an
> >> > > opportunity to whittle the PRs down and put out a really solid
> >> release.
> >> > >
> >> > > https://github.com/apache/metron/pull/1568 should be in before
> >> release.
> >> > It
> >> > > addresses an issue with our validation of dependencies_with_url.csv
> >> and
> >> > > it's validation.
> >> > > Should https://github.com/apache/metron/pull/1282 be in? Seems like
> >> that
> >> > > should have been merged awhile ago.
> >> > >
> >> > > There's also a couple UI performance / bug fixes PRs (e.g.
> >> > > https://github.com/apache/metron/pull/1533 and
> >> > > https://github.com/apache/metron/pull/1527) that have been sitting
> >> > awhile.
> >> > >
> >> > >
> >> > >
> >> > > On Thu, Dec 5, 2019 at 10:32 AM Nick Allen 
> >> wrote:
> >> > >
> >> > > > Hello Metron'ers -
> >> > > >
> >> > > > I would like to make the case that it is time for us to cut the
> next
> >> > > Apache
> >> > > > Metron release.
> >> > > >
> >> > > >- Our last release was 0.7.1 on May 15th
> >> > > ><
> >> > > >
> >> > >
> >> >
> >>
> https://lists.apache.org/thread.html/e2e532cbb63be757d0875718b082c069a268f57a9087510f196be09b%40%3Cdev.metron.apache.org%3E
> >> > > > >.
> >> > > >It has been *~6 months* since this release.
> >> > > >
> >> > > >
> >> > > >- We have *102 changes* in master since the last release. This
> >> > figure
> >> > > >excludes the two feature branches currently undergoing active
> >> > > > development.
> >> > > >
> >> > > >
> >> > > >- We should cut a release *prior to merging in any other
> >> significant
> >> > > >changes* from either feature branch.  The two active feature
> >> > branches
> >> > > >include ~47 other changes at this point in time.
> >> > > >
> >> > > >
> >> > > >- These 102 changes include some very nice *bug fixes and
> >> usability
> >> > > >improvements*. I would propose that we treat this as a bug-fix
> >> > release
> >> > > >and label it as *Metron 0.7.2*.
> >> > > >
> >> > > > Please let me know if you agree or disagree with this call for a
> >> > release.
> >> > > >
> >> > > > For those interested, here are the 102 unreleased changes in
> master.
> >> > > >
> >> > > > METRON-2323 Increase unit test coverage for Alerts List (sardell)
> >> > closes
> >> > > > apache/metron#1567
> >> > > > METRON-2208 [UI] Increase unit test coverage for Alert Details
> >> > (sardell)
> >> > > > closes apache/metron#1479
> >> > > > METRON-2316 [UI] Drag drop sorting for the selected fields in the
> >> > Alerts
> >> > > UI
> >> > > > (ruffle1986 via sardell) closes apache/metron#1560
> >> > > > METRON-2326 Unable to Call ENRICHMENT_GET from Threat Triage Rule
> >> > Reason
> >> > > > Field (nickwallen via mmiklavc) closes apache/metron#1570
> >> > > > METRON-2285 Batch Profiler Cannot Persist Data Sketches
> (nickwallen
> >> via
> >> > > > mmiklavc) closes apache/metron#1564
> >> > > > METRON-2321 Remove Legacy AWS Deployment Path (nickwallen) closes
> >> > > > apache/metron#1565
> >> > > > METRON-2317 [UI] Delete confirmation 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Justin Leet]

https://github.com/apache/metron/pull/1568 and
https://github.com/apache/metron/pull/1554 are in master now.

On Fri, Dec 6, 2019 at 7:16 PM Justin Leet  wrote:

> I'd like to throw https://github.com/apache/metron/pull/1552 on the pile.
> Per https://issues.apache.org/jira/browse/LEGAL-491, we should just note
> the contribution comes from dependabot. Would someone more familiar with
> the implications of upgrading that be able to review it, or give some
> advice on what we should be looking for in the review?
>
> On Thu, Dec 5, 2019 at 12:06 PM Shane Ardell 
> wrote:
>
>> Speaking on the UI-related PRs that Justin mentioned, I also would like to
>> see both of them merged before a release. At the moment, #1527 does not
>> address a few "stale data state" message inconsistencies that become
>> apparent as a result of that PR's work (you can read more about it in the
>> PR comments). That said, I think those inconsistencies can be tracked and
>> addressed separately from the current PR.
>>
>> On Thu, Dec 5, 2019 at 11:51 AM Michael Miklavcic <
>> michael.miklav...@gmail.com> wrote:
>>
>> > I think the junit upgrade should go in also. I'm almost finished
>> reviewing
>> > that.
>> >
>> > On Thu, Dec 5, 2019, 8:50 AM Justin Leet  wrote:
>> >
>> > >  If we're going to do a bug fix release, I'd like to see some of the
>> low
>> > > hanging fix PRs get finished and merged prior to the release. We've
>> been
>> > > lax about getting them cleaned up, so I'd like to use a release as an
>> > > opportunity to whittle the PRs down and put out a really solid
>> release.
>> > >
>> > > https://github.com/apache/metron/pull/1568 should be in before
>> release.
>> > It
>> > > addresses an issue with our validation of dependencies_with_url.csv
>> and
>> > > it's validation.
>> > > Should https://github.com/apache/metron/pull/1282 be in? Seems like
>> that
>> > > should have been merged awhile ago.
>> > >
>> > > There's also a couple UI performance / bug fixes PRs (e.g.
>> > > https://github.com/apache/metron/pull/1533 and
>> > > https://github.com/apache/metron/pull/1527) that have been sitting
>> > awhile.
>> > >
>> > >
>> > >
>> > > On Thu, Dec 5, 2019 at 10:32 AM Nick Allen 
>> wrote:
>> > >
>> > > > Hello Metron'ers -
>> > > >
>> > > > I would like to make the case that it is time for us to cut the next
>> > > Apache
>> > > > Metron release.
>> > > >
>> > > >- Our last release was 0.7.1 on May 15th
>> > > ><
>> > > >
>> > >
>> >
>> https://lists.apache.org/thread.html/e2e532cbb63be757d0875718b082c069a268f57a9087510f196be09b%40%3Cdev.metron.apache.org%3E
>> > > > >.
>> > > >It has been *~6 months* since this release.
>> > > >
>> > > >
>> > > >- We have *102 changes* in master since the last release. This
>> > figure
>> > > >excludes the two feature branches currently undergoing active
>> > > > development.
>> > > >
>> > > >
>> > > >- We should cut a release *prior to merging in any other
>> significant
>> > > >changes* from either feature branch.  The two active feature
>> > branches
>> > > >include ~47 other changes at this point in time.
>> > > >
>> > > >
>> > > >- These 102 changes include some very nice *bug fixes and
>> usability
>> > > >improvements*. I would propose that we treat this as a bug-fix
>> > release
>> > > >and label it as *Metron 0.7.2*.
>> > > >
>> > > > Please let me know if you agree or disagree with this call for a
>> > release.
>> > > >
>> > > > For those interested, here are the 102 unreleased changes in master.
>> > > >
>> > > > METRON-2323 Increase unit test coverage for Alerts List (sardell)
>> > closes
>> > > > apache/metron#1567
>> > > > METRON-2208 [UI] Increase unit test coverage for Alert Details
>> > (sardell)
>> > > > closes apache/metron#1479
>> > > > METRON-2316 [UI] Drag drop sorting for the selected fields in the
>> > Alerts
>> > > UI
>> > > > (ruffle1986 via sardell) closes apache/metron#1560
>> > > > METRON-2326 Unable to Call ENRICHMENT_GET from Threat Triage Rule
>> > Reason
>> > > > Field (nickwallen via mmiklavc) closes apache/metron#1570
>> > > > METRON-2285 Batch Profiler Cannot Persist Data Sketches (nickwallen
>> via
>> > > > mmiklavc) closes apache/metron#1564
>> > > > METRON-2321 Remove Legacy AWS Deployment Path (nickwallen) closes
>> > > > apache/metron#1565
>> > > > METRON-2317 [UI] Delete confirmation dialogue looks visually broken
>> > > (tiborm
>> > > > via sardell) closes apache/metron#1562
>> > > > METRON-2304 Update node and npm version to LTS releases (sardell)
>> > closes
>> > > > apache/metron#1550
>> > > > METRON-2311 Remove JUnit from all our uber jars (justinleet) closes
>> > > > apache/metron#1561
>> > > > METRON-2239 Metron Automated backup and restore (mmiklavc) closes
>> > > > apache/metron#1546
>> > > > METRON-2308 Fix 'Degrees' Example Profile (nickwallen) closes
>> > > > apache/metron#1555
>> > > > METRON-2310 Remove metron-integration-test from compile dependencies
>> > > > (justinleet) closes 

Re: [DISCUSS] Next Release - Life After 0.7.1

[Michael Miklavcic]

I think the junit upgrade should go in also. I'm almost finished reviewing
that.

On Thu, Dec 5, 2019, 8:50 AM Justin Leet  wrote:

>  If we're going to do a bug fix release, I'd like to see some of the low
> hanging fix PRs get finished and merged prior to the release. We've been
> lax about getting them cleaned up, so I'd like to use a release as an
> opportunity to whittle the PRs down and put out a really solid release.
>
> https://github.com/apache/metron/pull/1568 should be in before release. It
> addresses an issue with our validation of dependencies_with_url.csv and
> it's validation.
> Should https://github.com/apache/metron/pull/1282 be in? Seems like that
> should have been merged awhile ago.
>
> There's also a couple UI performance / bug fixes PRs (e.g.
> https://github.com/apache/metron/pull/1533 and
> https://github.com/apache/metron/pull/1527) that have been sitting awhile.
>
>
>
> On Thu, Dec 5, 2019 at 10:32 AM Nick Allen  wrote:
>
> > Hello Metron'ers -
> >
> > I would like to make the case that it is time for us to cut the next
> Apache
> > Metron release.
> >
> >- Our last release was 0.7.1 on May 15th
> ><
> >
> https://lists.apache.org/thread.html/e2e532cbb63be757d0875718b082c069a268f57a9087510f196be09b%40%3Cdev.metron.apache.org%3E
> > >.
> >It has been *~6 months* since this release.
> >
> >
> >- We have *102 changes* in master since the last release. This figure
> >excludes the two feature branches currently undergoing active
> > development.
> >
> >
> >- We should cut a release *prior to merging in any other significant
> >changes* from either feature branch.  The two active feature branches
> >include ~47 other changes at this point in time.
> >
> >
> >- These 102 changes include some very nice *bug fixes and usability
> >improvements*. I would propose that we treat this as a bug-fix release
> >and label it as *Metron 0.7.2*.
> >
> > Please let me know if you agree or disagree with this call for a release.
> >
> > For those interested, here are the 102 unreleased changes in master.
> >
> > METRON-2323 Increase unit test coverage for Alerts List (sardell) closes
> > apache/metron#1567
> > METRON-2208 [UI] Increase unit test coverage for Alert Details (sardell)
> > closes apache/metron#1479
> > METRON-2316 [UI] Drag drop sorting for the selected fields in the Alerts
> UI
> > (ruffle1986 via sardell) closes apache/metron#1560
> > METRON-2326 Unable to Call ENRICHMENT_GET from Threat Triage Rule Reason
> > Field (nickwallen via mmiklavc) closes apache/metron#1570
> > METRON-2285 Batch Profiler Cannot Persist Data Sketches (nickwallen via
> > mmiklavc) closes apache/metron#1564
> > METRON-2321 Remove Legacy AWS Deployment Path (nickwallen) closes
> > apache/metron#1565
> > METRON-2317 [UI] Delete confirmation dialogue looks visually broken
> (tiborm
> > via sardell) closes apache/metron#1562
> > METRON-2304 Update node and npm version to LTS releases (sardell) closes
> > apache/metron#1550
> > METRON-2311 Remove JUnit from all our uber jars (justinleet) closes
> > apache/metron#1561
> > METRON-2239 Metron Automated backup and restore (mmiklavc) closes
> > apache/metron#1546
> > METRON-2308 Fix 'Degrees' Example Profile (nickwallen) closes
> > apache/metron#1555
> > METRON-2310 Remove metron-integration-test from compile dependencies
> > (justinleet) closes apache/metron#1557
> > METRON-2284 Metron Profiler for Spark Doesn't Work as Expected
> (nickwallen)
> > closes apache/metron#1556
> > METRON-2290 [UI] Delaying first auto polling request on app start (tiborm
> > via sardell) closes apache/metron#1534
> > METRON-2293 Fix some inaccuracies in the MaaS README (mmiklavc) closes
> > apache/metron#1536
> > METRON-2302 [UI] Change the default polling interval for Alerts UI to
> > longer time (tiborm via sardell) closes apache/metron#1547
> > METRON-2295 [UI] Displaying No Data message in the Alerts UI
> > screen (subhashjha35 via sardell) closes apache/metron#1543
> > METRON-2294 [UI] Fixing Stale mode issue in Alert UI Manual Query Mode
> > (subhashjha35 via sardell) closes apache/metron#1540
> > METRON-2291 [UI] Fixing and rephrasing warning messages on Alerts UI
> > (tiborm via sardell) closes apache/metron#1535
> > METRON-2303 Change Default HDFS Port for Batch Profiler (nickwallen)
> closes
> > apache/metron#1548
> > METRON-2300 Fix Brad Kolarov's Apache ID (billierinaldi via mmiklavc)
> > closes apache/metron#1541
> > METRON-2280 PCAP queries no longer work (mmiklavc) closes
> > apache/metron#1537
> > METRON-2259 [UI] Hide Resolved and Hide Dismissed toggles not works when
> > filtering is in manual mode (tiborm via sardell) closes
> apache/metron#1532
> > METRON-2278 Metron on CentOS 6 Documentation is outdated
> > (subhashjha35 via sardell) closes apache/metron#1530
> > METRON-2274 Flatfile loader and summarizer mapreduce mode broken
> (mmiklavc)
> > closes apache/metron#1525
> > METRON-2272 [UI] Performance: Switching manual filtering 

[DISCUSS] Next Release - Life After 0.7.1

[Nick Allen]

Hello Metron'ers -

I would like to make the case that it is time for us to cut the next Apache
Metron release.

   - Our last release was 0.7.1 on May 15th
   
.
   It has been *~6 months* since this release.


   - We have *102 changes* in master since the last release. This figure
   excludes the two feature branches currently undergoing active development.


   - We should cut a release *prior to merging in any other significant
   changes* from either feature branch.  The two active feature branches
   include ~47 other changes at this point in time.


   - These 102 changes include some very nice *bug fixes and usability
   improvements*. I would propose that we treat this as a bug-fix release
   and label it as *Metron 0.7.2*.

Please let me know if you agree or disagree with this call for a release.

For those interested, here are the 102 unreleased changes in master.

METRON-2323 Increase unit test coverage for Alerts List (sardell) closes
apache/metron#1567
METRON-2208 [UI] Increase unit test coverage for Alert Details (sardell)
closes apache/metron#1479
METRON-2316 [UI] Drag drop sorting for the selected fields in the Alerts UI
(ruffle1986 via sardell) closes apache/metron#1560
METRON-2326 Unable to Call ENRICHMENT_GET from Threat Triage Rule Reason
Field (nickwallen via mmiklavc) closes apache/metron#1570
METRON-2285 Batch Profiler Cannot Persist Data Sketches (nickwallen via
mmiklavc) closes apache/metron#1564
METRON-2321 Remove Legacy AWS Deployment Path (nickwallen) closes
apache/metron#1565
METRON-2317 [UI] Delete confirmation dialogue looks visually broken (tiborm
via sardell) closes apache/metron#1562
METRON-2304 Update node and npm version to LTS releases (sardell) closes
apache/metron#1550
METRON-2311 Remove JUnit from all our uber jars (justinleet) closes
apache/metron#1561
METRON-2239 Metron Automated backup and restore (mmiklavc) closes
apache/metron#1546
METRON-2308 Fix 'Degrees' Example Profile (nickwallen) closes
apache/metron#1555
METRON-2310 Remove metron-integration-test from compile dependencies
(justinleet) closes apache/metron#1557
METRON-2284 Metron Profiler for Spark Doesn't Work as Expected (nickwallen)
closes apache/metron#1556
METRON-2290 [UI] Delaying first auto polling request on app start (tiborm
via sardell) closes apache/metron#1534
METRON-2293 Fix some inaccuracies in the MaaS README (mmiklavc) closes
apache/metron#1536
METRON-2302 [UI] Change the default polling interval for Alerts UI to
longer time (tiborm via sardell) closes apache/metron#1547
METRON-2295 [UI] Displaying No Data message in the Alerts UI
screen (subhashjha35 via sardell) closes apache/metron#1543
METRON-2294 [UI] Fixing Stale mode issue in Alert UI Manual Query Mode
(subhashjha35 via sardell) closes apache/metron#1540
METRON-2291 [UI] Fixing and rephrasing warning messages on Alerts UI
(tiborm via sardell) closes apache/metron#1535
METRON-2303 Change Default HDFS Port for Batch Profiler (nickwallen) closes
apache/metron#1548
METRON-2300 Fix Brad Kolarov's Apache ID (billierinaldi via mmiklavc)
closes apache/metron#1541
METRON-2280 PCAP queries no longer work (mmiklavc) closes apache/metron#1537
METRON-2259 [UI] Hide Resolved and Hide Dismissed toggles not works when
filtering is in manual mode (tiborm via sardell) closes apache/metron#1532
METRON-2278 Metron on CentOS 6 Documentation is outdated
(subhashjha35 via sardell) closes apache/metron#1530
METRON-2274 Flatfile loader and summarizer mapreduce mode broken (mmiklavc)
closes apache/metron#1525
METRON-2272 [UI] Performance: Switching manual filtering on and off
multiple times leads slow typing (ruffle1986 via sardell) closes
apache/metron#1524
METRON-2190 [UI] Alerts UI: Indicating loading and preventing parallel
requests (tiborm via sardell) closes apache/metron#1514
METRON-2271 Reorganize Travis Build (nickwallen) closes apache/metron#1522
METRON-2266 REST debug instructions (merrimanr via nickwallen) closes
apache/metron#1520
METRON-2235 Increase server startup timeout (tigerquoll via mmiklavc)
closes apache/metron#1496
METRON-2257 Metron-Alerts GUI testing failing on MacOS builds (sardell)
closes apache/metron#1513
METRON-2247 rpm-docker: Provide an option to bypass running rpmlint
(tigerquoll via nickwallen) closes apache/metron#1503
METRON-2254 Intermittent Test Failure in RestFunctionsIntegrationTest
(nickwallen) closes apache/metron#1510
METRON-2211 [UI] Alerts UI should optionally render timestamp in local time
(sardell) closes apache/metron#1495
METRON-2217 Migrate current HBase client from HTableInterface to Table
(mmiklavc) closes apache/metron#1483
METRON-2201 The description for the IS_IP method default behavior needs to
corrected as per implementation (MohanDV via mmiklavc) closes
apache/metron#1474
METRON-2227 Increase Kafka test harness timeout (tigerquoll via mmiklavc)
closes apache/metron#1493