This issue was discussed in the past but never reached a consensus for an
implementation that managed the concerns. My email is only to provide a
link to that pull request and discussion, for those who are curious.
https://github.com/apache/nifi/pull/4641
-- Mike
On Tue, Apr 23, 2024 at 5:47
Also agreed there. Profile should be there to exclude perhaps but include
should be default.
On Wed, Apr 24, 2024 at 6:30 AM David Handermann <
exceptionfact...@apache.org> wrote:
> Thanks for the replies thus far!
>
> With the goal of including the new UI, it seems like a good time to
> move
Thanks for the replies thus far!
With the goal of including the new UI, it seems like a good time to
move the module from an optional profile to part of the standard
build. That would make the release candidate build and review process
simpler, not requiring the optional build profile.
Regards,
I also agree with this stance for an initial period of transition time, but
this obviously has a huge impact on contributions. Without any kind of end
date, I worry this is going to be policy indefinitely. Because of this, I
tend to agree with what Rob said in the previous email. Maybe once 2.0 is
+1 Rob
On Wed, Apr 24, 2024 at 8:17 AM Robert Fellows
wrote:
> The new UI has progressed quite well and I agree with this stance. However,
> with 2.0 getting close, one could argue that new UI features should
> definitely land in the new UI but only really need to land in the original
> UI if
The new UI has progressed quite well and I agree with this stance. However,
with 2.0 getting close, one could argue that new UI features should
definitely land in the new UI but only really need to land in the original
UI if desired or to support backward compatibility.
--Rob
On Tue, Apr 23,
