Re: [DISCUSS] Next Release

2019-04-25 Thread zeo...@gmail.com
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 <

Re: [DISCUSS] Next Release

2019-04-25 Thread Michael Miklavcic
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

Re: [DISCUSS] Next Release

2019-04-25 Thread Justin Leet
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

Re: [DISCUSS] Next Release

2019-04-25 Thread Nick Allen
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

2019-04-23 Thread Justin Leet
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

Re: [DISCUSS] Next Release

2019-04-23 Thread Nick Allen
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

Re: [DISCUSS] Next Release

2019-04-23 Thread zeo...@gmail.com
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

Re: [DISCUSS] Next Release

2019-04-23 Thread Justin Leet
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

Re: [DISCUSS] Next Release

2019-04-23 Thread Nick Allen
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 >

Re: [DISCUSS] Next Release

2019-04-17 Thread Michael Miklavcic
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

Re: [DISCUSS] Next Release

2019-04-17 Thread Nick Allen
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]

Re: [DISCUSS] Next Release

2019-04-17 Thread Nick Allen
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

Re: [DISCUSS] Next Release

2019-04-16 Thread Michael Miklavcic
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

2019-04-15 Thread Michael Miklavcic
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

Re: [DISCUSS] Next Release

2019-04-05 Thread Ryan Merriman
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? > >

Re: [DISCUSS] Next Release

2019-03-30 Thread zeo...@gmail.com
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

Re: [DISCUSS] Next Release

2019-03-28 Thread Michael Miklavcic
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

Re: [DISCUSS] Next Release

2019-03-28 Thread Nick Allen
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 > >

Re: [DISCUSS] Next Release

2019-03-14 Thread Michael Miklavcic
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

2019-03-14 Thread zeo...@gmail.com
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

Re: [DISCUSS] Next Release

2019-03-14 Thread Michael Miklavcic
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

2019-03-14 Thread Justin Leet
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

2019-03-13 Thread Michael Miklavcic
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

[DISCUSS] Next Release

2019-03-13 Thread Nick Allen
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

2017-04-20 Thread Justin Leet
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

Re: [DISCUSS] next release proposal

2017-04-20 Thread Otto Fowler
+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

Re: [DISCUSS] next release proposal

2017-04-20 Thread David Lyle
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

Re: [DISCUSS] next release proposal

2017-04-20 Thread Matt Foley
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