I am writing to propose updating our release process to include signing artifacts with GPG. Currently we sign the full build (i.e. nifi-x.y.z-source-release.tar.gz) with the GPG key of the release manager, and the corresponding public key is available in our KEYS file, hosted by Apache. My proposal is that we complement this by signing the individual Maven modules as well, so that consuming projects (ourselves included) can verify that the code they are running was what was published. I’ve included a few links below  that hopefully answer preliminary questions about the process, but I am happy to have further discussion here as well.
I also volunteer to assist with whoever RMs the next release to ensure the process goes smoothly and we document the necessary steps and update our Release Guide .