+1 to feature freeze the 1.17 release on 1.17 (smile), and thanks all for volunteering as our release managers.
Looking forward to the soon-released 1.16.0 and the detailed feature plan for 1.17. Best Regards, Yu On Fri, 21 Oct 2022 at 20:17, Jing Ge <j...@ververica.com> wrote: > +1 > The plan looks rational. Thanks for your effort! > > Best regards, > Jing > > On Fri, Oct 21, 2022 at 1:16 PM Congxian Qiu <qcx978132...@gmail.com> > wrote: > > > Thanks for kicking off the 1.17 release, and volunteers as release > > managers. > > > > +1 to the feature freeze date > > > > Best, > > Congxian > > > > > > Yun Tang <myas...@live.com> 于2022年10月21日周五 17:24写道： > > > > > Thanks, Qingsheng and Leonard to kick off the release plan of > flink-1.17, > > > which targets a feature freeze date of January 17th 🙂. > > > > > > +1 to include Martijn and Matthias as the release managers. > > > > > > Best, > > > Yun Tang > > > ________________________________ > > > From: Piotr Nowojski <pnowoj...@apache.org> > > > Sent: Friday, October 21, 2022 16:22 > > > To: dev@flink.apache.org <dev@flink.apache.org> > > > Subject: Re: [DISCUSS] Planning Flink 1.17 > > > > > > Hi, > > > > > > Thanks for kicking this discussion off Qingsheng and Leonard. I like > the > > > January 17th, 2023 touch :) > > > > > > 1 for including Matthias Pohl and Martijn Visser as release managers. > > > > > > Best, > > > Piotrek > > > Always alright > > > > > > pt., 21 paź 2022 o 05:55 Yuan Mei <yuanmei.w...@gmail.com> napisał(a): > > > > > > > Thanks, Qingsheng for the kicking-off efforts. > > > > > > > > 1. January 17th, 2023 as feature freeze data sounds reasonable to me. > > > > 2. We will input our plan to the wiki link. > > > > > > > > Thanks > > > > > > > > Best > > > > Yuan > > > > Ververica (Alibaba) > > > > > > > > > > > > On Fri, Oct 21, 2022 at 10:38 AM Xingbo Huang <h...@apache.org> > wrote: > > > > > > > > > Thanks Qingsheng, Leonard and Martijn for starting the discussion > and > > > > > volunteering. > > > > > The timeline proposal sounds reasonable :+1: > > > > > > > > > > Best, > > > > > Xingbo > > > > > > > > > > Jark Wu <imj...@gmail.com> 于2022年10月21日周五 00:17写道： > > > > > > > > > > > Thanks for kicking off the 1.17 release. > > > > > > > > > > > > Targeting feature freeze on 1/17 for 1.17 release sounds pretty > > good > > > to > > > > > me. > > > > > > +1 for the volunteers as release managers. > > > > > > > > > > > > Best, > > > > > > Jark > > > > > > Ververica (Alibaba) > > > > > > > > > > > > On Thu, 20 Oct 2022 at 18:09, Matthias Pohl < > > matthias.p...@aiven.io > > > > > > .invalid> > > > > > > wrote: > > > > > > > > > > > > > Thanks for starting the discussion about Flink 1.17. I would be > > > > > > interested > > > > > > > in helping out around the release as well. > > > > > > > > > > > > > > Best, > > > > > > > Matthias > > > > > > > > > > > > > > On Thu, Oct 20, 2022 at 12:07 PM Xintong Song < > > > tonysong...@gmail.com > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > Thanks for kicking this off. > > > > > > > > > > > > > > > > +1 for the proposed timeline. > > > > > > > > > > > > > > > > Also +1 for Qingsheng, Leonard and Martijn as the release > > > managers. > > > > > > > Thanks > > > > > > > > for volunteering. > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > > > > Xintong > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Thu, Oct 20, 2022 at 3:59 PM Martijn Visser < > > > > > > martijnvis...@apache.org > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > Hi Qingsheng, > > > > > > > > > > > > > > > > > > I'm definitely interested in participating as a release > > manager > > > > > > again. > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > Martijn > > > > > > > > > > > > > > > > > > On Thu, Oct 20, 2022 at 9:47 AM Qingsheng Ren < > > > re...@apache.org> > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > > > > > > > As we are approaching the official release of Flink 1.16, > > > it’s > > > > a > > > > > > good > > > > > > > > > time > > > > > > > > > > to kick off some discussions and march toward 1.17. > > > > > > > > > > > > > > > > > > > > - Release managers > > > > > > > > > > > > > > > > > > > > Leonard Xu and I would like to volunteer as release > > managers > > > > for > > > > > > > 1.17, > > > > > > > > > and > > > > > > > > > > it would be great to have someone else working together > on > > > this > > > > > > > > release. > > > > > > > > > > Please let us know if you have any interest! > > > > > > > > > > > > > > > > > > > > - Timeline > > > > > > > > > > > > > > > > > > > > Having 1.16 will be released in the next few days and > the 4 > > > > > months > > > > > > > > > release > > > > > > > > > > cycle after that, we propose to set the feature freezing > > date > > > > on > > > > > > > > *January > > > > > > > > > > 17th, 2023* (aligned with our version number 1.17 :-)), > so > > > that > > > > > > > > everyone > > > > > > > > > > could enjoy the holiday season and Chinese new year. > > > > > > > > > > > > > > > > > > > > - What we’ll be focusing > > > > > > > > > > > > > > > > > > > > Similar to our previous releases, we’d like to keep an > eye > > on > > > > the > > > > > > > > > > timeline, CI stability, release testing, and any > > > communication > > > > > and > > > > > > > > > > coordination across teams and developers. One thing we’d > > like > > > > to > > > > > > > > mention > > > > > > > > > in > > > > > > > > > > particular is compatibility, which is a frequent > complaint > > > from > > > > > our > > > > > > > > > > ecosystem developers and users. We encourage all > committers > > > to > > > > do > > > > > > an > > > > > > > > > extra > > > > > > > > > > manual check to see if any public interface is touched > > before > > > > > > > merging a > > > > > > > > > PR. > > > > > > > > > > We could discuss details in another thread later and > update > > > the > > > > > > > > > > contributing guidelines to list which should be treated > as > > > > public > > > > > > > APIs. > > > > > > > > > > Please feel free to raise any discussions if you have > > > anything > > > > > else > > > > > > > to > > > > > > > > > > emphasize specifically. > > > > > > > > > > > > > > > > > > > > - Collecting features > > > > > > > > > > > > > > > > > > > > We'll create a wiki page under this directory[1] for > > > collecting > > > > > new > > > > > > > > > > features targeted in 1.17 as we always did before to give > > > > > everyone > > > > > > an > > > > > > > > > > overview and track the progress. Please don’t hesitate to > > > share > > > > > > your > > > > > > > > > ideas > > > > > > > > > > on the page. In the meantime, we’d like to kindly invite > > our > > > > > > > committers > > > > > > > > > to > > > > > > > > > > think about and plan what we could deliver to developers > > and > > > > > users > > > > > > in > > > > > > > > > this > > > > > > > > > > release. > > > > > > > > > > > > > > > > > > > > Looking forward to working with you all in the coming > 1.17 > > > > > release! > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > Qingsheng Ren and Leonard Xu > > > > > > > > > > Ververica (Alibaba) > > > > > > > > > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/Release+Management+and+Feature+Plan > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
