Hey,

> Did you mean skip 4.1.1, since 4.1.0 has already been released?

I meant skip "4.1.0-1.18" since we could release this with the existing
source. We will additionally skip 4.1.1 and jump to 4.2.0 since this
version has features it should be a minor version rather than a patch [1].

> Does this imply that the 4.1.x series will be reserved for Flink 1.17,
and the 4.2.x series will correspond to Flink 1.18?

4.1.x will receive bug fixes for Flink 1.17.
4.2.x will receive bug fixes and features for Flink 1.17 and 1.18.

Thanks,
Danny

[1] https://semver.org/


On Mon, Oct 30, 2023 at 3:47 PM Samrat Deb <decordea...@gmail.com> wrote:

> Hi Danny ,
>
> Thank you for driving it.
>
> +1 (non binding )
>
>
> >  I am proposing we skip 4.1.0 for Flink 1.18 and go
> straight to 4.2.0.
>
> Does this imply that the 4.1.x series will be reserved for Flink 1.17, and
> the 4.2.x series will correspond to Flink 1.18?
>
> Bests,
> Samrat
>
>
> On Mon, Oct 30, 2023 at 7:32 PM Jing Ge <j...@ververica.com.invalid>
> wrote:
>
> > Hi Danny,
> >
> > +1 Thanks for driving it. Did you mean skip 4.1.1, since 4.1.0 has
> already
> > been released?
> >
> > Best regards,
> > Jing
> >
> > On Mon, Oct 30, 2023 at 11:49 AM Danny Cranmer <dannycran...@apache.org>
> > wrote:
> >
> > > Hello all,
> > >
> > > I would like to start the discussion to release Apache Flink AWS
> > connectors
> > > v4.2.0. We released v4.1.0 over six months ago on 2023-04-03. Since
> then
> > we
> > > have resolved 23 issues [1]. Additionally now Flink 1.18 is live we
> need
> > to
> > > add support for this. I am proposing we skip 4.1.0 for Flink 1.18 and
> go
> > > straight to 4.2.0. The CI is stable [2].
> > >
> > > I volunteer myself as the release manager.
> > >
> > > Thanks,
> > > Danny
> > >
> > > [1]
> > >
> > >
> >
> https://issues.apache.org/jira/browse/FLINK-33021?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012315522%20AND%20fixVersion%20%3D%2012353011%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
> > > [2] https://github.com/apache/flink-connector-aws/actions
> > >
> >
>

Reply via email to