Thanks for kicking this off David! +1 for the revised timeline and release managers.
Best, Ferenc On Thursday, January 22nd, 2026 at 16:17, David Anderson <[email protected]> wrote: > > > I agree that it makes sense to extend the timeframe for this release, and > I've updated the wiki [1] accordingly. This moves the feature freeze to > March 31, 2026, and the final release to the end of April. > > Thank you, Yuepeng Pan, for offering to help. Happy to have you! > > [1] https://cwiki.apache.org/confluence/x/eYU8G > > On Thu, Jan 22, 2026 at 3:21 AM Yuepeng Pan [email protected] wrote: > > > Thanks David for kicking off this version. > > > > I briefly reviewed the number of FLIPs mentioned in the mailing list since > > the release of Flink 2.2, > > and there appear to be about ten [1]. Although not all of these are > > necessarily planned for the 2.3 release, > > several FLIPs have already entered the development phase. > > This may give a preliminary sense of the workload scope and the > > developer/user communities involved. > > So +1 for extending both the release timeline and the feature freeze > > deadline > > to mitigate the potential time and workload risks posed by the upcoming > > holidays. > > > > Additionally, I'd like to volunteer as one of the release managers this > > time, too. > > > > [1] https://lists.apache.org/[email protected]:lte=1M:FLIP- > > > > Best regards, > > Yuepeng Pan > > > > Rui Fan [email protected] 于2026年1月22日周四 16:48写道： > > > > > 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
