pective, the feature would bring significant value. I’d
> also
> > > be happy to help move it forward.
> > >
> > > Please let me know what would be most helpful to make this happen.
> > >
> > > Best regards,
> > > Fred Teunissen
> > >
be most helpful to make this happen.
> >
> > Best regards,
> > Fred Teunissen
> >
> > From: Ron Liu
> > Date: Saturday, 21 June 2025 at 11:46
> > To: dev@flink.apache.org
> > Subject: Re: [ANNOUNCE] Flink 2.1 feature freeze
> >
> > Hi, Ser
ng significant value. I’d also
> be happy to help move it forward.
>
> Please let me know what would be most helpful to make this happen.
>
> Best regards,
> Fred Teunissen
>
> From: Ron Liu
> Date: Saturday, 21 June 2025 at 11:46
> To: dev@flink.apache.org
> Subj
be
happy to help move it forward.
Please let me know what would be most helpful to make this happen.
Best regards,
Fred Teunissen
From: Ron Liu
Date: Saturday, 21 June 2025 at 11:46
To: dev@flink.apache.org
Subject: Re: [ANNOUNCE] Flink 2.1 feature freeze
Hi, Sergey
Make sense, +1 to merge.
Hi, Sergey
Make sense, +1 to merge.
Best,
Ron
Sergey Nuyanzin 于2025年6月21日周六 16:13写道：
> Hi Ron
>
> I was a bit late with merging [1]
> Can we merge this "Add API stability annotations (@Experimental,
> @PublicEvolving) to PyFlink APIs"
> ?
>
> [1] https://issues.apache.org/jira/browse/FLINK-373
Hi Ron
I was a bit late with merging [1]
Can we merge this "Add API stability annotations (@Experimental,
@PublicEvolving) to PyFlink APIs"
?
[1] https://issues.apache.org/jira/browse/FLINK-37365
On Sat, Jun 21, 2025 at 9:38 AM Ron Liu wrote:
>
> Hi, Hao
>
> I've understood the context, this is
Hi, Hao
I've understood the context, this is part of FLIP-525 and it's a
user-facing api change,
we should provide consistent usage to users on day one, makes sense,
I agree with merging this PR to release 2.1.
Best,
Ron
Hao Li 于2025年6月21日周六 13:01写道：
> Hi Ron,
>
> For FLIP-525, as discussed in
Hi, dev
The feature freeze of 2.1 has started now. That means that no new features
or improvements should now be merged into the master branch unless you ask
the release managers first, which has already been done for PRs, or pending
on CI to pass. Bug fixes and documentation PRs can still be merg
Hi Ron,
For FLIP-525, as discussed in [1], there's a config name change. I have a
PR [2] for it which needs to be merged into 2.1 release.
Thanks,
Hao
[1] https://lists.apache.org/thread/t979kpqs8v6zg5t8bgql3wwf27t7th9b
[2] https://github.com/apache/flink/pull/26706
On Fri, Jun 20, 2025 at 7:56
