Page History

...

• Blockers: are these really blockers or do we want to move the release forward?

  • Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-31092

     → Qingsheng Ren to check the status with Shengkai Fang 

  • Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-31104

    → Qingsheng Ren to check the status with Shengkai Fang 

  • Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-30978

     → Qingsheng Ren to check the status with Shengkai Fang 
• Other issues:

  • Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-31134

    : Revisit OOM in Kafka e2e test in 1.15.3 - we're keeping it as critical for now. There are no other artifacts that we can investigate. The test doesn't involve table-runner code (therefore, isn't connected to

    Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-18356

    ). → Martijn Visser to check internally
  • Dependabot alerts are affecting all commiters now
• Release managers to review draft of 1.17 announcement
• Release 1.17 preparation:  

  Jira
  server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-31146