Table of contents

Jira Boards

Flink 1.20 Burndown: 1.20 Burndown - Agile Board - ASF JIRA (apache.org)

Sync meeting

  • The release sync will start from April 9, 2024, at 10am (UTC+2) and 4pm (UTC+8). The release sync happens bi-weekly at first, and adjusted to weekly from June 4, 2024, as we approaching the feature freeze date. 
  • Feel free to join on Google Meetand attendees are encouraged to fill out the topics to be discussed at the bottom of this page a day in advance to make it easier for everyone to understand the background of the topic. 

Timeline

  • Feature Freeze
    • June 15, 2024, 00:00 CEST(UTC+2) 
  • Release
    • End of July 2024


Highlight features

please feel free to add/suggest.

Features

List of features announced by contributors and committers that are likely to be ready for the feature freeze:n

NOTICE: It's preferred if only new features end up there and not all bugs/tasks separately, so that the page is not over bloated. Of course, unless fixing a bug is a really big or important one equivalent to implementing a completely new feature. A good rule of thumb would be that each entry in the page could (but does not have to) be later on included in a release blog post.

Legend

State

symbolmeaningcomment
(big grin)validatedthrough cross team testing
(tick)donewell documented with a complete test coverage
(green star)will make itthere is no reason this effort should not go into 1.20
(star)in dangerthere are some concerns the effort could be ready for the feature freeze of 1.20
(red star)very unlikelythere are severe concerns the effort could make it to 1.20
(minus)won't make itit was decided against adding this for the 1.20 release. working on the effort has been stopped.
(question)state unclear
(blue star)independentas the artifact could be released independent of Apache Flink

X-Team verification

symbolmeaning
(tick)done
(blue star)not required

Feature Stage

Please align with the list on the Apache Flink Roadmap (https://flink.apache.org/roadmap.html).

  • MVP: Have a look, consider whether this can help you in the future.
  • Beta: You can benefit from this, but you should carefully evaluate the feature.
  • Ready and Evolving: Ready to use in production, but be aware you may need to make some adjustments to your application and setup in the future, when you upgrade Flink.
  • Stable: Unrestricted use in production
  • Reaching End-of-Life: Stable, still feel free to use, but think about alternatives. Not a good match for new long-lived projects.
  • Deprecated: Start looking for alternatives now 

Summary

Numbers are based on the items in the list below, not on the tickets 


(big grin)(tick) (green star)(star)(red star)(minus)(question)(blue star)Remaining weeks
2024-04-23

51



68
2024-05-07

62



86
2024-05-21
172



104
2024-06-04
38
2


132
2024-06-11
68

2

161

List

Feel free to add categories.

Runtime
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
Shuffle









Yuxin Tan 

(tick)
2024-06-12













Coordination









Junrui Lee Zhu Zhu 

(tick)
2024-05-31













State & Checkpoint











(green star)97%2024-06-04


FLINK-31238 - Getting issue details... STATUS



(minus)
2024-06-04




(minus)
2024-06-04


FLINK-26050 - Getting issue details... STATUS


Done

Documentation needed.

(green star)99%2024-06-05


REST

































Web UI











RocMarshal 

(tick)
2024-05-16













SQL
Name/JIRA IssueResponsible ContributorReviewer / committer availableFeature StageNoteState%UpdatedImplementedDocumentedX-team verified
Jane Chan 

(green star)99%2024-06-14
to be completed

FLIP-376: Add DISTRIBUTED BY clause

FLINK-33494 - Getting issue details... STATUS

Timo Walther 

(green star)
2024-04-10


ron liu@Feng Jin


MVP for 1.20 completed, docs are preparing(tick)95%2024-06-11


ron liu @Feng Jin



(tick)100%2024-06-11


Connectors









Sergey Nuyanzin 

(tick)100%2024-06-13


Xia Sun Zhu Zhu 

(tick)
2024-05-22




(tick)
2024-05-26


Resource Management































Runtime

FLIP-398: Improve Serialization Configuration And Usage In Flink

Add built-in Map/List/Set serializers

FLINK-34037 - Getting issue details... STATUS

Zhanghao Chen 

(minus)
2024-06-12


FLIP-443: Interruptible timers firing

FLINK-20217 - Getting issue details... STATUS



(tick)
2024-06-14













Status / Follow-ups

04/09/24

  • Feature freeze date – June 15 all set?
    • Discussed on ML and we are all aligned on the date 👍🏼
    • Robert Metzger feature list looks pretty light currently
    • TODOUfuk Celebi to ping Confluent teams to add features to Wiki
  • Flink 1.19 retro
    • TODO Ufuk Celebi to reach out to release managers of Flink 1.19 and ask for feedback
    • TODO Robert Metzger to ask about mailing list monitoring
  • Daily work divisions
    • JIRA ticket (Mainly focus on new blockers, progress of existing blockers each week)
    • CI (Failures reported in #build channel and not reported)
    • Benchmark (Check if there's regression in the #flink-dev-benchmarks channel)
    • Mailing list monitoring
  • Blockers of 1.20
    • FLINK-35040 - Getting issue details... STATUS
      • It seems Java 11 regresses, and Java 8 and Java 17 are fine.
      • Robert Metzger Any relevant change recently? 
      • Rui Fan applied for a Jenkins account to check for a JVM version upgrade.
    • FLINK-35009 - Getting issue details... STATUS
      • Since Transformation  is an Internal API indeed, and this only breaks the kafka-connector test code. I tend to this should not be a blocker at all.
    • FLINK-34997 - Getting issue details... STATUS
      • This one is an unstable test case, seems to be that docker-compose binaries are sometimes missing in the Azure VMs. 


04/23/24

  • Blockers of 1.20
    •   FLINK-35040 - Getting issue details... STATUS
      • It seems the performance regresses after FLINK-34955 - Getting issue details... STATUS is merged.
      • The performance will be recovered after reverting common-ios version.
      • 2 concerns:
        • I didn't find any common-ios code cost the time during run the benchmark on my Local. (async-profiler wall mode)
        • FLINK-34955 - Getting issue details... STATUS seems necessary and fixes some bugs.
      • TODO: Try generate the flame graph on benchmark server Rui Fan 
    • FLINK-35041 - Getting issue details... STATUS
      • I can't reproduce this by running IncrementalRemoteKeyedStateHandleTest itself, but I can reliably reproduce it (within about a minute) by running the entire org.apache.flink.runtime.state package in the mode "Repeat until stopped". (Comments from Ryan)
      • I have reached out Feifan Wang  to take a look.
    • FLINK-35009 - Getting issue details... STATUS
      • Can anyone reach out Martijn Visser and ask him about this? I'm inclined to think we can downgrade it.
    • FLINK-34997 - Getting issue details... STATUS
    • FLINK-35215 - Getting issue details... STATUS
      • It seems FLINK-34954 - Getting issue details... STATUS causes it.


05/07/24

  • Blockers of 1.20
    •   FLINK-35040 - Getting issue details... STATUS
      • TODO: Try generate the flame graph on benchmark server Rui Fan 
    • FLINK-35041 - Getting issue details... STATUS
      • I can't reproduce this by running IncrementalRemoteKeyedStateHandleTest itself, but I can reliably reproduce it (within about a minute) by running the entire org.apache.flink.runtime.state package in the mode "Repeat until stopped". (Comments from Ryan)
      • I have reached out Feifan Wang  to take a look.
      • Rui Fan reach out Feifan Wang 
    • FLINK-35215 - Getting issue details... STATUS
  • Rui Fan to send a reminder about:
    • The feature freeze date in 6 weeks
    • Check whether the Public or Public Evolving api related to flink 2.0 deprecation has been done


05/21/24

  • Blockers of 1.20
    •   FLINK-35040 - Getting issue details... STATUS
      • Generated the flame graph on benchmark server Zakelly Lan  Rui Fan 
      • But we didn't see any common-ios package code is called. And it doesn't influence other dependency.
      • Update it to dev mail list to collect some valuable suggestion.
      • We will accept this regression if we don't have any suggestion.
        • It only happens on benchmark server with jdk11
    • FLINK-35041 - Getting issue details... STATUS
      • it's solved.
    • FLINK-35215 - Getting issue details... STATUS

06/04/24

  • Blockers of 1.20
    • closed since the last sync: 
      • FLINK-35040 - Getting issue details... STATUS
        • We accepted this regression
      • FLINK-35215 - Getting issue details... STATUS
        • The performance has been recovered.
    • unclosed:
      • FLINK-35423 - Getting issue details... STATUS
        • Have reached out Sergey for updating the progress.
  • The development progress
    • Only left 2 weeks for feature freeze, do we need to remind developers in dev SUMMARY mail list?
    • And ask developers whether we need to extend it because of some awesome feature?
    • Update the percentage of progress.
  • CI pipeline triggered by pull request seems sort of unstable. https://github.com/apache/flink/pull/24883
  • According to the last discussion, this call will be scheduled once a week.

06/11/24

  • No blockers of 1.20
  • June 15 is the planned feature freeze day, total 16, done 8, will make it 6, very unlikely 2;
    • There are only three days left to feature freeze
    • We need to check all the features one by one
    • Highlight in the SUMMARY mail that it is very close to the feature freeze date.
    • Whether to delay feature freeze day
  • When to cut release-1.20 branch? 
    • 1~2 weeks after feature freeze.
  • Start cross team release testing after feature freeze Weijie Guo 
  • No labels