Re: [ANNOUNCE] Flink 1.18 feature freeze
Hi, I would like to ask if releasing the external HBase connector and remove those modules from the core Flink repo before Flink 1.18 sounds feasible at this point or not? The connector source is ready for quite a while, I externalized the E2E tests a couple weeks before and CI is passing so in theory there is no remaining task to release the connector. Martijn manages the tasks regarding connector externalization, but he is on holiday at the moment, so if this is something that can be done, is there anyone who can help with the connector release? I volunteer to help. Thanks, Ferenc --- Original Message --- On Wednesday, August 2nd, 2023 at 03:27, Jing Ge wrote: > > > Hi, > > Thanks for keeping us in the loop. +1 for merging these PRs. > > @Alex Please feel free to contact us for CR and PR merges. > > @Matthias the Pekko migration is an important task, since it is related to > CVE issues. Thanks for bringing it to our attention. > > Best regards, > Jing > > > > On Tue, Aug 1, 2023 at 5:23 PM Qingsheng Ren re...@apache.org wrote: > > > Thanks for letting us know, Matthias! > > > > As discussed in the release sync, +1 for merging these PRs. > > > > Best, > > Qingsheng > > > > On Tue, Aug 1, 2023 at 5:17 PM Matthias Pohl matthias.p...@aiven.io > > wrote: > > > > > I'm requesting to merge in FLINK-32098 [1]. It's a minor change that > > > reduces the amount of exists calls to S3 while submitting a job (which > > > can > > > be an expensive operation if the object actually doesn't exist but the > > > corresponding bucket itself contains a lot of objects). The PR is > > > reviewed > > > and ready to be merged. The change itself is minor and covered by > > > existing > > > tests. > > > > > > Additionally, I want to mention the two already merged (after > > > feature-freeze) changes: > > > - FLINK-32583 [2] which is a minor bugfix. I didn't explicitly mention it > > > initially because of the fact that it fixes a bug (which admittedly was > > > already present in older versions of Flink). I'm happy to revert that one > > > if the release managers have concerns. It's fixing a scenario where the > > > RestClient becomes unresponsive when submitting a request in rare cases. > > > - Migration from Akka to Pekko (FLINK-32468 [3], FLINK-32683 [4]): This > > > was agreed on in last week's 1.18 release sync. I just forgot to make it > > > public on the ML. The Pekko change will be "release-tested" as part of > > > FLINK-32678 stress test. > > > > > > Matthias > > > > > > [1] https://issues.apache.org/jira/browse/FLINK-32098 > > > [2] https://issues.apache.org/jira/browse/FLINK-32583 > > > [3] https://issues.apache.org/jira/browse/FLINK-32468 > > > [4] https://issues.apache.org/jira/browse/FLINK-32683 > > > [5] https://issues.apache.org/jira/browse/FLINK-32678 > > > > > > On Tue, Aug 1, 2023 at 10:58 AM Qingsheng Ren re...@apache.org wrote: > > > > > > > Thanks for letting us know, Alexander and Leonard! > > > > > > > > I checked these PRs and the changes are trivial. +1 for merging them. > > > > > > > > Best, > > > > Qingsheng > > > > > > > > On Tue, Aug 1, 2023 at 12:14 AM Leonard Xu xbjt...@gmail.com wrote: > > > > > > > > > Thank all Release Managers for driving the 1.18 release work! > > > > > > > > > > > - Deprecation works for 2.0 > > > > > > > > > > > > As discussed in another thread [3], we will not give extra > > > > > > extensions > > > > > > to > > > > > > deprecation works considering the overhead and potential side > > > > > > effects > > > > > > to > > > > > > the timeline of 1.18. We can accept tiny changes that only add > > > > > > annotations > > > > > > and JavaDocs, but please let us know before you are going to do > > > > > > that. > > > > > > > > > > Alexander and I ready to deprecate SourceFunction APIs as above > > > > > discussion > > > > > thread[1][2], now we apply the permission to merge following three > > > > > PRs : > > > > > > > > > > The first two PRs [3][4] only contains @Deprecated annotations and > > > > > JavaDocs, the PR[5] contains @Deprecated annotations, JavaDocs, and > > > > > necessary tiny changes for example code as some examples with strict > > > > > deprecation compiler checks to SourceFunction API, it should be okay > > > > > as > > > > > it > > > > > only changed example code, you can check the tiny change in this > > > > > commit[5]. > > > > > > > > > > Best, > > > > > Alexander and Leonard > > > > > > > > > > [1]https://lists.apache.org/thread/yyw52k45x2sp1jszldtdx7hc98n72w7k > > > > > [2]https://lists.apache.org/thread/kv9rj3w2rmkb8jtss5bqffhw57or7v8v > > > > > [3]https://github.com/apache/flink/pull/23106 > > > > > [4]https://github.com/apache/flink/pull/23079 > > > > > [5]https://github.com/apache/flink/pull/23105 > > > > > [6] > > > > https://github.com/apache/flink/pull/23079/commits/f5ea3c073d36f21fb4fe47e83c717ac080995509
Re: [ANNOUNCE] Flink 1.18 feature freeze
Hi, Thanks for keeping us in the loop. +1 for merging these PRs. @Alex Please feel free to contact us for CR and PR merges. @Matthias the Pekko migration is an important task, since it is related to CVE issues. Thanks for bringing it to our attention. Best regards, Jing On Tue, Aug 1, 2023 at 5:23 PM Qingsheng Ren wrote: > Thanks for letting us know, Matthias! > > As discussed in the release sync, +1 for merging these PRs. > > Best, > Qingsheng > > On Tue, Aug 1, 2023 at 5:17 PM Matthias Pohl > wrote: > > > I'm requesting to merge in FLINK-32098 [1]. It's a minor change that > > reduces the amount of exists calls to S3 while submitting a job (which > can > > be an expensive operation if the object actually doesn't exist but the > > corresponding bucket itself contains a lot of objects). The PR is > reviewed > > and ready to be merged. The change itself is minor and covered by > existing > > tests. > > > > Additionally, I want to mention the two already merged (after > > feature-freeze) changes: > > - FLINK-32583 [2] which is a minor bugfix. I didn't explicitly mention it > > initially because of the fact that it fixes a bug (which admittedly was > > already present in older versions of Flink). I'm happy to revert that one > > if the release managers have concerns. It's fixing a scenario where the > > RestClient becomes unresponsive when submitting a request in rare cases. > > - Migration from Akka to Pekko (FLINK-32468 [3], FLINK-32683 [4]): This > > was agreed on in last week's 1.18 release sync. I just forgot to make it > > public on the ML. The Pekko change will be "release-tested" as part of > > FLINK-32678 stress test. > > > > Matthias > > > > [1] https://issues.apache.org/jira/browse/FLINK-32098 > > [2] https://issues.apache.org/jira/browse/FLINK-32583 > > [3] https://issues.apache.org/jira/browse/FLINK-32468 > > [4] https://issues.apache.org/jira/browse/FLINK-32683 > > [5] https://issues.apache.org/jira/browse/FLINK-32678 > > > > On Tue, Aug 1, 2023 at 10:58 AM Qingsheng Ren wrote: > > > >> Thanks for letting us know, Alexander and Leonard! > >> > >> I checked these PRs and the changes are trivial. +1 for merging them. > >> > >> Best, > >> Qingsheng > >> > >> On Tue, Aug 1, 2023 at 12:14 AM Leonard Xu wrote: > >> > >> > Thank all Release Managers for driving the 1.18 release work! > >> > > >> > > - Deprecation works for 2.0 > >> > > > >> > > As discussed in another thread [3], we will not give extra > extensions > >> to > >> > > deprecation works considering the overhead and potential side > effects > >> to > >> > > the timeline of 1.18. We can accept tiny changes that only add > >> > annotations > >> > > and JavaDocs, but please let us know before you are going to do > that. > >> > > >> > Alexander and I ready to deprecate SourceFunction APIs as above > >> discussion > >> > thread[1][2], now we apply the permission to merge following three > PRs : > >> > > >> > The first two PRs [3][4] only contains @Deprecated annotations and > >> > JavaDocs, the PR[5] contains @Deprecated annotations, JavaDocs, and > >> > necessary tiny changes for example code as some examples with strict > >> > deprecation compiler checks to SourceFunction API, it should be okay > as > >> it > >> > only changed example code, you can check the tiny change in this > >> commit[5]. > >> > > >> > Best, > >> > Alexander and Leonard > >> > > >> > [1]https://lists.apache.org/thread/yyw52k45x2sp1jszldtdx7hc98n72w7k > >> > [2]https://lists.apache.org/thread/kv9rj3w2rmkb8jtss5bqffhw57or7v8v > >> > [3]https://github.com/apache/flink/pull/23106 > >> > [4]https://github.com/apache/flink/pull/23079 > >> > [5]https://github.com/apache/flink/pull/23105 > >> > [6] > >> > > >> > https://github.com/apache/flink/pull/23079/commits/f5ea3c073d36f21fb4fe47e83c717ac080995509 > >> > > >> > > >> > > >
Re: [ANNOUNCE] Flink 1.18 feature freeze
Thanks for letting us know, Matthias! As discussed in the release sync, +1 for merging these PRs. Best, Qingsheng On Tue, Aug 1, 2023 at 5:17 PM Matthias Pohl wrote: > I'm requesting to merge in FLINK-32098 [1]. It's a minor change that > reduces the amount of exists calls to S3 while submitting a job (which can > be an expensive operation if the object actually doesn't exist but the > corresponding bucket itself contains a lot of objects). The PR is reviewed > and ready to be merged. The change itself is minor and covered by existing > tests. > > Additionally, I want to mention the two already merged (after > feature-freeze) changes: > - FLINK-32583 [2] which is a minor bugfix. I didn't explicitly mention it > initially because of the fact that it fixes a bug (which admittedly was > already present in older versions of Flink). I'm happy to revert that one > if the release managers have concerns. It's fixing a scenario where the > RestClient becomes unresponsive when submitting a request in rare cases. > - Migration from Akka to Pekko (FLINK-32468 [3], FLINK-32683 [4]): This > was agreed on in last week's 1.18 release sync. I just forgot to make it > public on the ML. The Pekko change will be "release-tested" as part of > FLINK-32678 stress test. > > Matthias > > [1] https://issues.apache.org/jira/browse/FLINK-32098 > [2] https://issues.apache.org/jira/browse/FLINK-32583 > [3] https://issues.apache.org/jira/browse/FLINK-32468 > [4] https://issues.apache.org/jira/browse/FLINK-32683 > [5] https://issues.apache.org/jira/browse/FLINK-32678 > > On Tue, Aug 1, 2023 at 10:58 AM Qingsheng Ren wrote: > >> Thanks for letting us know, Alexander and Leonard! >> >> I checked these PRs and the changes are trivial. +1 for merging them. >> >> Best, >> Qingsheng >> >> On Tue, Aug 1, 2023 at 12:14 AM Leonard Xu wrote: >> >> > Thank all Release Managers for driving the 1.18 release work! >> > >> > > - Deprecation works for 2.0 >> > > >> > > As discussed in another thread [3], we will not give extra extensions >> to >> > > deprecation works considering the overhead and potential side effects >> to >> > > the timeline of 1.18. We can accept tiny changes that only add >> > annotations >> > > and JavaDocs, but please let us know before you are going to do that. >> > >> > Alexander and I ready to deprecate SourceFunction APIs as above >> discussion >> > thread[1][2], now we apply the permission to merge following three PRs : >> > >> > The first two PRs [3][4] only contains @Deprecated annotations and >> > JavaDocs, the PR[5] contains @Deprecated annotations, JavaDocs, and >> > necessary tiny changes for example code as some examples with strict >> > deprecation compiler checks to SourceFunction API, it should be okay as >> it >> > only changed example code, you can check the tiny change in this >> commit[5]. >> > >> > Best, >> > Alexander and Leonard >> > >> > [1]https://lists.apache.org/thread/yyw52k45x2sp1jszldtdx7hc98n72w7k >> > [2]https://lists.apache.org/thread/kv9rj3w2rmkb8jtss5bqffhw57or7v8v >> > [3]https://github.com/apache/flink/pull/23106 >> > [4]https://github.com/apache/flink/pull/23079 >> > [5]https://github.com/apache/flink/pull/23105 >> > [6] >> > >> https://github.com/apache/flink/pull/23079/commits/f5ea3c073d36f21fb4fe47e83c717ac080995509 >> > >> > >> >
Re: [ANNOUNCE] Flink 1.18 feature freeze
I'm requesting to merge in FLINK-32098 [1]. It's a minor change that reduces the amount of exists calls to S3 while submitting a job (which can be an expensive operation if the object actually doesn't exist but the corresponding bucket itself contains a lot of objects). The PR is reviewed and ready to be merged. The change itself is minor and covered by existing tests. Additionally, I want to mention the two already merged (after feature-freeze) changes: - FLINK-32583 [2] which is a minor bugfix. I didn't explicitly mention it initially because of the fact that it fixes a bug (which admittedly was already present in older versions of Flink). I'm happy to revert that one if the release managers have concerns. It's fixing a scenario where the RestClient becomes unresponsive when submitting a request in rare cases. - Migration from Akka to Pekko (FLINK-32468 [3], FLINK-32683 [4]): This was agreed on in last week's 1.18 release sync. I just forgot to make it public on the ML. The Pekko change will be "release-tested" as part of FLINK-32678 stress test. Matthias [1] https://issues.apache.org/jira/browse/FLINK-32098 [2] https://issues.apache.org/jira/browse/FLINK-32583 [3] https://issues.apache.org/jira/browse/FLINK-32468 [4] https://issues.apache.org/jira/browse/FLINK-32683 [5] https://issues.apache.org/jira/browse/FLINK-32678 On Tue, Aug 1, 2023 at 10:58 AM Qingsheng Ren wrote: > Thanks for letting us know, Alexander and Leonard! > > I checked these PRs and the changes are trivial. +1 for merging them. > > Best, > Qingsheng > > On Tue, Aug 1, 2023 at 12:14 AM Leonard Xu wrote: > > > Thank all Release Managers for driving the 1.18 release work! > > > > > - Deprecation works for 2.0 > > > > > > As discussed in another thread [3], we will not give extra extensions > to > > > deprecation works considering the overhead and potential side effects > to > > > the timeline of 1.18. We can accept tiny changes that only add > > annotations > > > and JavaDocs, but please let us know before you are going to do that. > > > > Alexander and I ready to deprecate SourceFunction APIs as above > discussion > > thread[1][2], now we apply the permission to merge following three PRs : > > > > The first two PRs [3][4] only contains @Deprecated annotations and > > JavaDocs, the PR[5] contains @Deprecated annotations, JavaDocs, and > > necessary tiny changes for example code as some examples with strict > > deprecation compiler checks to SourceFunction API, it should be okay as > it > > only changed example code, you can check the tiny change in this > commit[5]. > > > > Best, > > Alexander and Leonard > > > > [1]https://lists.apache.org/thread/yyw52k45x2sp1jszldtdx7hc98n72w7k > > [2]https://lists.apache.org/thread/kv9rj3w2rmkb8jtss5bqffhw57or7v8v > > [3]https://github.com/apache/flink/pull/23106 > > [4]https://github.com/apache/flink/pull/23079 > > [5]https://github.com/apache/flink/pull/23105 > > [6] > > > https://github.com/apache/flink/pull/23079/commits/f5ea3c073d36f21fb4fe47e83c717ac080995509 > > > > >
Re: [ANNOUNCE] Flink 1.18 feature freeze
Thanks for letting us know, Alexander and Leonard! I checked these PRs and the changes are trivial. +1 for merging them. Best, Qingsheng On Tue, Aug 1, 2023 at 12:14 AM Leonard Xu wrote: > Thank all Release Managers for driving the 1.18 release work! > > > - Deprecation works for 2.0 > > > > As discussed in another thread [3], we will not give extra extensions to > > deprecation works considering the overhead and potential side effects to > > the timeline of 1.18. We can accept tiny changes that only add > annotations > > and JavaDocs, but please let us know before you are going to do that. > > Alexander and I ready to deprecate SourceFunction APIs as above discussion > thread[1][2], now we apply the permission to merge following three PRs : > > The first two PRs [3][4] only contains @Deprecated annotations and > JavaDocs, the PR[5] contains @Deprecated annotations, JavaDocs, and > necessary tiny changes for example code as some examples with strict > deprecation compiler checks to SourceFunction API, it should be okay as it > only changed example code, you can check the tiny change in this commit[5]. > > Best, > Alexander and Leonard > > [1]https://lists.apache.org/thread/yyw52k45x2sp1jszldtdx7hc98n72w7k > [2]https://lists.apache.org/thread/kv9rj3w2rmkb8jtss5bqffhw57or7v8v > [3]https://github.com/apache/flink/pull/23106 > [4]https://github.com/apache/flink/pull/23079 > [5]https://github.com/apache/flink/pull/23105 > [6] > https://github.com/apache/flink/pull/23079/commits/f5ea3c073d36f21fb4fe47e83c717ac080995509 > >
Re: [ANNOUNCE] Flink 1.18 feature freeze
Thank all Release Managers for driving the 1.18 release work! > - Deprecation works for 2.0 > > As discussed in another thread [3], we will not give extra extensions to > deprecation works considering the overhead and potential side effects to > the timeline of 1.18. We can accept tiny changes that only add annotations > and JavaDocs, but please let us know before you are going to do that. Alexander and I ready to deprecate SourceFunction APIs as above discussion thread[1][2], now we apply the permission to merge following three PRs : The first two PRs [3][4] only contains @Deprecated annotations and JavaDocs, the PR[5] contains @Deprecated annotations, JavaDocs, and necessary tiny changes for example code as some examples with strict deprecation compiler checks to SourceFunction API, it should be okay as it only changed example code, you can check the tiny change in this commit[5]. Best, Alexander and Leonard [1]https://lists.apache.org/thread/yyw52k45x2sp1jszldtdx7hc98n72w7k [2]https://lists.apache.org/thread/kv9rj3w2rmkb8jtss5bqffhw57or7v8v [3]https://github.com/apache/flink/pull/23106 [4]https://github.com/apache/flink/pull/23079 [5]https://github.com/apache/flink/pull/23105 [6] https://github.com/apache/flink/pull/23079/commits/f5ea3c073d36f21fb4fe47e83c717ac080995509
[ANNOUNCE] Flink 1.18 feature freeze
Hi everyone, The feature freeze of 1.18 has started now. That means that no new features or improvements should now be merged into the master branch unless you ask the release managers first, which has already been done for PRs, or pending on CI to pass. Bug fixes and documentation PRs can still be merged. - Cutting release branch Currently we have several CI instability issues, and will try to close them in the coming week. We are planning to cut the release branch on next Tuesday (Aug 1), and we'll make another announcement in the dev mailing list then. - Cross-team testing The release testing will start right after we cut the release branch, which is expected to come in the next week. As a prerequisite of it, please complete the documentation of your new feature and mark the related JIRA issue in the 1.18 release wiki page [1] before we start testing, which would be quite helpful for other developers to validate your features. - Release syncs We'll switch to weekly release sync starting from next Tuesday, so the next release sync will be on Aug 1, 2023. Feel free to join us [2]! - Deprecation works for 2.0 As discussed in another thread [3], we will not give extra extensions to deprecation works considering the overhead and potential side effects to the timeline of 1.18. We can accept tiny changes that only add annotations and JavaDocs, but please let us know before you are going to do that. [1] https://cwiki.apache.org/confluence/display/FLINK/1.18+Release [2] https://us04web.zoom.us/j/79158702091?pwd=8CXPqxMzbabWkma5b0qFXI1IcLbxBh.1 [3] https://lists.apache.org/thread/zbzgyc9ds1sx7931z6cv5hkfmng580d6 Best regards, Jing, Konstantin, Sergey and Qingsheng
Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023
Thanks for driving the release and sharing the update, looking forward to 1.18 Best, Shammon FY On Fri, Jul 7, 2023 at 10:56 AM Yun Tang wrote: > Thanks for driving this release and sharing the update on the feature > freeze extension. > > > Best > Yun Tang > > From: Jing Ge > Sent: Thursday, July 6, 2023 17:13 > To: yuxia > Cc: dev ; re...@apache.org ; > snuyan...@gmail.com ; Konstantin Knauf < > kna...@apache.org> > Subject: Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July > 24th, 2023 > > Thanks for driving it and sharing the update! > > Best regards, > Jing > > On Thu, Jul 6, 2023 at 9:21 AM yuxia wrote: > > > Thanks for the update and thanks for your efforts. > > > > Best regards, > > Yuxia > > > > - 原始邮件 - > > 发件人: "Rui Fan" <1996fan...@gmail.com> > > 收件人: "dev" , re...@apache.org > > 抄送: "Jing Ge" , snuyan...@gmail.com, "Konstantin > > Knauf" > > 发送时间: 星期四, 2023年 7 月 06日 下午 3:06:28 > > 主题: Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, > 2023 > > > > Thanks for the update, and thank you for your efforts for the 1.18 > release! > > > > Best, > > Rui Fan > > > > On Thu, Jul 6, 2023 at 2:40 PM Qingsheng Ren wrote: > > > > > Hi devs, > > > > > > Recently we collected some feedback from developers, and in order to > give > > > more time for polishing some important features in 1.18, we decide to > > > extend the feature freezing date to: > > > > > > July 24th, 2023, at 00:00 CEST(UTC+2) > > > > > > which gives us ~2 weeks for development from now. There will be no > > > extension after Jul 24, so please arrange new features in the next > > release > > > if they cannot be finished before the closing date. > > > > > > Thanks everyone for your work in 1.18! > > > > > > Best regards, > > > Qingsheng, Jing, Konstantin and Sergey > > > > > >
Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023
Thanks for driving this release and sharing the update on the feature freeze extension. Best Yun Tang From: Jing Ge Sent: Thursday, July 6, 2023 17:13 To: yuxia Cc: dev ; re...@apache.org ; snuyan...@gmail.com ; Konstantin Knauf Subject: Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023 Thanks for driving it and sharing the update! Best regards, Jing On Thu, Jul 6, 2023 at 9:21 AM yuxia wrote: > Thanks for the update and thanks for your efforts. > > Best regards, > Yuxia > > - 原始邮件 - > 发件人: "Rui Fan" <1996fan...@gmail.com> > 收件人: "dev" , re...@apache.org > 抄送: "Jing Ge" , snuyan...@gmail.com, "Konstantin > Knauf" > 发送时间: 星期四, 2023年 7 月 06日 下午 3:06:28 > 主题: Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023 > > Thanks for the update, and thank you for your efforts for the 1.18 release! > > Best, > Rui Fan > > On Thu, Jul 6, 2023 at 2:40 PM Qingsheng Ren wrote: > > > Hi devs, > > > > Recently we collected some feedback from developers, and in order to give > > more time for polishing some important features in 1.18, we decide to > > extend the feature freezing date to: > > > > July 24th, 2023, at 00:00 CEST(UTC+2) > > > > which gives us ~2 weeks for development from now. There will be no > > extension after Jul 24, so please arrange new features in the next > release > > if they cannot be finished before the closing date. > > > > Thanks everyone for your work in 1.18! > > > > Best regards, > > Qingsheng, Jing, Konstantin and Sergey > > >
Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023
Thanks for driving it and sharing the update! Best regards, Jing On Thu, Jul 6, 2023 at 9:21 AM yuxia wrote: > Thanks for the update and thanks for your efforts. > > Best regards, > Yuxia > > - 原始邮件 - > 发件人: "Rui Fan" <1996fan...@gmail.com> > 收件人: "dev" , re...@apache.org > 抄送: "Jing Ge" , snuyan...@gmail.com, "Konstantin > Knauf" > 发送时间: 星期四, 2023年 7 月 06日 下午 3:06:28 > 主题: Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023 > > Thanks for the update, and thank you for your efforts for the 1.18 release! > > Best, > Rui Fan > > On Thu, Jul 6, 2023 at 2:40 PM Qingsheng Ren wrote: > > > Hi devs, > > > > Recently we collected some feedback from developers, and in order to give > > more time for polishing some important features in 1.18, we decide to > > extend the feature freezing date to: > > > > July 24th, 2023, at 00:00 CEST(UTC+2) > > > > which gives us ~2 weeks for development from now. There will be no > > extension after Jul 24, so please arrange new features in the next > release > > if they cannot be finished before the closing date. > > > > Thanks everyone for your work in 1.18! > > > > Best regards, > > Qingsheng, Jing, Konstantin and Sergey > > >
Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023
Thanks for the update and thanks for your efforts. Best regards, Yuxia - 原始邮件 - 发件人: "Rui Fan" <1996fan...@gmail.com> 收件人: "dev" , re...@apache.org 抄送: "Jing Ge" , snuyan...@gmail.com, "Konstantin Knauf" 发送时间: 星期四, 2023年 7 月 06日 下午 3:06:28 主题: Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023 Thanks for the update, and thank you for your efforts for the 1.18 release! Best, Rui Fan On Thu, Jul 6, 2023 at 2:40 PM Qingsheng Ren wrote: > Hi devs, > > Recently we collected some feedback from developers, and in order to give > more time for polishing some important features in 1.18, we decide to > extend the feature freezing date to: > > July 24th, 2023, at 00:00 CEST(UTC+2) > > which gives us ~2 weeks for development from now. There will be no > extension after Jul 24, so please arrange new features in the next release > if they cannot be finished before the closing date. > > Thanks everyone for your work in 1.18! > > Best regards, > Qingsheng, Jing, Konstantin and Sergey >
Re: [ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023
Thanks for the update, and thank you for your efforts for the 1.18 release! Best, Rui Fan On Thu, Jul 6, 2023 at 2:40 PM Qingsheng Ren wrote: > Hi devs, > > Recently we collected some feedback from developers, and in order to give > more time for polishing some important features in 1.18, we decide to > extend the feature freezing date to: > > July 24th, 2023, at 00:00 CEST(UTC+2) > > which gives us ~2 weeks for development from now. There will be no > extension after Jul 24, so please arrange new features in the next release > if they cannot be finished before the closing date. > > Thanks everyone for your work in 1.18! > > Best regards, > Qingsheng, Jing, Konstantin and Sergey >
[ANNOUNCE] Flink 1.18 Feature Freeze Extended until July 24th, 2023
Hi devs, Recently we collected some feedback from developers, and in order to give more time for polishing some important features in 1.18, we decide to extend the feature freezing date to: July 24th, 2023, at 00:00 CEST(UTC+2) which gives us ~2 weeks for development from now. There will be no extension after Jul 24, so please arrange new features in the next release if they cannot be finished before the closing date. Thanks everyone for your work in 1.18! Best regards, Qingsheng, Jing, Konstantin and Sergey
