I’m +1 on pulling the current RC and re-voting with at least the METRON-734 fix
included.
I’m 0 (zero, unsigned :-) on whether or not to roll to current HEAD. Normally
I wouldn’t do it, but the CEF parser is clearly a valuable addition.
Thanks,
--Matt
On 2/22/17, 8:43 AM, "Casey Stella" <ceste...@gmail.com> wrote:
I'm in favor of moving 0.3.1 RC5 concurrent with master. I see a number of
things there will make the release better:
- Better docs in the doc-book
- The CEF parser
Casey
On Wed, Feb 22, 2017 at 7:46 AM, Kyle Richardson <kylerichards...@gmail.com>
wrote:
> +1 on pulling and cutting a new RC. Would we simply patch rc4 with this
one
> change or include all of the master commits too?
>
> -Kyle
>
> On Wed, Feb 22, 2017 at 10:29 AM, Nick Allen <n...@nickallen.org> wrote:
>
> > +1 I agree with you Casey. I think we should re-cut the release.
> >
> > On Wed, Feb 22, 2017 at 10:27 AM, Casey Stella <ceste...@gmail.com>
> wrote:
> >
> > > As you are all aware by now, we have an issue with our maven build.
In
> > > short, we tripped on https://github.com/maxmind/GeoIP2-java/issues/77
> > >
> > > As such, our build no longer works, but also our RC for 0.3.1 no
longer
> > > builds. I am inclined to pull the release candidate from voting on
> > > incubator general and re-cut a new candidate after the fix METRON-734
(
> > > https://github.com/apache/incubator-metron/pull/462) gets in later
> > today.
> > > My reasoning is that the current situation makes the release candidate
> > > un-releasable due to it not being able to be build.
> > >
> > > I would like to bring that decision to the community and get some
> > feedback,
> > > though, before I summarily retract the candidate on incubator general.
> > >
> > > Thoughts?
> > >
> > > Best,
> > >
> > > Casey
> > >
> >
>
