Hi Ron,

When reading the jira release notes, I found there might be some tickets
that are not fixed in 2.1.0 (still open) but labeled 2.1.0,
e.g. FLINK-9879[1] and FLINK-10113[2]. Correct me if I'm wrong.
Shall we revisit those open tickets which are labeled 2.1.0 and see if they
are actually done?


[1] https://issues.apache.org/jira/browse/FLINK-9879
[2] https://issues.apache.org/jira/browse/FLINK-10113

Best,
Zakelly

On Mon, Jul 28, 2025 at 12:06 PM Hongshun Wang <loserwang1...@gmail.com>
wrote:

> +1 (no binding)
> - verified & checksums
> - use release-2.1.0-rc1.tar.gz to run sql jobs.
>
>
> Best,
> Hongshun
>
> On Mon, Jul 28, 2025 at 11:27 AM Leonard Xu <xbjt...@gmail.com> wrote:
>
> > +1 (binding)
> >
> > - verified signatures
> > - verified hashsums
> > - checked Github release tag
> > - checked release notes
> > - ran SQL values test via SQL client in standalone cluster
> > - checked compiled version 55.0 (Java SE 11)
> > - reviewed the web PR, left two comments 'NEED' to fix
> >
> > Best,
> > Leonard
> >
> > > On 2025 Jul 25, at 19:20, Xiqian YU <kono....@outlook.com> wrote:
> > >
> > > +1 (non-binding)
> > >
> > > Checklist:
> > >
> > > - verified tarball checksums & gpg signatures are valid
> > > - confirmed that artifacts were built with JDK 11.0.22 and Maven 3.8.6
> > > - confirmed target bytecode version is 55.0 (JDK 11)
> > > - played Flink SQL client with code snippets
> > > - compiled from source code locally with JDK 11
> > >
> > > Best Regards,
> > > Xiqian
> > >
> > >> 2025年7月25日 18:44,Ferenc Csaky <ferenc.cs...@pm.me.INVALID <mailto:
> > ferenc.cs...@pm.me.INVALID>> 写道:
> > >>
> > >> +1 (non-binding)
> > >>
> > >> - verified checksums & signatures
> > >> - built src with Maven 3.8.6 & JDK17
> > >> - checked Maven repo artifacts
> > >> - deployed TopSpeedWindowing.jar example via `standalone-job.sh`
> > >> - verified GitHub tag
> > >> - reviewed web PR
> > >>
> > >> Best,
> > >> Ferenc
> > >>
> > >>
> > >> On Friday, July 25th, 2025 at 05:35, Xingbo Huang <hxbks...@gmail.com
> >
> > wrote:
> > >>
> > >>>
> > >>>
> > >>> +1 (binding)
> > >>>
> > >>> - verified signatures & checksums
> > >>> - pip install apache-flink-libraries && apache-flink with Python
> > 3.12/3.10
> > >>> in M2
> > >>> - run pyflink job with UDF/Pandas in jdk11 && python 3.10
> > >>>
> > >>> Best,
> > >>> Xingbo
> > >>>
> > >>> Xuyang xyzhong...@163.com 于2025年7月24日周四 17:28写道:
> > >>>
> > >>>> +1
> > >>>>
> > >>>> - built from sources (mac)
> > >>>>
> > >>>> - ran simple jobs by sql-client
> > >>>>
> > >>>> - checked the git tag and date in flink-ui
> > >>>>
> > >>>> --
> > >>>>
> > >>>> Best!
> > >>>> Xuyang
> > >>>>
> > >>>> 在 2025-07-24 11:50:44,"Lincoln Lee" lincoln.8...@gmail.com 写道:
> > >>>>
> > >>>>> Retract my previous -1, it's a local env issue and works fine after
> > fixed.
> > >>>>> Will continue the verification and give my vote later.
> > >>>>>
> > >>>>> Best,
> > >>>>> Lincoln Lee
> > >>>>>
> > >>>>> Lincoln Lee lincoln.8...@gmail.com 于2025年7月24日周四 11:08写道:
> > >>>>>
> > >>>>>> -1
> > >>>>>>
> > >>>>>> When building from source flink-2.1.0-src.tgz, some unexpected
> files
> > >>>>>> (dependency-reduced-pom.xml) with unapproved licenses were found,
> > >>>>>> this should be fixed.
> > >>>>>>
> > >>>>>> Best,
> > >>>>>> Lincoln Lee
> > >>>>>>
> > >>>>>> Ron Liu ron9....@gmail.com 于2025年7月23日周三 12:11写道:
> > >>>>>>
> > >>>>>>> Hi, Xingbo
> > >>>>>>>
> > >>>>>>> Thanks for reporting it.
> > >>>>>>>
> > >>>>>>> After confirming with Dian Fu and Ferenc Csaky, the duplicated
> name
> > >>>>>>> is as
> > >>>>>>> expected, it's a new feature, more detail can see[1].
> > >>>>>>>
> > >>>>>>> 1. https://issues.apache.org/jira/browse/FLINK-38130
> > >>>>>>>
> > >>>>>>> Best,
> > >>>>>>> Ron
> > >>>>>>>
> > >>>>>>> Ron Liu ron9....@gmail.com 于2025年7月23日周三 10:15写道:
> > >>>>>>>
> > >>>>>>>> Hi, Fred
> > >>>>>>>>
> > >>>>>>>>>>> I'm currently experimenting with a local build of Flink
> > 2.1.0-rc1
> > >>>>>>>>>>> and
> > >>>>>>>>>>> a local build of the Flink Kafka Connector 4.0.0. While
> > building the
> > >>>>>>>>>>> Flink
> > >>>>>>>>>>> Kafka Connector, I encountered an issue: the static method
> > >>>>>>>>>>> DataTypeUtils::stripRowPrefix(...) appears to have been
> > removed from
> > >>>>>>>>>>> the
> > >>>>>>>>>>> Flink codebase.
> > >>>>>>>>
> > >>>>>>>> Was this removal intentional? And if so, does the Flink Kafka
> > >>>>>>>> Connector
> > >>>>>>>> still need to be updated to reflect this change?
> > >>>>>>>>
> > >>>>>>>> The method `DataTypeUtils::stripRowPrefix` is removed in PR[1]
> by
> > >>>>>>>> timo.
> > >>>>>>>> This is a normal codebase change, we should update the flink
> > >>>>>>>> dependency
> > >>>>>>>> in
> > >>>>>>>> Kafka connector after Flink 2.1 release.
> > >>>>>>>>
> > >>>>>>>>>>> Also, I'm curious, what is the typical process for releasing
> a
> > >>>>>>>>>>> new
> > >>>>>>>>>>> version of Flink? Do the Flink Connectors receive a new
> > release as
> > >>>>>>>>>>> part
> > >>>>>>>>>>> of
> > >>>>>>>>>>> that process as well?
> > >>>>>>>>
> > >>>>>>>> I've followed the community rule to create a Jira ticket[2] to
> > track
> > >>>>>>>> the
> > >>>>>>>> Flink connector version upgrade for Flink 2.1. After Flink 2.1
> > >>>>>>>> release,
> > >>>>>>>> we
> > >>>>>>>> should push the connector flink version update to 2.1.0.
> > >>>>>>>>
> > >>>>>>>> Reference:
> > >>>>>>>> 1. https://issues.apache.org/jira/browse/FLINK-38090
> > >>>>>>>> 2. https://issues.apache.org/jira/browse/FLINK-38031
> > >>>>>>>>
> > >>>>>>>> Best,
> > >>>>>>>> Ron
> > >>>>>>>>
> > >>>>>>>> Teunissen, F.G.J. (Fred) fred.teunis...@ing.com.invalid
> > >>>>>>>> 于2025年7月23日周三
> > >>>>>>>> 02:27写道:
> > >>>>>>>>
> > >>>>>>>>> Hi Ron,
> > >>>>>>>>>
> > >>>>>>>>> I'm currently experimenting with a local build of Flink
> 2.1.0-rc1
> > >>>>>>>>> and a
> > >>>>>>>>> local build of the Flink Kafka Connector 4.0.0. While building
> > the
> > >>>>>>>>> Flink
> > >>>>>>>>> Kafka Connector, I encountered an issue: the static method
> > >>>>>>>>> DataTypeUtils::stripRowPrefix(...) appears to have been removed
> > from
> > >>>>>>>>> the
> > >>>>>>>>> Flink codebase.
> > >>>>>>>>>
> > >>>>>>>>> Was this removal intentional? And if so, does the Flink Kafka
> > >>>>>>>>> Connector
> > >>>>>>>>> still need to be updated to reflect this change?
> > >>>>>>>>>
> > >>>>>>>>> Also, I'm curious, what is the typical process for releasing a
> > new
> > >>>>>>>>> version of Flink? Do the Flink Connectors receive a new release
> > as
> > >>>>>>>>> part of
> > >>>>>>>>> that process as well?
> > >>>>>>>>>
> > >>>>>>>>> Best regards,
> > >>>>>>>>> Fred Teunissen
> > >>>>>>>>>
> > >>>>>>>>> Sent from Outlook for Mac
> > >>>>>>>>>
> > >>>>>>>>> From: Ron Liu ron9....@gmail.com
> > >>>>>>>>> Date: Monday, 21 July 2025 at 15:41
> > >>>>>>>>> To: dev dev@flink.apache.org
> > >>>>>>>>> Subject: [VOTE] Release 2.1.0, release candidate #1
> > >>>>>>>>>
> > >>>>>>>>> Hi everyone,
> > >>>>>>>>>
> > >>>>>>>>> Please review and vote on the release candidate #1 for the
> > version
> > >>>>>>>>> 2.1.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], and the pull request adding release
> > note
> > >>>>>>>>> for
> > >>>>>>>>>
> > >>>>>>>>> users [2]
> > >>>>>>>>>
> > >>>>>>>>> * the official Apache source release and binary convenience
> > releases
> > >>>>>>>>> to be
> > >>>>>>>>>
> > >>>>>>>>> deployed to dist.apache.org [3], which are signed with the key
> > with
> > >>>>>>>>>
> > >>>>>>>>> fingerprint 7A14EF9AD986EF0D56B2E73F6AF817E6C59EC690 [4],
> > >>>>>>>>>
> > >>>>>>>>> * all artifacts to be deployed to the Maven Central Repository
> > [5],
> > >>>>>>>>>
> > >>>>>>>>> * source code tag "release-2.1.0-rc1" [6],
> > >>>>>>>>>
> > >>>>>>>>> * website pull request listing the new release and adding
> > >>>>>>>>> announcement
> > >>>>>>>>> blog
> > >>>>>>>>> post [7].
> > >>>>>>>>>
> > >>>>>>>>> The vote will be open for at least 72 hours. It is adopted by
> > >>>>>>>>> majority
> > >>>>>>>>>
> > >>>>>>>>> approval, with at least 3 PMC affirmative votes.
> > >>>>>>>>>
> > >>>>>>>>> [1]
> > >>>>
> > >>>>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12355556&styleName=&projectId=12315522
> > >>>>
> > >>>>>>>>> <
> > >>>>
> > >>>>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12355556&styleName=&projectId=12315522
> > >>>>
> > >>>>>>>>> [2]
> > >>>>
> > >>>> https://github.com/apache/flink/pull/26778
> > >>>>
> > >>>>>>>>> https://github.com/apache/flink/pull/26778
> > >>>>>>>>>
> > >>>>>>>>> [3]
> > >>>>
> > >>>> https://dist.apache.org/repos/dist/dev/flink/flink-2.1.0-rc1/
> > >>>>
> > >>>>>>>>> https://dist.apache.org/repos/dist/dev/flink/flink-2.1.0-rc1/
> > >>>>>>>>>
> > >>>>>>>>> [4]
> > >>>>
> > >>>> https://dist.apache.org/repos/dist/release/flink/KEYS
> > >>>>
> > >>>>>>>>> https://dist.apache.org/repos/dist/release/flink/KEYS
> > >>>>>>>>>
> > >>>>>>>>> [5]
> > >>>>
> > >>>>
> > https://repository.apache.org/content/repositories/orgapacheflink-1839/
> > >>>>
> > >>>>>>>>> <
> > >>>>
> > >>>>
> > https://repository.apache.org/content/repositories/orgapacheflink-1839/>
> > >>>>
> > >>>>>>>>> [6]
> > >>>>
> > >>>> https://github.com/apache/flink/releases/tag/release-2.1.0-rc1
> > >>>>
> > >>>>>>>>> https://github.com/apache/flink/releases/tag/release-2.1.0-rc1
> > >>>>>>>>>
> > >>>>>>>>> [7]
> > >>>>
> > >>>> https://github.com/apache/flink-web/pull/800
> > >>>>
> > >>>>>>>>> https://github.com/apache/flink-web/pull/800
> > >>>>>>>>>
> > >>>>>>>>> Best,
> > >>>>>>>>> Ron
> > >>>>>>>>>
> > >>>>>>>>>
> -----------------------------------------------------------------
> > >>>>>>>>> ATTENTION:
> > >>>>>>>>> The information in this e-mail is confidential and only meant
> for
> > >>>>>>>>> the
> > >>>>>>>>> intended recipient. If you are not the intended recipient,
> don't
> > >>>>>>>>> use or
> > >>>>>>>>> disclose it in any way. Please let the sender know and delete
> the
> > >>>>>>>>> message
> > >>>>>>>>> immediately.
> > >>>>>>>>>
> -----------------------------------------------------------------
> >
> >
>

Reply via email to