+1 on RC5 from master/HEAD On Wed, Feb 22, 2017 at 10:16 AM, Nick Allen <n...@nickallen.org> wrote:
> +1 on re-cutting RC5 from head. We're going to have to go through the > same level of effort either way. Might as well get more value out of it. > > > On Wed, Feb 22, 2017 at 11: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 > > > > > > > > > > > > > > >
