+1  for the proposed release managers and feature freeze on Jan 26
sounds good to me.

Best.
Jark

On Mon, 30 Oct 2023 at 12:15, Xintong Song <tonysong...@gmail.com> wrote:

> Thanks for kicking this off.
>
> +1 for the proposed release managers (Lincoln, Yun, Jing and Martijn) and
> targeting date (feature freeze: Jan 26).
>
> I'd like to bring up that it is likely many efforts in the 1.19 release
> cycle are also related to the 2.0 release. I think it would be better if
> the 1.19 and 2.0 RMs can track these efforts jointly rather than
> separately. It would be appreciated if you can also involve us for the 1.19
> discussions & syncs.
>
> Best,
>
> Xintong
>
>
>
> On Sun, Oct 29, 2023 at 5:30 PM Leonard Xu <xbjt...@gmail.com> wrote:
>
> > Thanks everyone for volunteering. +1 for Lincoln, Yun Tang, Jing and
> > Martijn as release managers from my side.
> >
> > The combination of experienced release managers and new release managers
> > can help community cultivate more committers with version management
> > experience.
> >
> > Best,
> > Leonard
> >
> > > 2023年10月27日 下午5:22,Matthias Pohl <matthias.p...@aiven.io.INVALID> 写道:
> > >
> > > +1 from my side for Lincoln, Yun Tang, Jing and Martijn as release
> > managers.
> > > Thanks everyone for volunteering.
> > >
> > > I tried to collect the different tasks that are part of release
> > management
> > > in [1]. It might help to identify responsibilities. Feel free to have a
> > > look and/or update it. Ideally, it will help others to decide whether
> > they
> > > feel ready to contribute to the community as release managers in future
> > > releases.
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Flink+Release+Management
> > >
> > >
> > > On Thu, Oct 26, 2023 at 9:15 PM Martijn Visser
> > <mvis...@confluent.io.invalid>
> > > wrote:
> > >
> > >> Hi Lincoln and Yun,
> > >>
> > >> Happy to jump on board as release manager too :)
> > >>
> > >> Best regards,
> > >>
> > >> Martijn
> > >>
> > >> Op do 26 okt 2023 om 20:50 schreef Jing Ge <j...@ververica.com.invalid
> >
> > >>
> > >>> Hi Lincoln,
> > >>>
> > >>> Thanks for kicking off 1.19! I got a lot of experience as a release
> > >> manager
> > >>> for the 1.18 release. I would like to join you and participate in the
> > >> 1.19
> > >>> release cycle.
> > >>>
> > >>> Best regards,
> > >>> Jing
> > >>>
> > >>> On Thu, Oct 26, 2023 at 6:27 PM Lincoln Lee <lincoln.8...@gmail.com>
> > >>> wrote:
> > >>>
> > >>>> Hi everyone,
> > >>>>
> > >>>> With the release announcement of Flink 1.18, it’s a good time to
> kick
> > >> off
> > >>>> discussion of the next release 1.19.
> > >>>>
> > >>>> - Release managers
> > >>>>
> > >>>> Yun Tang and I would like to volunteer as release managers for 1.19,
> > >> and
> > >>>> it would be great to have someone else working together on this
> > >> release.
> > >>>> Please let us know if you have any interest!
> > >>>>
> > >>>> - Timeline
> > >>>>
> > >>>> Flink 1.18 has been released. With a target release cycle of 4
> months,
> > >> we
> > >>>> propose a feature freeze date of *Jan 26, 2024*.
> > >>>>
> > >>>> - Collecting features
> > >>>>
> > >>>> As usual, we've created a wiki page[1] for collecting new features
> in
> > >>> 1.19.
> > >>>> In addition, we already have a number of FLIPs that have been voted
> or
> > >>> are
> > >>>> in
> > >>>> the process, including pre-works for version 2.0.
> > >>>> In the meantime, the release management team will be finalized in
> the
> > >>> next
> > >>>> few days,
> > >>>> and we'll continue to create Jira Boards and Sync meetings to make
> it
> > >>> easy
> > >>>> for
> > >>>> everyone to get an overview and track progress.
> > >>>>
> > >>>> 1. https://cwiki.apache.org/confluence/display/FLINK/1.19+Release
> > >>>>
> > >>>> Best,
> > >>>> Lincoln Lee
> > >>>>
> > >>>
> > >>
> >
> >
>

Reply via email to