Thanks for the kicking off. +1 for Zhijiang & Piotr (if he agrees to) being the release managers. Thanks for the volunteering. +1 for the *anticipated feature freeze date* end of April
Thank you~ Xintong Song On Thu, Feb 20, 2020 at 10:30 AM Yuan Mei <yuanmei.w...@gmail.com> wrote: > +1 > > 3-month sounds a very reasonable duration for a release. > > On Thu, Feb 20, 2020 at 9:53 AM tison <wander4...@gmail.com> wrote: > > > Thanks for kicking off the discussion Stephan! > > > > +1 for the *anticipated feature freeze date* end of April and > > Zhijiang & Piotr to be the release managers. > > > > Best, > > tison. > > > > > > Dian Fu <dian0511...@gmail.com> 于2020年2月20日周四 上午9:41写道： > > > > > Thanks Stephan kicking off this discussion and Zhijiang volunteering as > > > one of the release managers. > > > > > > +1 for the "feature freeze date" around end of April. There are still > > more > > > than 2 months left, so I think it's a reasonable time. > > > > > > Thanks, > > > Dian > > > > > > > 在 2020年2月19日，下午10:52，Aljoscha Krettek <aljos...@apache.org> 写道： > > > > > > > > +1 > > > > > > > > Although I would hope that it can be more than just "anticipated". > > > > > > > > Best, > > > > Aljoscha > > > > > > > > On 19.02.20 15:40, Till Rohrmann wrote: > > > >> Thanks for volunteering as one of our release managers Zhijiang. > > > >> +1 for the *anticipated feature freeze date* end of April. As we go > > > along > > > >> and collect more data points we might be able to strengthen our > > > >> initial anticipation. > > > >> Cheers, > > > >> Till > > > >> On Wed, Feb 19, 2020 at 4:44 AM Zhijiang < > wangzhijiang...@aliyun.com > > > .invalid> > > > >> wrote: > > > >>> Thanks for kicking off the next release and the introduction, > > @Stephan! > > > >>> > > > >>> It's my pleasure to become the release manager and involve in other > > > >>> community works. I am working together with @Piotr for a long time, > > so > > > >>> very happy to cooperate for the release manager work again. The > > > previous > > > >>> release work was always well done, and I can learn a lot from these > > > rich > > > >>> experiences. > > > >>> > > > >>> +1 for the "feature freeze date" around end of April. > > > >>> Although we have the FF SF in the meantime, fortunately there are > no > > > long > > > >>> public holidays during this period in China. > > > >>> > > > >>> Best, > > > >>> Zhijiang > > > >>> > > > >>> > > > >>> ------------------------------------------------------------------ > > > >>> From:Stephan Ewen <se...@apache.org> > > > >>> Send Time:2020 Feb. 19 (Wed.) 01:15 > > > >>> To:dev <dev@flink.apache.org> > > > >>> Cc:zhijiang <zhiji...@apache.org>; pnowojski <pnowoj...@apache.org > > > > > >>> Subject:[DISCUSS] Kicking off the 1.11 release cycle > > > >>> > > > >>> Hi all! > > > >>> > > > >>> Now that the 1.10 release is out (congrats again, everyone!), I > > wanted > > > to > > > >>> bring up some questions about organizing the next release cycle. > > > >>> > > > >>> The most important questions at the beginning would be > > > >>> - Who would volunteer as Release Managers > > > >>> - When would be the release date. > > > >>> > > > >>> For the release managers, Piotrek and Zhijiang have mentioned > > > previously > > > >>> that they would be interested, so I am copying them here to chime > in. > > > >>> @Piotr and @Zhijiang could you confirm if you are interested in > > helping > > > >>> out with this? > > > >>> > > > >>> About the release date: By our original "3 months release cycle" > > > >>> assumption, we should aim for a release **Mid May**, meaning a > > feature > > > >>> freeze no later than end of April. > > > >>> That would be indeed a shorter release cycle than 1.10, and the > > > assumption > > > >>> of a shorter testing period. But aiming for a shorter release cycle > > > than > > > >>> 1.10 would actually be nice, in my opinion. 1.10 grew very big in > the > > > end, > > > >>> which caused also a very long testing period (plus Christmas and > > > Chinese > > > >>> New Year are also partially to blame). > > > >>> > > > >>> The exact feature freeze date is anyways a community discussion > > later, > > > but > > > >>> what do you think about starting with an "anticipated feature > freeze > > > date" > > > >>> around end of April, so that committers, contributors, and users > know > > > >>> roughly what to expect? > > > >>> > > > >>> Best, > > > >>> Stephan > > > >>> > > > >>> > > > >>> > > > > > > > > >
