Re: [DISCUSS] Next Release - Life After 0.7.1

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

Re: [DISCUSS] Next Release - Life After 0.7.1

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 righ

Re: [DISCUSS] Next Release - Life After 0.7.1

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 opin

Re: [DISCUSS] Next Release - Life After 0.7.1

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 h

Re: [DISCUSS] Next Release - Life After 0.7.1

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: >

Re: [DISCUSS] Next Release - Life After 0.7.1

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

Re: [DISCUSS] Next Release - Life After 0.7.1

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 n

Re: [DISCUSS] Next Release - Life After 0.7.1

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

Re: [DISCUSS] Next Release - Life After 0.7.1

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/p

Re: [DISCUSS] Next Release - Life After 0.7.1

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 w

Re: [DISCUSS] Next Release - Life After 0.7.1

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 no

Re: [DISCUSS] Next Release - Life After 0.7.1

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 an

Re: [DISCUSS] Next Release - Life After 0.7.1

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 sho

Re: [DISCUSS] Next Release - Life After 0.7.1

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

Re: [DISCUSS] Next Release - Life After 0.7.1

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 commen

Re: [DISCUSS] Next Release - Life After 0.7.1

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 getti

Re: [DISCUSS] Next Release - Life After 0.7.1

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://gi

[DISCUSS] Next Release - Life After 0.7.1

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 b

Re: [DISCUSS] Next Release

Any chance we could do a quick cleanup of METRON-1795? Seems like it should be assigned to Jagdeep Singh (jagdeep.sing...@team.telstra.com), but I couldn't find that account in the assignee field. - Jon Zeolla zeo...@gmail.com On Thu, Apr 25, 2019 at 12:33 PM Michael Miklavcic < michael.miklav.

Re: [DISCUSS] Next Release

Just a heads up, we'll also want this PR in for the release because without it fulldev won't build. https://github.com/apache/metron/pull/1391. It's got a +1 from me and should be merged shortly. On Thu, Apr 25, 2019 at 6:53 AM Justin Leet wrote: > Great, thanks Nick! > > I'll work on cutting th

Re: [DISCUSS] Next Release

Great, thanks Nick! I'll work on cutting the release candidate later today. That'll probably happen in the afternoon (EDT), and I'll let everyone know here and in the Slack room when it's available. On Thu, Apr 25, 2019 at 8:41 AM Nick Allen wrote: > Justin - I cleaned up the last bit of stragg

Re: [DISCUSS] Next Release

Justin - I cleaned up the last bit of stragglers in JIRA. JIRA should be ready for the release. $ /dev-utilities/release-utils/validate-jira-for-release --version=0.7.1 --start=tags/apache-metron_0.7.0-release ... JIRA STATUS FIX VERSION ASSIGNEE

Re: [DISCUSS] Next Release

Thanks Nick! I've updated all the "Next + 1" tickets to "0.7.1", and cleaned up the unassigned tickets (and possibly my own). Everyone else should have emails outlining what to update at this point. On Tue, Apr 23, 2019 at 3:54 PM Nick Allen wrote: > I was able to create the "0.7.1" release ve

Re: [DISCUSS] Next Release

I was able to create the "0.7.1" release version in JIRA. On Tue, Apr 23, 2019 at 1:41 PM Justin Leet wrote: > Absolutely. It'll probably be tomorrow before that gets into full swing. > > I don't believe we have a "0.7.1" release in Jira, and I (oddly enough) > don't believe I have permissions t

Re: [DISCUSS] Next Release

On a related note, I would love to get 0.2 and 0.3 versions for metron-bro-plugin-kafka so we can clean up the JIRAs. Currently the metron-bro-plugin-kafka plugin uses major.minor versioning but once zeek 3.0 is released we plan to align with the metron project and do major.minor.patch versioning.

Re: [DISCUSS] Next Release

Absolutely. It'll probably be tomorrow before that gets into full swing. I don't believe we have a "0.7.1" release in Jira, and I (oddly enough) don't believe I have permissions to create it. We'll need someone to get that created (James, maybe?). Until then, I'd like to ask everyone to make sur

Re: [DISCUSS] Next Release

Justin - Can you kick-off the release process? On Wed, Apr 17, 2019 at 11:51 AM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > I don't think it should hold up the release. It's *extremely* rare, even > though it's come up twice. I wanted to be preemptive about bringing up the > intermi

Re: [DISCUSS] Next Release

I don't think it should hold up the release. It's *extremely* rare, even though it's come up twice. I wanted to be preemptive about bringing up the intermittent failure list because we agreed as a community on this being a regular release cycle review step. I think all those voting on the release s

Re: [DISCUSS] Next Release

Oh, and that failure from 21 days ago was caused by a downstream issue brought in by PR #1364, that we then later reverted [1]. So at least that particular issue has been identified and addressed and should no longer impacts builds. --- [1] https://github.com/apache/metron/commit/cad679a5948ce0ee

Re: [DISCUSS] Next Release

Are you suggesting the release should wait on this? Personally, I don't feel that we have any *persistently intermittent* test failures that would block a release. The last build failure on master I see was from 21 days ago. Otherwise, I'd really like to kick off the next release. On Tue, Apr 1

Re: [DISCUSS] Next Release

FYI, I just saw one of our reported intermittent test failures pop up again today - https://issues.apache.org/jira/browse/METRON-1814 On Mon, Apr 15, 2019 at 2:22 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > I want to thread the needle on this. I just reviewed a PR from Ryan that

Re: [DISCUSS] Next Release

I want to thread the needle on this. I just reviewed a PR from Ryan that addresses this and gave it a +1. https://github.com/apache/metron/pull/1381 I think Jon Zeolla and Justin Leet should have an opportunity to chime in as they also had commented about this request in the original PR. One othe

Re: [DISCUSS] Next Release

Jon is correct. I am actively working on this and hope to have it completed soon. I realize it will hold up the release so it's a priority for me. On Sat, Mar 30, 2019 at 6:09 PM zeo...@gmail.com wrote: > Isn't the documentation already in progress? > > https://github.com/apache/metron/pull/

Re: [DISCUSS] Next Release

Isn't the documentation already in progress? https://github.com/apache/metron/pull/1330#issuecomment-466453372 If not I would still consider it important to complete prior to a release and I agree with Justin's comments in https://lists.apache.org/thread.html/50b89b919bd8bef3f7fcdef167cbd7e489fa

Re: [DISCUSS] Next Release

Jon and Ryan - this was a convo/negotiation between you two at the time. Any thoughts? On Thu, Mar 28, 2019 at 9:08 AM Nick Allen wrote: > Is anyone volunteering to take this on? Would be nice to get a release > out. > > On Thu, Mar 14, 2019, 4:53 PM zeo...@gmail.com wrote: > > > We should lik

Re: [DISCUSS] Next Release

Is anyone volunteering to take this on? Would be nice to get a release out. On Thu, Mar 14, 2019, 4:53 PM zeo...@gmail.com wrote: > We should likely get METRON-2014 in, based on > > https://lists.apache.org/thread.html/13bd0ed5606ad4f3427f24a8e759d6bcb61ace76d4afcc9f48310a00@%3Cdev.metron.apach

Re: [DISCUSS] Next Release

Good catch On Thu, Mar 14, 2019 at 2:53 PM zeo...@gmail.com wrote: > We should likely get METRON-2014 in, based on > > https://lists.apache.org/thread.html/13bd0ed5606ad4f3427f24a8e759d6bcb61ace76d4afcc9f48310a00@%3Cdev.metron.apache.org%3E > > On Thu, Mar 14, 2019 at 4:24 PM Michael Miklavcic <

Re: [DISCUSS] Next Release

We should likely get METRON-2014 in, based on https://lists.apache.org/thread.html/13bd0ed5606ad4f3427f24a8e759d6bcb61ace76d4afcc9f48310a00@%3Cdev.metron.apache.org%3E On Thu, Mar 14, 2019 at 4:24 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > Ticket is now done and merged. I'm also

Re: [DISCUSS] Next Release

Ticket is now done and merged. I'm also good on 0.7.1. On Thu, Mar 14, 2019 at 2:18 PM Justin Leet wrote: > I'm in favor doing a release, pending the ticket Mike pointed out (and > anything else someone comes up with). > > To the best of my knowledge, I think 0.7.1 is sufficient, but if someone

Re: [DISCUSS] Next Release

I'm in favor doing a release, pending the ticket Mike pointed out (and anything else someone comes up with). To the best of my knowledge, I think 0.7.1 is sufficient, but if someone comes up with something, it's not hard to pivot. On Wed, Mar 13, 2019, 13:08 Michael Miklavcic wrote: > I'd like

Re: [DISCUSS] Next Release

I'd like to see this fixed for the next release. https://issues.apache.org/jira/browse/METRON-2036. Even though it's a non-prod issue, this is a core part of our infrastructure/development lifecycle that is currently broken and fits with our previous agreements of holding a release until all interm

[DISCUSS] Next Release

I would like to open a discussion in regards to the next release. Our last 0.7.0 release was on Dec 11th. I believe we have a significant number of bug fixes and performance improvements that would make a worthy point release; 0.7.1. Although, we should review the change log and see if there are

Re: [DISCUSS] next release proposal

METRON-799 is in master. I know at least METRON-859 now has a conflict on Kerberos-setup.md, so if anyone has anything similar, please make sure to update your branch. On Thu, Apr 20, 2017 at 9:25 AM, Otto Fowler wrote: > Maybe in the next release we should have theme labels for the release in

Re: [DISCUSS] next release proposal

Maybe in the next release we should have theme labels for the release in jira On April 20, 2017 at 09:24:14, Casey Stella (ceste...@gmail.com) wrote: +1, I agree. We should see this through. I will point out also that while not strictly required, METRON-861 ( https://github.com/apache/incubator-

Re: [DISCUSS] next release proposal

+1, I agree. We should see this through. I will point out also that while not strictly required, METRON-861 ( https://github.com/apache/incubator-metron/pull/534) would be required to use the CLI utilities if people are planning on setting acl's on the znodes for our config in their installation

Re: [DISCUSS] next release proposal

+1 on the proposed changes. I think that it is important that if it is in reach, we ‘complete’ any major theme of the release. In this case kerberos. I think that given where pycapa and rest are, we should make the effort to get them in. On April 20, 2017 at 08:52:11, Ryan Merriman (merrim...@

Re: [DISCUSS] next release proposal

Dave is correct on the status of METRON-799. It's been spun up on EC2. In addition to general review, if reviewers could take a glance at Kerberos-setup.md and make sure I haven't made any mistakes, I would appreciate it. The main thing is splitting it up a bit so that Ambari and Manual setup in

Re: [DISCUSS] next release proposal

Jon, I've already started reviewing the pycapa PR but a second pair of eyes never hurts. On Thu, Apr 20, 2017 at 6:15 AM, zeo...@gmail.com wrote: > At a high level this looks good to me. I'm going to try and pick out a PR > that needs some testing and hit it today (pycapa?). I found an issue

Re: [DISCUSS] next release proposal

Matt, I started a discussion around Kerberos support as a prerequisite for MPack work and the consensus was that a service should support Kerberos before it's included in the MPack. There is a PR out there for Kerberos support for REST (https://github.com/apache/incubator-metron/pull/535) but it

Re: [DISCUSS] next release proposal

At a high level this looks good to me. I'm going to try and pick out a PR that needs some testing and hit it today (pycapa?). I found an issue in master yesterday but I don't think it's in the release breach - I'll try to confirm that that and file the prior JIRA(s). Jon On Thu, Apr 20, 2017, 7

Re: [DISCUSS] next release proposal

Hi Matt, +1 on the fixes you selected for inclusion. Check with Justin to be sure, but I believe METRON-799 is ready for review, so pending that, it's ready to go. -D... On Thu, Apr 20, 2017 at 2:13 AM, Matt Foley wrote: > Hi all, > I’ve put together RC1 for the 0.4.0 release of Metron, along

Re: [DISCUSS] next release proposal

Hi all, I’ve put together RC1 for the 0.4.0 release of Metron, along with its book-site. It is available for your review at https://dist.apache.org/repos/dist/dev/incubator/metron/0.4.0-RC1-incubating/ I’m not putting it to VOTE yet, because I think some additional fixes are proba