At the end of yesterday, while testing the version increment, I found a couple of bugs with the Ambari mpack I think are pretty important.
https://issues.apache.org/jira/browse/METRON-563 https://issues.apache.org/jira/browse/METRON-564 METRON-564, has a current PR out (That's already +1'ed): https://github.com/apache/incubator-metron/pull/355 METRON-563 I am working on a fix for, and should have a PR out by EOD and hopefully sooner. It's also the one that more directly impacts usability of the mpack, because it forces a workaround for installing ES templates that requires shutting down and restarting the service. Justin On Fri, Nov 11, 2016 at 9:26 AM, Casey Stella <[email protected]> wrote: > That'd save me from doing it this afternoon, so absolutely. :) > > On Fri, Nov 11, 2016 at 9:26 AM, David Lyle <[email protected]> wrote: > > > I have a few minutes, do you want me to change the 0.2.2 release labels > to > > 0.3.0? > > > > -D... > > > > > > On Fri, Nov 11, 2016 at 9:23 AM, Casey Stella <[email protected]> > wrote: > > > > > Hi Everyone, > > > > > > Two weeks ago, I sent out an email asking for features for the release > > and > > > announcing that I got the JIRA mostly in order release-wise. Reviewing > > the > > > set of pending PRs > > > <https://issues.apache.org/jira/browse/METRON-490?jql= > > > project%20%3D%20METRON%20AND%20resolution%20%3D%20Unresolved%20AND% > > > 20fixVersion%20%3D%200.2.2BETA%20ORDER%20BY%20priority%20DESC>, > > > nothing in there seems to be a show-stopper now that METRON-533 has a > PR > > > for it. I am going to call it a release at the end of the day unless > > > someone speaks up with a critical issue. > > > > > >
