Info
It is NOT necessary to run all checks to cast a vote for a release candidate. However, you should clearly state which checks you did when casting a vote. The release manager needs to ensure that each following check was done.

Legal Verifications

Checking Artifacts

Some of these are strictly required for a release to be ASF compliant.

(required) Verify that the checksums and GPG files match the corresponding release files, for:
- All artifacts to be released to Maven in the staging Apache Nexus Repository
- Java/Scala source distributions staged in https://dist.apache.org/repos/dist/dev/flink
(required) Verify that the source distributions do not contain any binaries
(required) Build the source distribution to ensure all source files have Apache headers
- Run "mvn clean install -DskipTests" in the maven source distribution.
(required) Verify that all POM files point to the same version.
Check that the README.md file does not have anything unexpected.

These checks are strictly required for a release to be ASF compliant.

...

A detailed explanation on the steps above is in Licensing.

This is not necessarily required for a release to be ASF compliant, but required to ensure a high quality release.

This is not an exhaustive list - it is mainly a suggestion where to start testing.

Check if the source release is building properly with Maven, including checkstyle and all tests

Create a settings.xml file with these contents:

...