-1 (non-binding) I hate to be the one to down vote this RC. I know we are all anxious to reach the 2.0.0 release. However, I believe it is worth a very minor delay to go through an RC2 to fix some issues that would be very disappointing for users to see out of a major release. Their existence gives the impression that 2.0.0 is buggy, IMO. There are PR's already available for some of the issues I noted so the turn-around should be fast.
The most significant is the issue reported by Nissim which I replicated. A versioned flow cannot be instantiated from Registry, or at best it can be but the user has no intuitive way to accomplish it nor a clear recognition of which version is being instantiated. This issue alone is enough for me to down vote. See Jira and PR: https://issues.apache.org/jira/browse/NIFI-13926 https://github.com/apache/nifi/pull/9443 Another issue is the color of the icon when dragging a new component to the canvas (in light mode). Overall, this one might be minor. But again, in the interest of a major release presenting itself well to users, I think it is worth fixing. A PR is already up. https://issues.apache.org/jira/browse/NIFI-13920 https://github.com/apache/nifi/pull/9438 Items which I am not sure if they have been reported (and may not be enough on their own to tank an RC) include: - A misconfiguration of a cluster caused it to not start. Two of the three nodes did not properly terminate and log messages continued to be entered into nifi-app.log even though "nifi.sh status" indicated NiFi was not running. - A Management Controller Service was invalid on startup. (The flow.json.gz was copied from another instance, but a file in the CS properties was missing.) The service could not be edited immediately even though it was in an "Invalid" state. It needed to be explicitly disabled first. On Tue, Oct 22, 2024 at 1:03 AM David Handermann < exceptionfact...@apache.org> wrote: > Team, > > I am pleased to be calling this vote for the source release of Apache > NiFi 2.0.0. > > Please review the following guide for how to verify a release candidate > build: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification > > The source being voted on the and the convenience binaries are > available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.0.0 > > The build artifacts are available on the Apache Nexus Repository: > > https://repository.apache.org/content/repositories/orgapachenifi-1293/ > > Git Tag: nifi-2.0.0-RC1 > Git Commit ID: 34160740980c2d9d5cd0a6c399e09c2bd06d5acb > GitHub Commit Link: > > https://github.com/apache/nifi/commit/34160740980c2d9d5cd0a6c399e09c2bd06d5acb > > Checksums of nifi-2.0.0-source-release.zip > > SHA512: > 09f37a4f8fd798a8b067d7970ea571ebc2f729c98cffd427e00d41a0b9312bbcd6b074a1f9109304939b89b5074ccdc48feeff712ecce3f3b1e1a358da7e4a57 > > Release artifacts are signed with the following key: > > https://people.apache.org/keys/committer/exceptionfactory.asc > > KEYS file is available on the Apache Distribution Repository: > > https://dist.apache.org/repos/dist/release/nifi/KEYS > > Issues resolved for this version: 323 > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354889 > > Release note highlights can be found on the project wiki: > > > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0 > > The vote will be open for 72 hours. > > Please download the release candidate and evaluate the necessary items > including checking hashes, signatures, build from source, and test. > Then please vote: > > [] +1 Release this package as nifi-2.0.0 > [] +0 no opinion > [] -1 Do not release this package because... >
