Re: Flink Releases

2024-09-09 Thread Aleksandr Pilipenko
Hi David, Shortcode {{all_versions}} is defined here [1] and relies on the configuration file [2] to get information about previous versions. I have created a ticket [3] with PR to address the missing version. 1 - https://github.com/apache/flink/blob/master/docs/layouts/shortcodes/all_versions.htm

Flink Releases

2024-09-05 Thread David Radley
Hi, I notice that https://nightlies.apache.org/flink/flink-docs-master/versions/ does not include 1.20. It seems that {{< all_versions >}} is not picking it up. I am happy to make the change, but could not see where to, Kind regards, David. Unless otherwise stated above: IBM Uni

[jira] [Created] (FLINK-25682) Check in script to verify cheksums and signatures for Apache Flink Releases

2022-01-17 Thread Konstantin Knauf (Jira)
Konstantin Knauf created FLINK-25682: Summary: Check in script to verify cheksums and signatures for Apache Flink Releases Key: FLINK-25682 URL: https://issues.apache.org/jira/browse/FLINK-25682

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-13 Thread Prasanna kumar
It would be good if docker images are released too . Prasanna. On Mon, 13 Dec 2021, 16:16 Jing Zhang, wrote: > +1 for the quick release. > > Till Rohrmann 于2021年12月13日周一 17:54写道: > > > +1 > > > > Cheers, > > Till > > > > On Mon, Dec 13, 2021 at 10:42 AM Jing Ge wrote: > > > > > +1 > > > > > >

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-13 Thread Jing Zhang
+1 for the quick release. Till Rohrmann 于2021年12月13日周一 17:54写道: > +1 > > Cheers, > Till > > On Mon, Dec 13, 2021 at 10:42 AM Jing Ge wrote: > > > +1 > > > > As I suggested to publish the blog post last week asap, users have been > > keen to have such urgent releases. Many thanks for it. > > > >

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-13 Thread Ada Luna
+1 I need 1.12.6, thanks Till Rohrmann 于2021年12月13日周一 17:54写道: > > +1 > > Cheers, > Till > > On Mon, Dec 13, 2021 at 10:42 AM Jing Ge wrote: > > > +1 > > > > As I suggested to publish the blog post last week asap, users have been > > keen to have such urgent releases. Many thanks for it. > > > >

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-13 Thread Till Rohrmann
+1 Cheers, Till On Mon, Dec 13, 2021 at 10:42 AM Jing Ge wrote: > +1 > > As I suggested to publish the blog post last week asap, users have been > keen to have such urgent releases. Many thanks for it. > > > > On Mon, Dec 13, 2021 at 8:29 AM Konstantin Knauf > wrote: > > > +1 > > > > I didn't

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-13 Thread Jing Ge
+1 As I suggested to publish the blog post last week asap, users have been keen to have such urgent releases. Many thanks for it. On Mon, Dec 13, 2021 at 8:29 AM Konstantin Knauf wrote: > +1 > > I didn't think this was necessary when I published the blog post on Friday, > but this has made hi

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-13 Thread Chesnay Schepler
I will start preparing the release candidates. On 12/12/2021 23:23, Stephan Ewen wrote: Hi all! Without doubt, you heard about the log4j vulnerability [1]. There is an advisory blog post on how to mitigate this in Apache Flink [2], which involves setting a config option and restarting the proc

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Konstantin Knauf
+1 I didn't think this was necessary when I published the blog post on Friday, but this has made higher waves than I expected over the weekend. On Mon, Dec 13, 2021 at 8:23 AM Yuan Mei wrote: > +1 for quick release. > > On Mon, Dec 13, 2021 at 2:55 PM Martijn Visser > wrote: > > > +1 to addr

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Yuan Mei
+1 for quick release. On Mon, Dec 13, 2021 at 2:55 PM Martijn Visser wrote: > +1 to address the issue like this > > On Mon, 13 Dec 2021 at 07:46, Jingsong Li wrote: > > > +1 for fixing it in these versions and doing quick releases. Looks good > to > > me. > > > > Best, > > Jingsong > > > > On M

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Martijn Visser
+1 to address the issue like this On Mon, 13 Dec 2021 at 07:46, Jingsong Li wrote: > +1 for fixing it in these versions and doing quick releases. Looks good to > me. > > Best, > Jingsong > > On Mon, Dec 13, 2021 at 2:18 PM Becket Qin wrote: > > > > +1. The solution sounds good to me. There have

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Jingsong Li
+1 for fixing it in these versions and doing quick releases. Looks good to me. Best, Jingsong On Mon, Dec 13, 2021 at 2:18 PM Becket Qin wrote: > > +1. The solution sounds good to me. There have been a lot of inquiries > about how to react to this. > > Thanks, > > Jiangjie (Becket) Qin > > On Mo

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Becket Qin
+1. The solution sounds good to me. There have been a lot of inquiries about how to react to this. Thanks, Jiangjie (Becket) Qin On Mon, Dec 13, 2021 at 12:40 PM Prasanna kumar < prasannakumarram...@gmail.com> wrote: > 1+ for making Updates for 1.12.5 . > We are looking for fix in 1.12 version.

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Prasanna kumar
1+ for making Updates for 1.12.5 . We are looking for fix in 1.12 version. Please notify once the fix is done. On Mon, Dec 13, 2021 at 9:45 AM Leonard Xu wrote: > +1 for the quick release and the special vote period 24h. > > > 2021年12月13日 上午11:49,Dian Fu 写道: > > > > +1 for the proposal and cre

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Leonard Xu
+1 for the quick release and the special vote period 24h. > 2021年12月13日 上午11:49,Dian Fu 写道: > > +1 for the proposal and creating a quick release. > > Regards, > Dian > > > On Mon, Dec 13, 2021 at 11:15 AM Kyle Bendickson wrote: > >> +1 to doing a release for this widely publicized vulnerabi

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Dian Fu
+1 for the proposal and creating a quick release. Regards, Dian On Mon, Dec 13, 2021 at 11:15 AM Kyle Bendickson wrote: > +1 to doing a release for this widely publicized vulnerability. > > In my experience, users will often update to the latest minor patch version > without much fuss. Plus, u

Re: [DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Kyle Bendickson
+1 to doing a release for this widely publicized vulnerability. In my experience, users will often update to the latest minor patch version without much fuss. Plus, users have also likely heard about this and will appreciate a simple fix (updating their version where possible). The work-around wi

[DISCUSS] Immediate dedicated Flink releases for log4j vulnerability

2021-12-12 Thread Stephan Ewen
Hi all! Without doubt, you heard about the log4j vulnerability [1]. There is an advisory blog post on how to mitigate this in Apache Flink [2], which involves setting a config option and restarting the processes. That is fortunately a relatively simple fix. Despite this workaround, I think we sh

[jira] [Created] (FLINK-24517) Streamline Flink releases

2021-10-12 Thread Chesnay Schepler (Jira)
Chesnay Schepler created FLINK-24517: Summary: Streamline Flink releases Key: FLINK-24517 URL: https://issues.apache.org/jira/browse/FLINK-24517 Project: Flink Issue Type: Technical Debt

Re: [ANNOUNCE] Kinesis connector becomes part of Flink releases

2019-09-03 Thread vino yang
1, Bowen Li wrote: > >> Hi all, >> >> I'm glad to announce that, as #9494 >> <https://github.com/apache/flink/pull/9494>was merged today, >> flink-connector-kinesis is officially of Apache 2.0 license now in master >> branch and its artifact will

Re: [ANNOUNCE] Kinesis connector becomes part of Flink releases

2019-09-01 Thread Yu Li
pull/9494>was merged today, > flink-connector-kinesis is officially of Apache 2.0 license now in master > branch and its artifact will be deployed to Maven central as part of Flink > releases starting from Flink 1.10.0. Users can use the artifact out of > shelf then and no longer have to

[ANNOUNCE] Kinesis connector becomes part of Flink releases

2019-08-30 Thread Bowen Li
Hi all, I'm glad to announce that, as #9494 <https://github.com/apache/flink/pull/9494>was merged today, flink-connector-kinesis is officially of Apache 2.0 license now in master branch and its artifact will be deployed to Maven central as part of Flink releases starting from Flink 1.