Versions Compared

Old Version 14

changes.mady.by.user Matthias Pohl

Saved on

compared with

New Version 15

changes.mady.by.user Matthias Pohl

Saved on

Key

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

...

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.

Other tasks:

  • Monitoring the remote branches. Sometimes, there are remote branches created accidentally in the Apache Flink repo. Branches should generally been created in the forks. We might want to reach out to contributors to delete these accidentally created remote branches.

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.
  • Newly created Jira issue should follow the Flink Jira Process guide
  • Jira issues should be correctly labeled with fixVersion, affectedVersion, component

...