Versions Compared

Old Version 3

changes.mady.by.user Robert Metzger

Saved on

compared with

New Version 4

changes.mady.by.user Robert Metzger

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Verifying a Release Candidate

Legal: (required checks for a valid ASF compilant release)

  • Check if checksums and GPG files match the corresponding release files
  • Check if the source archive contains any binaries
    • binaries are not allowed in the source release
  • Check if the source release is building properly with maven (including license header check (default) and checkstyle). Also the tests should be executed (mvn clean install)
  • Verify that the LICENSE and NOTICE file is correct for the binary and source release.Verify that the quickstarts for scala and java are working with the staging repository for both IntelliJ and Eclipse.
  • in particular the dependencies of the quickstart project need to be set correctly and the QS project needs to build from the staging repository (replace the snapshot repo URL with the staging repo URL)
    • The dependency tree of the QS project must not contain any dependencies we shade away upstream (guava, netty, ...

Functional: (checks for delivering a release with good quality)

  • Verify that the examples are running from both ./bin/flink and from the web-based job submission tool
    • Check also that the examples are running with the build-in data and external sources.
    • On a cluster with HDFS check that a good amount of input splits is read locally
  • Verify that Flink is working properly on OS X, Linux and Windows
    • No exceptions in the log output (after shutdown)
    • Web interface shows progress and finished job in history
    • Results of job are produced and correct
  • Verify the plan visualizer with different browsers/operating systems
  • Verify that the quickstarts for scala and java are working with the staging repository for both IntelliJ and Eclipse.
    • in particular the dependencies of the quickstart project need to be set correctly and the QS project needs to build from the staging repository (replace the snapshot repo URL with the staging repo URL)
    • The dependency tree of the QS project must not contain any dependencies we shade away upstream (guava, netty, ...)

 

Creating a release candidate

...