Hi, Thanks for driving this!
I see that every Flink minor version will have a major connector version. Do we have any specific reason to do so? The different versions ship backward- incompatible changes between those Flink versions? Otherwise I do not see a reason to do this, that's why I'm asking. Best, Ferenc On Thursday, June 25th, 2026 at 02:52, 주수민 <[email protected]> wrote: > Hi Dev, > > This is a progress update and plan sync for the upcoming > flink-connector-jdbc releases > targeting the following versions: > > [1] jdbc-3.4.0 (for Flink 1.20) > [2] jdbc-5.0.0 (for Flink 2.1) > [3] jdbc-6.0.0 (for Flink 2.2) > > We have reviewed and merged critical, high-priority PRs, and we are now > moving forward > to build the RC (Release Candidate) in the next phase. > > [Progress] > > 1. Jira version tags have been created (jdbc-3.4.0, jdbc-3.5.0, > jdbc-5.0.0, jdbc-6.0.0). > Note: jdbc-3.5.0 is prepared as a reserve version to accommodate > potential follow-up > patches after the initial jdbc-3.4.0 release, if needed. > 2. The major feature patch (PR #180 [4]) has been merged. > 3. PR #198 [5] was submitted as a follow-up to the stale PR #174[6] > (FLINK-38046). > > [1] > https://issues.apache.org/jira/browse/FLINK-33463?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%20jdbc-3.4.0 > [2] > https://issues.apache.org/jira/browse/FLINK-33463?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%20jdbc-5.0.0 > [3] > https://issues.apache.org/jira/browse/FLINK-39974?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%20jdbc-6.0.0 > [4] https://github.com/apache/flink-connector-jdbc/pull/180 > [5] https://github.com/apache/flink-connector-jdbc/pull/198 > [6] https://github.com/apache/flink-connector-jdbc/pull/174 > > Thanks, > Sumin Joo >
