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 <h...@confluent.io.invalid> 于2025年6月21日周六 13:01写道:

> 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 PM Ron Liu <ron9....@gmail.com> wrote:
>
> > 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 merged.
> >
> >
> > - *Cutting release branch*
> >
> > Currently we have no blocker issues(beside tickets that used for
> > release-testing).
> >
> > We are planning to cut the release branch on next Wednesday (June 25) if
> > no new test instabilities, and we'll make another announcement in the
> > dev mailing list then.
> >
> >
> > - *Cross-team testing*
> >
> > The release testing will start right after we cut the release branch,
> which
> > is expected to come in the next week. As a prerequisite of it, please
> > complete the documentation of your new feature and mark the related JIRA
> > issue in the 2.1 release wiki page [1] before we start testing, which
> > would be quite helpful for other developers to validate your features.
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/FLINK/2.1+Release
> >
> > Best,
> > Ron
> >
>

Reply via email to