Joe,

Nope, not a 1.6 blocker, just a nice to have.

On Mon, Mar 12, 2018 at 1:47 PM, Joe Witt <joe.w...@gmail.com> wrote:

> Mike, Michael,
>
> Both items noted seem fair for inclusion in whatever release vehicle
> follows them being merged but neither look like they'd impact release
> timing.  Please advise if I'm misreading either of those.
>
>
> Thanks
> Joe
>
> On Mon, Mar 12, 2018 at 5:42 PM, Michael Moser <moser...@gmail.com> wrote:
> > I would like to finish up NIFI-3599
> > <https://issues.apache.org/jira/browse/NIFI-3599>, which just needs some
> > contributer / review agreement.
> >
> > -- Another Mike
> >
> > On Mon, Mar 12, 2018 at 1:28 PM, Mike Thomsen <mikerthom...@gmail.com>
> > wrote:
> >
> >> If we could get this patch for HBase visibility labels merged before,
> I'd
> >> appreciate it.
> >>
> >> https://github.com/apache/nifi/pull/2518
> >>
> >> If anyone else has patches they'd like to see merged, feel to ping me on
> >> GitHub, and I'll help out with a code review.
> >>
> >> Thanks,
> >>
> >> Mike
> >>
> >> On Mon, Mar 12, 2018 at 12:56 PM, Joe Witt <joe.w...@gmail.com> wrote:
> >>
> >> > Team,
> >> >
> >> > Looks like a ton of great work already in JIRA making a nifi 1.6.0
> >> > release pretty easily justified.  Lots of nice bug fixes/improvements
> >> > and notable we relaxed the http header corruption restrictions which
> >> > fixed a potential security risk but also created operations
> >> > challenges.
> >> >
> >> > Any glaring things to hold up on?  Doing this soon doesn't preclude
> >> > doing another release soon but it feels like we need to get out a
> >> > release again.
> >> >
> >> > I'm happy to RM unless someone is really looking to do so.
> >> >
> >> > Thanks
> >> >
> >>
>

Reply via email to