You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Yuepeng Pan <pa...@apache.org> on 2026/07/07 16:45:10 UTC

[VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Hi everyone,

Please review and vote on release candidate #3 for

flink-connector-jdbc v3.4.0, as follows:

[ ] +1, Approve the release

[ ] -1, Do not approve the release (please provide specific comments)



The complete staging area is available for your review, which includes:

* JIRA release notes [1],

* the official Apache source release to be deployed to dist.apache.org

[2], which are signed with the key with fingerprint B5B638DCA5F94E4A

[3],

* all artifacts to be deployed to the Maven Central Repository [4],

* source code tag v3.4.0-rc3 [5],

* website pull request listing the new release [6].

* CI build of the tag [7][8].



The vote will be open for at least 72 hours. It is adopted by majority

approval, with at least 3 PMC affirmative votes.



Thanks,

Yuepeng Pan



[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12356738

[2]
https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.4.0-rc3

[3] https://dist.apache.org/repos/dist/release/flink/KEYS

[4]
https://repository.apache.org/content/repositories/staging/org/apache/flink/flink-connector-jdbc/3.4.0-1.20/

[5] https://github.com/apache/flink-connector-jdbc/releases/tag/v3.4.0-rc3

[6] https://github.com/apache/flink-web/pull/869

[7] https://github.com/apache/flink-connector-jdbc/actions/runs/28875672551

[8] https://github.com/apache/flink-connector-jdbc/actions/runs/28875669459

Re: [VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Posted by Yuepeng Pan <pa...@apache.org>.
Thanks João and everyone involved in the rc voting.

BTW, The voting was cancelled due to [1]

[1] https://github.com/apache/flink-connector-jdbc/pull/209

Thanks,
Yuepeng Pan

João Boto <es...@apache.org> 于2026年7月9日周四 23:47写道:

> Hi,
>
> I agree, also as that module is not released we are ok..
>
> On 2026/07/09 11:06:25 Yuepeng Pan wrote:
> > HI, João.
> >
> > Thanks for your comments.
> >
> > IIUC, since we’re only one release away from completing the multi-module
> > migration, it may be a good idea to plan the removal in the next release
> > cycle.
> >
> > WDYTA ?
> >
> >
> > Best,
> > Yuepeng Pan
> >
> >
> > João Boto <es...@apache.org> 于2026年7月9日周四 06:12写道:
> >
> > > This module was originally a safety net to check backward compatibility
> > > during our multi-module migration.
> > >
> > > I mentioned back then that we could eventually delete it. Since it
> doesn't
> > > follow our current setup principles (like being in the parent POM).
> > >
> > > Should we double-check if it's still providing any real value, or are
> we
> > > good to remove it now?
> > >
> > > Best
> > >
> > > On 2026/07/08 05:06:25 Yuepeng Pan wrote:
> > > > Thanks Weiqing for the catch and PRs.
> > > > I'm not entirely sure whether this warrants a mandatory fix and a
> new RC.
> > > > Please let's hold off for now and wait for some comments from other
> dev
> > > > members.
> > > >
> > > > And I'll process the PRs.
> > > >
> > > >
> > > >
> > > > Thanks,
> > > > Yuepeng Pan
> > > >
> > >
> >
>

Re: [VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Posted by João Boto <es...@apache.org>.
Hi,

I agree, also as that module is not released we are ok..

On 2026/07/09 11:06:25 Yuepeng Pan wrote:
> HI, João.
> 
> Thanks for your comments.
> 
> IIUC, since we’re only one release away from completing the multi-module
> migration, it may be a good idea to plan the removal in the next release
> cycle.
> 
> WDYTA ?
> 
> 
> Best,
> Yuepeng Pan
> 
> 
> João Boto <es...@apache.org> 于2026年7月9日周四 06:12写道:
> 
> > This module was originally a safety net to check backward compatibility
> > during our multi-module migration.
> >
> > I mentioned back then that we could eventually delete it. Since it doesn't
> > follow our current setup principles (like being in the parent POM).
> >
> > Should we double-check if it's still providing any real value, or are we
> > good to remove it now?
> >
> > Best
> >
> > On 2026/07/08 05:06:25 Yuepeng Pan wrote:
> > > Thanks Weiqing for the catch and PRs.
> > > I'm not entirely sure whether this warrants a mandatory fix and a new RC.
> > > Please let's hold off for now and wait for some comments from other dev
> > > members.
> > >
> > > And I'll process the PRs.
> > >
> > >
> > >
> > > Thanks,
> > > Yuepeng Pan
> > >
> >
> 

Re: [VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Posted by Yuepeng Pan <pa...@apache.org>.
HI, João.

Thanks for your comments.

IIUC, since we’re only one release away from completing the multi-module
migration, it may be a good idea to plan the removal in the next release
cycle.

WDYTA ?


Best,
Yuepeng Pan


João Boto <es...@apache.org> 于2026年7月9日周四 06:12写道:

> This module was originally a safety net to check backward compatibility
> during our multi-module migration.
>
> I mentioned back then that we could eventually delete it. Since it doesn't
> follow our current setup principles (like being in the parent POM).
>
> Should we double-check if it's still providing any real value, or are we
> good to remove it now?
>
> Best
>
> On 2026/07/08 05:06:25 Yuepeng Pan wrote:
> > Thanks Weiqing for the catch and PRs.
> > I'm not entirely sure whether this warrants a mandatory fix and a new RC.
> > Please let's hold off for now and wait for some comments from other dev
> > members.
> >
> > And I'll process the PRs.
> >
> >
> >
> > Thanks,
> > Yuepeng Pan
> >
>

Re: [VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Posted by João Boto <es...@apache.org>.
This module was originally a safety net to check backward compatibility during our multi-module migration. 

I mentioned back then that we could eventually delete it. Since it doesn't follow our current setup principles (like being in the parent POM). 

Should we double-check if it's still providing any real value, or are we good to remove it now?

Best

On 2026/07/08 05:06:25 Yuepeng Pan wrote:
> Thanks Weiqing for the catch and PRs.
> I'm not entirely sure whether this warrants a mandatory fix and a new RC.
> Please let's hold off for now and wait for some comments from other dev
> members.
> 
> And I'll process the PRs.
> 
> 
> 
> Thanks,
> Yuepeng Pan
> 

Re: [VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Posted by Chanhae Oh <dh...@gmail.com>.
Hi, Yuepeng.

First of all, thank you for leading the release.
I would also like to thank Weiqing for identifying the issue.

In my opinion, while this isn't a critical issue that would block the
release, it should be included in the main branch.
How about we create a Jira ticket for this issue right away and proceed
with the current release separately?

Thanks,
Chanhae Oh

On Wed, Jul 8, 2026 at 2:07 PM Yuepeng Pan <pa...@apache.org> wrote:

> Thanks Weiqing for the catch and PRs.
> I'm not entirely sure whether this warrants a mandatory fix and a new RC.
> Please let's hold off for now and wait for some comments from other dev
> members.
>
> And I'll process the PRs.
>
>
>
> Thanks,
> Yuepeng Pan
>

Re: [VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Posted by Yuepeng Pan <pa...@apache.org>.
Thanks Weiqing for the catch and PRs.
I'm not entirely sure whether this warrants a mandatory fix and a new RC.
Please let's hold off for now and wait for some comments from other dev
members.

And I'll process the PRs.



Thanks,
Yuepeng Pan

Re: [VOTE] Release flink-connector-jdbc v3.4.0, release candidate #3

Posted by Weiqing Yang <ya...@gmail.com>.
Hi Yuepeng,

Thanks for driving the release. One minor, pre-existing thing I hit while
verifying RC3:

The flink-connector-jdbc-backward-compatibility module ships two files
missing the Apache license header: pom.xml and DynamicTableSourceTest.java.
CI doesn't catch it because the module sits outside the parent pom's
<modules>, so RAT never scans it. It was the same in 3.3.0, so it's not a
regression and doesn't affect the artifacts. (PRs created to fix it: maste
<https://github.com/apache/flink-connector-jdbc/pull/205>, v4.1
<https://github.com/apache/flink-connector-jdbc/pull/206>, v3.4
<https://github.com/apache/flink-connector-jdbc/pull/207>)

My read is this doesn't need an RC respin, but wanted to check how you'd
prefer to handle it.

Best,
Weiqing

On Tue, Jul 7, 2026 at 9:45 AM Yuepeng Pan <pa...@apache.org> wrote:

> Hi everyone,
>
> Please review and vote on release candidate #3 for
>
> flink-connector-jdbc v3.4.0, as follows:
>
> [ ] +1, Approve the release
>
> [ ] -1, Do not approve the release (please provide specific comments)
>
>
>
> The complete staging area is available for your review, which includes:
>
> * JIRA release notes [1],
>
> * the official Apache source release to be deployed to dist.apache.org
>
> [2], which are signed with the key with fingerprint B5B638DCA5F94E4A
>
> [3],
>
> * all artifacts to be deployed to the Maven Central Repository [4],
>
> * source code tag v3.4.0-rc3 [5],
>
> * website pull request listing the new release [6].
>
> * CI build of the tag [7][8].
>
>
>
> The vote will be open for at least 72 hours. It is adopted by majority
>
> approval, with at least 3 PMC affirmative votes.
>
>
>
> Thanks,
>
> Yuepeng Pan
>
>
>
> [1]
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12356738
>
> [2]
> https://dist.apache.org/repos/dist/dev/flink/flink-connector-jdbc-3.4.0-rc3
>
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>
> [4]
>
> https://repository.apache.org/content/repositories/staging/org/apache/flink/flink-connector-jdbc/3.4.0-1.20/
>
> [5] https://github.com/apache/flink-connector-jdbc/releases/tag/v3.4.0-rc3
>
> [6] https://github.com/apache/flink-web/pull/869
>
> [7]
> https://github.com/apache/flink-connector-jdbc/actions/runs/28875672551
>
> [8]
> https://github.com/apache/flink-connector-jdbc/actions/runs/28875669459
>