Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

Good, I’ll build the RC tonight. Thanks Jon. --Matt From: "zeo...@gmail.com" <zeo...@gmail.com> Date: Thursday, December 7, 2017 at 12:27 PM To: Matt Foley <mfo...@hortonworks.com> Subject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro' Otto, your un

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

s it convenient for you to do so today? >> >> >> >> Thanks, >> >> --Matt >> >> >> >> From: Nick Allen <n...@nickallen.org> >> Date: Thursday, December 7, 2017 at 10:13 AM >> To: "dev@metron.apache.org" <dev@met

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

>> >> --Matt >> >> >> >> From: Nick Allen <n...@nickallen.org> >> Date: Thursday, December 7, 2017 at 10:13 AM >> To: "dev@metron.apache.org" <dev@metron.apache.org> >> Cc: Matt Foley <ma

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

> Thanks, >> >> --Matt >> >> >> >> From: Nick Allen <n...@nickallen.org> >> Date: Thursday, December 7, 2017 at 10:13 AM >> To: "dev@metron.apache.org" <dev@metron.apache.org> >> Cc: Matt Foley <ma...@apache.org&g

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

2017 at 10:13 AM > To: "dev@metron.apache.org" <dev@metron.apache.org> > Cc: Matt Foley <ma...@apache.org> > Subject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro' > > > > I am more interested in getting a release cut. If me mov

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

and > > > > > > - document as much as we think appropriate regarding what it is, > how > > to > > > build it, and how to update it, > > > > > > and commit that before the 0.4.2 release. > > > > > > > > > > > >

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

that before the 0.4.2 release. > > > > > > > > What is the will of the community? > > > > Thanks, > > > > --Matt > > > > > > > > From: Nick Allen <n...@nickallen.org> > > Reply-To: "dev@metron.apache.org&

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

...@nickallen.org> > Reply-To: "dev@metron.apache.org" <dev@metron.apache.org> > Date: Tuesday, November 28, 2017 at 9:09 AM > To: "dev@metron.apache.org" <dev@metron.apache.org> > Subject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Pl

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

of the community? Thanks, --Matt From: Nick Allen <n...@nickallen.org> Reply-To: "dev@metron.apache.org" <dev@metron.apache.org> Date: Tuesday, November 28, 2017 at 9:09 AM To: "dev@metron.apache.org" <dev@metron.apache.org>

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

: Nick Allen <n...@nickallen.org> Reply-To: "dev@metron.apache.org" <dev@metron.apache.org> Date: Tuesday, November 28, 2017 at 9:09 AM To: "dev@metron.apache.org" <dev@metron.apache.org> Subject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

ubject: Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro' I'll add a bit to Jon's technical comments. * We only created a separate repo because it was a technical requirement to leverage the bro-pkg mechanism. * Leveraging the new bro-pkg mechanism has many advantages as ou

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

I'll add a bit to Jon's technical comments. * We only created a separate repo because it was a technical requirement to leverage the bro-pkg mechanism. * Leveraging the new bro-pkg mechanism has many advantages as outlined by Jon. * Enabling the bro-pkg mechanism is backwards compatible. I can

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

In an attempt to keep this from becoming unbearably long, I will try to keep my responses short, but I would be happy to elaborate. That's a fairly good timeline and summary, but here are some clarifications in corresponding order: - The plugin history is quite short and you can probably get a

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

I am not sure that our use of the plugin necessarily equates to it being implicitly coupled to Metron. It seems like the Right Thing To Do™, esp. for an Apache project would be to make this available for use by the greater bro community. Unless we expect to do extensive iterative work on the

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

[Please pardon me that the below is a little labored. I’m trying to understand the implications for both release and use, which requires some explanation as well as the two questions needed. Q1 and Q2 below are probably the same question, asked in slightly different contexts. Please consider

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

The reason we decided to do that was because it is the best way for it to be used (and thus improved on and quality tested) by the broader bro community. If it's any indication of it's popularity, there was just an email on the bro mailing list about the plugin a few days ago, and I've already

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

I agree with Nick. Since the plugin is tightly coupled with Metron why not just pull it into the main repo and version it with the rest of the code? Do we really need the second repo for the plug-in? Thanks, James 16.11.2017, 08:06, "Nick Allen" : >>  I would suggest

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

I propose that we coordinate the review of METRON-1329 and METRON-1313 , then merge METRON-1329, pursue a 0.1 release for apache/metron-bro-plugin-kafka, and then finalize METRON-1313

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

There’s two issues, I think: (1) We’d like to be able to version and evolve the main body of Metron and the metron-bro-plugin-kafka separately. (2) We want to be able to assure that each release of Metron has a known-working version of metron-bro-plugin-kafka At a very simple level, we can

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

I expect a few version changes up front to add some new features to the package (0.1 for the initial release, 0.{2..n} for some new features, 1.0 when we stabilize) but after that it will probably only be updated to follow kafka/librdkafka updates. Jon On Thu, Nov 16, 2017 at 10:10 AM Otto

Re: [MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

How often to we expect to change this? If it is effectively pinned then a release process is not that bad. On November 16, 2017 at 10:06:53, Nick Allen (n...@nickallen.org) wrote: > > I would suggest that we institute a release procedure for the package > itself, but I don't think it

[MENTORS][DISCUSS] Release Procedure + 'Kafka Plugin for Bro'

+ Restarting the thread to include mentors. The code of the 'Kafka Plugin for Bro' is now maintained in the external repository that we set up a while back. - Metron Core: git://git.apache.org/metron.git - Kafka Plugin for Bro: git://git.apache.org/metron-bro-plugin-kafka.git (Q) Do we