; > > > [1] https://cwiki.apache.org/confluence/display/FLINK/2.0+Release
> > > > > [2]
> > > > >
> > > > >
> > > >
> >
> https://newrelic.com/sites/default/files/2024-04/new-relic-state-of-the-java-ecosystem-report-2024-04-3
gt;
> > > >
> > >
> https://newrelic.com/sites/default/files/2024-04/new-relic-state-of-the-java-ecosystem-report-2024-04-30.pdf
> > > >
> > > > On Tue, Jun 25, 2024 at 4:58 AM David Radley <
> david_rad...@uk.ibm.com>
> > > > wr
overed
> > > > elsewhere, but it would be good to be clear how this effects the
> > > connectors
> > > > and operator repos, with potentially v1 and v2 oriented new featuresI
> > > > suspect this will be a connector by connector investigation. I am
> > >
e a connector by connector investigation. I am
> > thinking
> > > connectors with Hadoop eco-system dependencies (e.g. Paimon) which may
> > not
> > > work nicely with Java 17,
> > >
> > > Kind regards, David.
> > >
> > >
> > &g
l
> > Date: Tuesday, 25 June 2024 at 09:57
> > To: dev@flink.apache.org
> > Cc: Xintong Song , martijnvis...@apache.org <
> > martijnvis...@apache.org>, imj...@gmail.com ,
> > becket@gmail.com
> > Subject: [EXTERNAL] [2.0] How to handle on-going feat
> Kind regards, David.
>
>
> From: Matthias Pohl
> Date: Tuesday, 25 June 2024 at 09:57
> To: dev@flink.apache.org
> Cc: Xintong Song , martijnvis...@apache.org <
> martijnvis...@apache.org>, imj...@gmail.com ,
> becket@gmail.com
> Subject: [EXT
@gmail.com
Subject: [EXTERNAL] [2.0] How to handle on-going feature development in Flink
2.0?
Hi 2.0 release managers,
With the 1.20 release branch being cut [1], master is now referring to
2.0-SNAPSHOT. I remember that, initially, the community had the idea of
keeping the 2.0 release as small
Hi 2.0 release managers,
With the 1.20 release branch being cut [1], master is now referring to
2.0-SNAPSHOT. I remember that, initially, the community had the idea of
keeping the 2.0 release as small as possible focusing on API changes [2].
What does this mean for new features? I guess blocking t
