You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Mike Thomsen <mi...@gmail.com> on 2019/07/29 19:12:11 UTC
Required work to close out 1.10
This thread is to just get a discussion started on what tickets need to be
closed out before we should do 1.10.
For graph there are two essential bug fixes:
https://github.com/apache/nifi/pull/3571
https://github.com/apache/nifi/pull/3572
I think Jeff's Java 11 build support should also be included if possible:
https://github.com/apache/nifi/pull/3404/
If anyone needs some help on a review, feel free to ping me on GitHub.
Mike
Re: Required work to close out 1.10
Posted by Mike Thomsen <mi...@gmail.com>.
FWIW I'm 100% in favor of waiting until we can get both fully working on
Java 11.
On Mon, Jul 29, 2019 at 3:44 PM Jeff <jt...@gmail.com> wrote:
> Another thought might be to get NiFi Registry builds on Java 11 working as
> well for the NiFi Registry 0.5.0 release. With the NiFi Java 11 build
> compatibility close to being merged, it should be much more simple to get
> NiFi Registry building on Java 11. It would be good to release versions
> for both projects to support Java 11 builds close together.
>
> We could release NiFi 1.10.0 with Java 11 build compatibility, and then
> release NiFi Registry 0.6.0 with Java 11 build compatibility, but I'm not
> sure what other features would be included in NiFi Registry 0.6.0 other
> than the Java 11 build compatibility. I realize that might push back the
> NiFi Registry 0.5.0 release timeframe back, probably weeks.
>
> On Mon, Jul 29, 2019 at 3:29 PM Andy LoPresto <al...@apache.org>
> wrote:
>
> > There are also a number of new features around encrypted repositories and
> > encrypted configuration values that would be good to get in. Some have
> > active PRs up right now, and others are close to being posted.
> >
> > Andy LoPresto
> > alopresto@apache.org
> > alopresto.apache@gmail.com
> > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> >
> > > On Jul 29, 2019, at 12:27 PM, Bryan Bende <bb...@gmail.com> wrote:
> > >
> > > There are two really helpful bug fixes [1][2] related to version
> > > controlling flows that I would like to see make it in to 1.10.0, but
> > > they are dependent on releasing registry 0.5.0 first, since part of
> > > the fixes are in the registry flow-diff code which NiFi depends on.
> > >
> > > So I was hoping to release registry 0.5.0 first, then nifi 1.10.0.
> > >
> > > If we took that approach I think there are still a few remaining items
> > > before we can make a registry release.
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-6025
> > > [2] https://issues.apache.org/jira/browse/NIFI-6314
> > >
> > > On Mon, Jul 29, 2019 at 3:12 PM Mike Thomsen <mi...@gmail.com>
> > wrote:
> > >>
> > >> This thread is to just get a discussion started on what tickets need
> to
> > be
> > >> closed out before we should do 1.10.
> > >>
> > >> For graph there are two essential bug fixes:
> > >>
> > >> https://github.com/apache/nifi/pull/3571
> > >> https://github.com/apache/nifi/pull/3572
> > >>
> > >> I think Jeff's Java 11 build support should also be included if
> > possible:
> > >>
> > >> https://github.com/apache/nifi/pull/3404/
> > >>
> > >> If anyone needs some help on a review, feel free to ping me on GitHub.
> > >>
> > >> Mike
> >
> >
>
Re: Required work to close out 1.10
Posted by Jeff <jt...@gmail.com>.
Another thought might be to get NiFi Registry builds on Java 11 working as
well for the NiFi Registry 0.5.0 release. With the NiFi Java 11 build
compatibility close to being merged, it should be much more simple to get
NiFi Registry building on Java 11. It would be good to release versions
for both projects to support Java 11 builds close together.
We could release NiFi 1.10.0 with Java 11 build compatibility, and then
release NiFi Registry 0.6.0 with Java 11 build compatibility, but I'm not
sure what other features would be included in NiFi Registry 0.6.0 other
than the Java 11 build compatibility. I realize that might push back the
NiFi Registry 0.5.0 release timeframe back, probably weeks.
On Mon, Jul 29, 2019 at 3:29 PM Andy LoPresto <al...@apache.org> wrote:
> There are also a number of new features around encrypted repositories and
> encrypted configuration values that would be good to get in. Some have
> active PRs up right now, and others are close to being posted.
>
> Andy LoPresto
> alopresto@apache.org
> alopresto.apache@gmail.com
> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>
> > On Jul 29, 2019, at 12:27 PM, Bryan Bende <bb...@gmail.com> wrote:
> >
> > There are two really helpful bug fixes [1][2] related to version
> > controlling flows that I would like to see make it in to 1.10.0, but
> > they are dependent on releasing registry 0.5.0 first, since part of
> > the fixes are in the registry flow-diff code which NiFi depends on.
> >
> > So I was hoping to release registry 0.5.0 first, then nifi 1.10.0.
> >
> > If we took that approach I think there are still a few remaining items
> > before we can make a registry release.
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-6025
> > [2] https://issues.apache.org/jira/browse/NIFI-6314
> >
> > On Mon, Jul 29, 2019 at 3:12 PM Mike Thomsen <mi...@gmail.com>
> wrote:
> >>
> >> This thread is to just get a discussion started on what tickets need to
> be
> >> closed out before we should do 1.10.
> >>
> >> For graph there are two essential bug fixes:
> >>
> >> https://github.com/apache/nifi/pull/3571
> >> https://github.com/apache/nifi/pull/3572
> >>
> >> I think Jeff's Java 11 build support should also be included if
> possible:
> >>
> >> https://github.com/apache/nifi/pull/3404/
> >>
> >> If anyone needs some help on a review, feel free to ping me on GitHub.
> >>
> >> Mike
>
>
Re: Required work to close out 1.10
Posted by Andy LoPresto <al...@apache.org>.
There are also a number of new features around encrypted repositories and encrypted configuration values that would be good to get in. Some have active PRs up right now, and others are close to being posted.
Andy LoPresto
alopresto@apache.org
alopresto.apache@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jul 29, 2019, at 12:27 PM, Bryan Bende <bb...@gmail.com> wrote:
>
> There are two really helpful bug fixes [1][2] related to version
> controlling flows that I would like to see make it in to 1.10.0, but
> they are dependent on releasing registry 0.5.0 first, since part of
> the fixes are in the registry flow-diff code which NiFi depends on.
>
> So I was hoping to release registry 0.5.0 first, then nifi 1.10.0.
>
> If we took that approach I think there are still a few remaining items
> before we can make a registry release.
>
> [1] https://issues.apache.org/jira/browse/NIFI-6025
> [2] https://issues.apache.org/jira/browse/NIFI-6314
>
> On Mon, Jul 29, 2019 at 3:12 PM Mike Thomsen <mi...@gmail.com> wrote:
>>
>> This thread is to just get a discussion started on what tickets need to be
>> closed out before we should do 1.10.
>>
>> For graph there are two essential bug fixes:
>>
>> https://github.com/apache/nifi/pull/3571
>> https://github.com/apache/nifi/pull/3572
>>
>> I think Jeff's Java 11 build support should also be included if possible:
>>
>> https://github.com/apache/nifi/pull/3404/
>>
>> If anyone needs some help on a review, feel free to ping me on GitHub.
>>
>> Mike
Re: Required work to close out 1.10
Posted by Bryan Bende <bb...@gmail.com>.
There are two really helpful bug fixes [1][2] related to version
controlling flows that I would like to see make it in to 1.10.0, but
they are dependent on releasing registry 0.5.0 first, since part of
the fixes are in the registry flow-diff code which NiFi depends on.
So I was hoping to release registry 0.5.0 first, then nifi 1.10.0.
If we took that approach I think there are still a few remaining items
before we can make a registry release.
[1] https://issues.apache.org/jira/browse/NIFI-6025
[2] https://issues.apache.org/jira/browse/NIFI-6314
On Mon, Jul 29, 2019 at 3:12 PM Mike Thomsen <mi...@gmail.com> wrote:
>
> This thread is to just get a discussion started on what tickets need to be
> closed out before we should do 1.10.
>
> For graph there are two essential bug fixes:
>
> https://github.com/apache/nifi/pull/3571
> https://github.com/apache/nifi/pull/3572
>
> I think Jeff's Java 11 build support should also be included if possible:
>
> https://github.com/apache/nifi/pull/3404/
>
> If anyone needs some help on a review, feel free to ping me on GitHub.
>
> Mike