Thanks Mika for kicking off the discussion about the 2.4 version.
I also agree with extending the freeze window duration. +1 (non-binding) Additionally, I would like to volunteer as one of the release managers for this version as well. While I'm not a committer, I would like to contribute to whichever parts are needed from the perspective of someone who actively uses Flink. Thanks, Chanhae Oh 2026년 8월 27일 목요일, Mika Naylor <[email protected]>님이 작성: > Hi all! > > I would like to start a discussion on the next Flink release: 2.4. > > Release Managers > ------------------ > > After discussing with David Anderson who was a RM for the last release, I > would like to propose another release cycle where we have a team of > committers from different backgrounds. > > To that end I would like to volunteer as a RM for this round, with the > caveat that I am not a committer or PMC member, but would love to drive > whichever bits of the process (like the feature collection wiki, blocker > triage, release notes, coordination, testing and verification) I can > contribute to. With that in mind, if any committers and/or PMC members > would be interested in joining the release time this cycle, please let me > know! > > Timeline > -------- > > Flink 2.3 was released on June 25th, so I would propose a feature freeze > around September 30th with a release date around the end of October. Does > this sound reasonable? Rui Fan mentioned a 1 month freeze window is maybe > too narrow for ongoing flips during the 2.3 discussion, would 1.5-2 make > more sense? > > Feature Collection > ------------------ > > I've set up a wiki page [1] for collecting new features for 2.4. Once > everything is finalized, we can then set up the jira board, meetings and > sync points to give everyone an overview. > > Kind regards, > Mika > > [1] https://cwiki.apache.org/confluence/spaces/FLINK/pages/ > 449286596/2.4+Release >
