Thanks for the kick off and volunteering as release manager, Ron. +1 for start preparing release 2.1 and Ron as the release manager. The proposed feature freeze date sounds good to me.
@David, Just to provide some background information. In the Flink community, we use the terminologies Major, Minor and Bugfix releases, represented by the three digits in the version number respectively. E.g., 1.20.1 represents Major version 1, Minor version 20 and Bugfix version 1. The major differences are: 1. API compatibility: @Public APIs are guaranteed compatible across different Minor and Bugfix releases of the same Major version. @PublicEvolving APIs are guaranteed compatible across Bugfix releases of the same Minor version. 2. Bugfix releases typically only include bugfixes, but not feature / improvement code changes. Major and Minor releases include both feature / improvements and bugfixes. The Flink community applies a time-based release planning [1] for Major / Minor releases. We try to deliver new features with a new release (typically Minor, unless we decide to break the API compatibility with a Major release) roughly every 4 months. As for bugfix releases, they are usually planned on-demand. E.g., to make a critical bugfix available to users, or observed significant bugfix issues have been merged for the release branch. Best, Xintong [1] https://cwiki.apache.org/confluence/display/FLINK/Time-based+releases On Wed, Mar 26, 2025 at 12:14 AM David Radley <david_rad...@uk.ibm.com> wrote: > Hi , > I am wondering what the thinking is about calling the next release 2.1 > rather than 2.0.1. This numbering implies to me you are considering a > minor release rather than a point release. For example > https://commons.apache.org/releases/versioning.html, > > Kind regards, David. > > > From: Jark Wu <imj...@gmail.com> > Date: Tuesday, 25 March 2025 at 06:52 > To: dev@flink.apache.org <dev@flink.apache.org> > Subject: [EXTERNAL] Re: [DISCUSS] Planning Flink 2.1 > Thanks, Ron Liu for kicking off the 2.1 release. > > +1 for Ron Liu to be the release manager and > +1 for the feature freeze date > > Best, > Jark > > On Mon, 24 Mar 2025 at 16:33, Ron Liu <ron9....@gmail.com> wrote: > > > Hi everyone, > > With the release announcement of Flink 2.0, it's a good time to kick off > > discussion of the next release 2.1. > > > > - Release Managers > > > > I'd like to volunteer as one of the release managers this time. It has > been > > good practice to have a team of release managers from different > > backgrounds, so please raise you hand if you'd like to volunteer and get > > involved. > > > > > > - Timeline > > > > Flink 2.0 has been released. With a target release cycle of 4 months, > > we propose a feature freeze date of *June 21, 2025*. > > > > > > - Collecting Features > > > > As usual, we've created a wiki page[1] for collecting new features in > 2.1. > > > > In the meantime, the release management team will be finalized in the > next > > few days, and we'll continue to create Jira Boards and Sync meetings > > to make it easy for everyone to get an overview and track progress. > > > > > > Best, > > Ron > > > > [1] https://cwiki.apache.org/confluence/display/FLINK/2.1+Release > > > > Unless otherwise stated above: > > IBM United Kingdom Limited > Registered in England and Wales with number 741598 > Registered office: Building C, IBM Hursley Office, Hursley Park Road, > Winchester, Hampshire SO21 2JN >
