Hey David and Hao, Thanks for driving the 2.3 release.
Would it be feasible to push back both the feature freeze and the final release by one month? I’d like to propose this for two reasons: 1. Tight Schedule for FLIPs: The current one-month window until the feature freeze is quite tight for many of the ongoing FLIPs. 2. Holiday Impact on Community Availability: This release cycle coincides with several major holidays, including Christmas, New Year, and the Lunar(Chinese) New Year (Feb 17-23). These breaks will inevitably limit the bandwidth of many contributors and reviewers right before the freeze date. Given these factors, a one-month extension might help ensure a more stable and high-quality release. I would love to hear the community's thoughts on this. Best, Rui On Wed, Jan 21, 2026 at 10:43 PM David Anderson <[email protected]> wrote: > Hi everyone, > > I'd like to start the discussion of the next release, Flink 2.3. > > - Release Managers > > I'd like to volunteer as one of the release managers, along with Hao Li. > Rui Fan has offered to help us with the steps that require PMC permission. > > It has been good practice to have a team of release managers from different > backgrounds, so please raise your hand if you'd like to volunteer and get > involved. > > - Timeline > > Flink 2.2 was released at the beginning of December 2025. With a target > release cycle of 4 months, we propose a feature freeze date of Feb 28, > 2026, targeting a final release at the end of March 2026. > > - Collecting Features > > As usual, we've created a wiki page[1] for collecting new features in 2.3. > > Once the release management team is finalized, we will setup the Jira > Boards and Sync meetings to make it easy for everyone to get an overview > and track progress. > > Best, > David > > [1] https://cwiki.apache.org/confluence/x/eYU8G >
