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] Upgrade to HDP 3.1.0

2019-04-23 Thread Nick Allen
FYI - I opened a ticket to serve as an epic for this work and the feature branch. https://issues.apache.org/jira/browse/METRON-2088 On Mon, Apr 22, 2019 at 3:32 PM Michael Miklavcic < michael.miklav...@gmail.com> wrote: > +1 to starting a feature branch for this. > +1 to removing our custom

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 >