Re: [DISCUSS] Storm topology.classpath setting

topology.classpath is a topology level config, so Mike's potential alternative is to migrate that down from Ambari into the actual topologies we launch (assuming it works as expected). Basically we're trading ease of use in Ambari vs. additional setup for each topology that's run. I'm in favor

Re: [DISCUSS] Modify bylaws to allow speculative branches

I'd prefer to still keep "Review then Commit" but I'd be interested in lowering the review bar for it as long as the branch gets a solid final review before merge. I don't think a feature branch needs to be micromanaged, but people should still take a quick glance at the commits that come

Re: Reducing Warnings in Build

First off, I would absolutely love to see the warnings reduced and the quality of our code improved. I'm in favor of all four of the points, and I think it's a good start towards weeding out a lot of issues. So regarding question 1: That awkwardness comes about because org.simple.json is all

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

Re: Having difficulty setting up both QuickDev and FullDev

issue, would it make sense to undo it? > > -D... > > > On Thu, Apr 20, 2017 at 1:26 PM, Justin Leet <justinjl...@gmail.com> > wrote: > > > Our instructions on building the RPMs are slightly out of date. The pom > > for metron-deployment changed slight

<    1   2   3