[DISCUSS] Planning Flink 1.18

2023-03-24 Thread Konstantin Knauf
Hi everyone, "Nach dem Spiel ist vor dem Spiel" [1] aka "There is always a next release". With the announcement of Flink 1.17, we have entered the next release cycle and with it comes the usual routine: - Release Managers I'd like to volunteer as one of the release managers this time. It has bee

Re: [DISCUSS] Planning Flink 1.18

2023-03-24 Thread Jing Ge
Hi Konstantin, Qingsheng and I would love to participate and join you as release managers for 1.18. Speaking of the timeline, since we will have a big feature release with 1.18, a feature freeze in the middle of July would be better. It is also not far from your proposal. Best regards, Jing On

Re: [DISCUSS] Planning Flink 1.18

2023-03-24 Thread Qingsheng Ren
Hi Konstantin, Thanks for kicking off 1.18! As mentioned by Jing we’d like to participate in the new cycle, and hope my experience in 1.17 could help. About the feature freezing date, I’m also thinking to set it around mid July. 1.18 will be a larger release with more features to work with compar

Re: [DISCUSS] Planning Flink 1.18

2023-03-24 Thread Sergey Nuyanzin
Thanks for starting the discussion about Flink 1.18. I would be interested in helping out around the release as well. On Sat, Mar 25, 2023 at 2:20 AM Qingsheng Ren wrote: > Hi Konstantin, > > Thanks for kicking off 1.18! As mentioned by Jing we’d like to participate > in the new cycle, and hope

Re: [DISCUSS] Planning Flink 1.18

2023-03-24 Thread Yun Tang
Sent: Saturday, March 25, 2023 9:46 To: dev@flink.apache.org Cc: Jing Ge ; Konstantin Knauf Subject: Re: [DISCUSS] Planning Flink 1.18 Thanks for starting the discussion about Flink 1.18. I would be interested in helping out around the release as well. On Sat, Mar 25, 2023 at 2:20 AM Qingshen

Re: [DISCUSS] Planning Flink 1.18

2023-03-27 Thread Matthias Pohl
.13.2 and also be interested in helping to release > the next major Flink-1.18 version. > > > Best > Yun Tang > > From: Sergey Nuyanzin > Sent: Saturday, March 25, 2023 9:46 > To: dev@flink.apache.org > Cc: Jing Ge ; Konstantin Knau

Re: [DISCUSS] Planning Flink 1.18

2023-03-29 Thread Qingsheng Ren
. > > > > > > Best > > Yun Tang > > > > From: Sergey Nuyanzin > > Sent: Saturday, March 25, 2023 9:46 > > To: dev@flink.apache.org > > Cc: Jing Ge ; Konstantin Knauf > > Subject: Re: [DISCUSS] Planning Flink

Re: [DISCUSS] Planning Flink 1.18

2023-03-29 Thread Leonard Xu
sion. >>> >>> I'm not sure whether I am a bit late here. I had experience on releasing >>> minor version of Flink-1.13.2 and also be interested in helping to >> release >>> the next major Flink-1.18 version. >>> >>> >>> Be

Re: [DISCUSS] Planning Flink 1.18

2023-03-30 Thread Martijn Visser
On Sat, Mar 25, 2023 at 4:00 AM Yun Tang wrote: > >> > >>> Thanks for kick off the discussion. > >>> > >>> I'm not sure whether I am a bit late here. I had experience on > releasing > >>> minor version of Flink-1.13.2 and also be interested in helpi

Re: [DISCUSS] Planning Flink 1.18

2023-04-01 Thread Jark Wu
Sat, Mar 25, 2023 at 4:00 AM Yun Tang wrote: >>>> >>>>> Thanks for kick off the discussion. >>>>> >>>>> I'm not sure whether I am a bit late here. I had experience on >> releasing >>>>> minor version of Flink-1.13.2 an

Re: [DISCUSS] Planning Flink 1.18

2023-04-04 Thread Jing Ge
t;> not > >>>> spam this thread with 1.17-related stuff. > >>>> > >>>> [1] https://lists.apache.org/thread/1mdbpdo42df4642wtmf91b26p8v2qtbf > >>>> > >>>> > >>>> On Sat, Mar 25, 2023 at 4:00 AM Yun Tang wrote: &