You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

This page is work in progress! 

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.

Hints around AzureCI/Jira usage

  • AzureCI's console log output view supports line bookmarks: Each line number on the left side of the console log view has its own link assigned to it
  • There are several URLs with placeholder that might be handy when accessing Jira through your browser using Firefox's bookmark keywords or Chrome's search engine feature:
    • https://issues.apache.org/jira/browse/FLINK-%s enables a lookup by ID (i.e. "<keyword> 123" in the browser's address field opens Unable to render Jira issues macro, execution error. straight away)
    • https://issues.apache.org/jira/browse/FLINK-1?filter=-1&jql=project%20%3D%20FLINK%20AND%20text%20~%20%22%s%22%20ORDER%20BY%20id%20DESC  search for any FLINK issue based on a query string (i.e. "<keyword> asd" in the browser's address field opens a search result containing all Flink Jira issues having the search term "asd" in it; handy for looking up Jira issues related to some test instability)
    • https://issues.apache.org/jira/browse/FLINK-10106?filter=-1&jql=project%20%3D%20FLINK%20AND%20text%20~%20%22%s%22%20AND%20status%20NOT%20IN%20(Closed%2C%20Resolved) same as the query above but only for open FLINK Jira issues.
  • No labels