Flink Release Management

Flink Release Management consists of the following tasks:

• Managing the feature development for the release
• Maintenance of CI builds and infrastructure (for master and the two most-recently release Flink versions)
• Jira maintenance

These tasks are not necessarily exclusively done by the release manager. The community should take care of it. The responsibility of the release manager is to make sure that a certain quality and stability of the relevant code base is achieved.

Additionally, any release-related documentation should be kept up-to-date (e.g. Release Management and Feature Plan or Creating a Flink Release)

Organization

Regular Sync

It's a good habit to meat on a regular basis to sync on the developments of the current release cycle. A summary should be kept in the release's wiki article (see Release Management and Feature Plan) and sent to the dev mailing list to keep the community up-to-date.

Feature Freeze

???

Release

???

Maintenance of CI builds and infrastructure

The release manager should ensure stability of master and the two most-recently published Flink versions in terms of CI. Builds can be monitored on AzureCI Flink build overview (see Testing Infrastructure for further details on the build process). Failed builds are reported to Apache Flink's #builds Slack channel.

Jira maintenance

Build failures should be reported in the corresponding Jira issue (or a Jira issue should be created if none exists, yet). Contributors should be pinged to fix instabilities as soon as possible to ensure a stable infrastructure of the course of the release cycle. More details on Jira issues can be found on the Flink Jira Process wiki page.