+1 for the release and the release manager.
Thanks for driving this.
Best,
Ferenc
On Tuesday, April 8th, 2025 at 05:06, Leonard Xu wrote:
>
>
> +1, thanks @Arvid for driving this release!
>
> Best,
> Leonard
>
> > 2025 4月 7 18:02，Tom Cooper c...@tomcooper.dev 写道：
> >
> > +1 from me. Than
+1, thanks @Arvid for driving this release!
Best,
Leonard
> 2025 4月 7 18:02，Tom Cooper 写道：
>
> +1 from me. Thanks for driving this.
>
> Is there anything I can do to help?
>
> Tom Cooper
> @tomcooper.dev | https://tomcooper.dev
>
>
> On Monday, 7 April 2025 at 08:54, Arvid Heise wrote:
>
+1 from me. Thanks for driving this.
Is there anything I can do to help?
Tom Cooper
@tomcooper.dev | https://tomcooper.dev
On Monday, 7 April 2025 at 08:54, Arvid Heise wrote:
> Hi folks,
>
> I would like to volunteer to drive the Kafka connector 4.0.0 release to
> make the connector finall
Hi Yanquan,
thank you very much for taking care of this.
I propose to merge your PR without E2E into 4.0-SNAPSHOT. Then we wait
for Flink 2.0.0 with the fix, reenable E2E and lastly we can cut an
official 4.0.0 release (we need to wait for 2.0.0 anyways for the
release).
We could release a 4.0.0-
Hi, Devs.
I am now working on the Kafka connector bump to Flink 2.0 in 4.0.0 version, and
I have already opened a PR for this. Since there is a bug that fix in
[FLINK-36568](Flink 2.0) in Flink 2.0-preview1 that would cause fail to run e2e
case, so I comment out these e2e tests to pass CI.
How
Hi all,
I just sent out the first release candidate for 3.4.0. The only difference
to 3.3.0 is that we cease to support 1.19 in favor of supporting the open
lineage interfaces [1] that have been added to Flink 1.20.
With that release under way (please verify and vote!), the main branch is
now goo
Hi Yanquan,
the current state of the 3.4.0 release is that it's still pending on the
lineage PR [1] which I expect to be merged next week (the author is on
vacation). The release cut would then happen right afterwards.
After the release cut, we can then bump to 4.0.0-SNAPSHOT and Flink
2.0-previe
Thanks @Yanquan for track this thread, and thanks @Arvid for the information,
it makes sense to me
Qingsheng will drive the release of flink-2.0-preview of Flink Kafka connector,
and I’d like assist it too.
Best,
Leonard
> 2024年11月6日 下午6:58，Arvid Heise 写道：
>
> Hi Yanquan,
>
> the current s
Hi, Arvid.
It has been a month and we are glad to see that we have completed the release
of Kafka 3.3.0 targeting 1.19 and 1.20.
Considering that Flink 2.0-preview1 has already been released, I would like to
know about our plans and progress for bumping to 2.0-preview1.
I tested the changes req
that there will be no bug release for 1.19 also? I
assume 1.20 as the last v1 release would have bug releases.
Thoughts?
Kind regards, David.
From: Arvid Heise
Date: Friday, 27 September 2024 at 11:12
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Kafka connector releases
Hi David,
thank
bug release for 1.19 also? I
assume 1.20 as the last v1 release would have bug releases.
Thoughts?
Kind regards, David.
From: Arvid Heise
Date: Friday, 27 September 2024 at 11:12
To: dev@flink.apache.org
Subject: [EXTERNAL] Re: Kafka connector releases
Hi David,
thank you very much for your
Hi Danny,
thanks for bringing this to my attention. I'm also in favor of starting
with Flink 2.0. It's just a nice opportunity to break with some traditions
and we are almost there anyways. We could resume the discussion over there
if you'd like.
Regarding the deprecation. I think you misundersto
Thanks for driving this Arvid.
+1 for the releases and the RM
For the 4.0.0 version it would be good to drop the Flink version from the
connector version (4.0.0, not 4.0.0-2.0). I started a discussion some time
ago [1], however the thread went stale. But I think the feedback was
generally aligned
Hi folks,
thanks for the feedback. I'm still not convinced that it's the best
approach to start with a bugfix release but I did a poor job in
highlighting my thoughts.
* I don't think we have any precedent of deprecating API in a bugfix
release.
* It's not obvious to me if a bugfix release counts
Thanks Arvid for the volunteering!
+ 1 for all of the three releases and RM candidate.Qingsheng and I would like
to help the 4.0.0-preview which follows the Flink 2.0 preview,
please feel free to ping us if you need any help.
Btw, for other external connectors which highest supported flink ve
Hi David,
thank you very much for your reply.
> Some thoughts on whether we need the 3 deliverables. And whether we could
follow more traditional fixpack numbering:
> I see that there is already a release for 1.19
https://mvnrepository.com/artifact/org.apache.flink/flink-connector-kafka/3.2.0-1.1
Thanks for the work, Arvid!
I'm not sure if there's any incompatibility issue for 3.2 + 1.20. If
they are fully compatible, what about not dropping support for 1.18 in
3.2.1, and we release one more version 3.2.1-1.20? Then we can use
3.3.0 for the new lineage feature in 1.20 and drop support for
Hi Arvid,
Some thoughts on whether we need the 3 deliverables. And whether we could
follow more traditional fixpack numbering:
I see that there is already a release for 1.19
https://mvnrepository.com/artifact/org.apache.flink/flink-connector-kafka/3.2.0-1.19
. I am wondering why we need the firs
Hi David,
I didn't see this message, but I did go over the Flink repo yesterday
and closed off all PRs that were relevant to the Kafka connector.
Removing the label won't help much, if a user classifies a Jira ticket
as Connector/Kafka but opens a PR in the Flink repo, the label will be
re-added.
19 matches
Mail list logo
