nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff <jtsw...@gmail.com>
Subject Re: [discuss] approaching a NiFi 1.10.0 release
Date Fri, 30 Aug 2019 06:21:09 GMT
I'd also like to get the PR [1] for NIFI-6275 merged before 1.10.0 is
released.  It's an update to ListHDFS so that the scheme and authority are
ignored when using the "Full Path" filter mode.

[1] https://github.com/apache/nifi/pull/3483

On Thu, Aug 29, 2019 at 10:04 PM Aldrin Piri <aldrinpiri@gmail.com> wrote:

> I created NIFI-6604 [1] to reduce assembly size and listed it as a Blocker
> for this release.  The issue has a link to the associated discussion thread
> and an initial PR.
>
> --aldrin
>
> [1] https://issues.apache.org/jira/browse/NIFI-6604
>
> On Thu, Aug 29, 2019 at 4:08 PM Matt Burgess <mattyb149@gmail.com> wrote:
>
> > Mike,
> >
> > I’ll review those two graph PRs tonight or tomorrow (if they’re still
> open
> > by then)
> >
> > > On Aug 29, 2019, at 3:43 PM, Mike Thomsen <mikerthomsen@gmail.com>
> > wrote:
> > >
> > > I have two open graph-related PR's that are really small and are needed
> > to
> > > close some bugs that will be bad for early adopters:
> > >
> > > https://github.com/apache/nifi/pull/3571
> > > https://github.com/apache/nifi/pull/3572
> > >
> > > If someone wants to review, that'd be great. Otherwise, I can merge
> them
> > in
> > > because I'm doing daily work on some graph stuff using a branch based
> on
> > > both patches.
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > >> On Thu, Aug 29, 2019 at 2:12 PM Joe Witt <joe.witt@gmail.com> wrote:
> > >>
> > >> We had another discuss on that recently and the intent is to drop a
> few
> > >> toys off the raft and update migration guidance.
> > >>
> > >> Thanks
> > >>
> > >>> On Thu, Aug 29, 2019 at 2:02 PM Jeremy Dyer <jdye64@gmail.com>
> wrote:
> > >>>
> > >>> +1 looking forward to this.
> > >>>
> > >>> I recall seeing some issues about Apache Infra and the binary size.
> > Were
> > >>> all of those appropriate modules removed as discussed and the build
> > size
> > >>> will be small enough now?
> > >>>
> > >>>> On Thu, Aug 29, 2019 at 1:35 PM Bryan Bende <bbende@gmail.com>
> wrote:
> > >>>>
> > >>>> +1 Looking forward to getting parameters and Java 11 support out
> there
> > >>>> in a release.
> > >>>>
> > >>>>> On Thu, Aug 29, 2019 at 1:02 PM Joe Witt <joewitt@apache.org>
> wrote:
> > >>>>>
> > >>>>> Team,
> > >>>>>
> > >>>>> It looks like we're reaching a point in which it is time to
close
> in
> > >> on
> > >>>>> 1.10.
> > >>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> >
> https://issues.apache.org/jira/browse/NIFI-6595?jql=project%20%3D%20NIFI%20AND%20fixVersion%20%3D%201.10.0
> > >>>>>
> > >>>>> There are 250+ issues in there nearly 240 of which are already
> > >>>> resolved.  I
> > >>>>> haven't gone through yet for fully analyzing but the awesome
Java
> 11
> > >>> work
> > >>>>> Jeff Storck and others has done means we can now build on Java
11
> as
> > >>> well
> > >>>>> as run on it.  There is a ton of great work on parameters which
> will
> > >>> make
> > >>>>> managing flows at scale much easier.  We will need to drop
some
> nars
> > >>>> which
> > >>>>> means we have some migration guidance to update.
> > >>>>>
> > >>>>> I'd like to volunteer as RM but if there are any other takers
> please
> > >>> let
> > >>>> me
> > >>>>> know.
> > >>>>>
> > >>>>> As we close in on releases this tends to create a lot of urgency
to
> > >>>> quickly
> > >>>>> try to get new things in.  I will try to manage this well.
 As
> always
> > >>> we
> > >>>>> can do another release.  There is no timeline pushing us to
have
> such
> > >>>> gaps
> > >>>>> between releases...we can always do another feature release.
 That
> > >>> said,
> > >>>> PR
> > >>>>> review bandwidth is at a super premium.  We receive a lot more
PRs
> > >> than
> > >>>> we
> > >>>>> do receive reviews.  We'll have to work this as the PR depth
grows.
> > >>>>>
> > >>>>> Thanks
> > >>>>> Joe
> > >>>>
> > >>>
> > >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message