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
> > >
> > >
+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.
> >
> >
+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.
> >
> >
+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
+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
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
+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
+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
+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
+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
+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.
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
+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
+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
+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
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
16 matches
Mail list logo
