Re: Flink 1.17.2 planned?

2023-10-23 Thread Deepyaman Datta
Hi Jing,

My team and I have been blocked by the need for a PyFlink release including
https://github.com/apache/flink/pull/23141, and I saw that you mentioned
that anybody can be the release manager of a bug fix release. Could we
explore what it would take for me to do this (assuming nobody is already
handling the release)?

Best regards,
Deepyaman


Re: Flink 1.17.2 planned?

2023-08-23 Thread Jing Ge via user
Hi Christian,

Thanks for your understanding. We will take a look at 1.17.2, once the 1.18
release is done. In the meantime, there might be someone in the community
who volunteers to be the 1.17.2 release manager. You will see related email
threads on the Dev. Stay tuned please :-)

Best regards,
Jing

On Wed, Aug 23, 2023 at 9:27 AM Christian Lorenz 
wrote:

> Hi Jing,
>
>
>
> thanks for the answer. I have no idea what kind of work is needed for
> being a release manager. I think we’ll have to wait for the release then
> (if really urgent, the blocking bug can also be patched by us).
>
>
>
> Kind regards,
>
> Christian
>
>
>
> *Von: *Jing Ge via user 
> *Datum: *Dienstag, 22. August 2023 um 11:40
> *An: *liu ron 
> *Cc: *user@flink.apache.org 
> *Betreff: *Re: Flink 1.17.2 planned?
>
> This email has reached Mapp via an external source
>
>
>
> Hi Christian,
>
>
>
> Thanks for reaching out. Liked Ron pointed out that the community is
> focusing on the 1.18 release. If you are facing urgent issues, would you
> like to volunteer as the release manager of 1.17.2 and drive the release?
> Theoretically, everyone could be the release manager of a bugs fix release.
>
>
>
> Best regards,
>
> Jing
>
>
>
> On Tue, Aug 22, 2023 at 3:41 AM liu ron  wrote:
>
> Hi, Christian
>
>
>
> We released 1.17.1 [1] in May, and the main focus of the community is
> currently on the 1.18 release, so 1.17.2 should be planned for after the
> 1.18 release!
>
>
>
> [1]
> https://flink.apache.org/2023/05/25/apache-flink-1.17.1-release-announcement/
>
>
>
>
>
> Best,
>
> Ron
>
>
>
> Christian Lorenz via user  于2023年8月21日周一 17:33写道:
>
> Hi team,
>
>
>
> are there any infos about a bugfix release 1.17.2 available? E.g. will
> there be another bugfix release of 1.17 / approximate timing?
>
> We are hit by https://issues.apache.org/jira/browse/FLINK-32296 which
> leads to wrong SQL responses in some circumstances.
>
>
>
> Kind regards,
>
> Christian
>
> This e-mail is from Mapp Digital Group and its international legal
> entities and may contain information that is confidential.
> If you are not the intended recipient, do not read, copy or distribute the
> e-mail or any attachments. Instead, please notify the sender and delete the
> e-mail and any attachments.
>
> This e-mail is from Mapp Digital Group and its international legal
> entities and may contain information that is confidential.
> If you are not the intended recipient, do not read, copy or distribute the
> e-mail or any attachments. Instead, please notify the sender and delete the
> e-mail and any attachments.
>


Re: Flink 1.17.2 planned?

2023-08-22 Thread Jing Ge via user
Hi Christian,

Thanks for reaching out. Liked Ron pointed out that the community is
focusing on the 1.18 release. If you are facing urgent issues, would you
like to volunteer as the release manager of 1.17.2 and drive the release?
Theoretically, everyone could be the release manager of a bugs fix release.

Best regards,
Jing

On Tue, Aug 22, 2023 at 3:41 AM liu ron  wrote:

> Hi, Christian
>
> We released 1.17.1 [1] in May, and the main focus of the community is
> currently on the 1.18 release, so 1.17.2 should be planned for after the
> 1.18 release!
>
> [1]
> https://flink.apache.org/2023/05/25/apache-flink-1.17.1-release-announcement/
>
>
> Best,
> Ron
>
> Christian Lorenz via user  于2023年8月21日周一 17:33写道:
>
>> Hi team,
>>
>>
>>
>> are there any infos about a bugfix release 1.17.2 available? E.g. will
>> there be another bugfix release of 1.17 / approximate timing?
>>
>> We are hit by https://issues.apache.org/jira/browse/FLINK-32296 which
>> leads to wrong SQL responses in some circumstances.
>>
>>
>>
>> Kind regards,
>>
>> Christian
>>
>> This e-mail is from Mapp Digital Group and its international legal
>> entities and may contain information that is confidential.
>> If you are not the intended recipient, do not read, copy or distribute
>> the e-mail or any attachments. Instead, please notify the sender and delete
>> the e-mail and any attachments.
>>
>


Re: Flink 1.17.2 planned?

2023-08-21 Thread liu ron
Hi, Christian

We released 1.17.1 [1] in May, and the main focus of the community is
currently on the 1.18 release, so 1.17.2 should be planned for after the
1.18 release!

[1]
https://flink.apache.org/2023/05/25/apache-flink-1.17.1-release-announcement/


Best,
Ron

Christian Lorenz via user  于2023年8月21日周一 17:33写道:

> Hi team,
>
>
>
> are there any infos about a bugfix release 1.17.2 available? E.g. will
> there be another bugfix release of 1.17 / approximate timing?
>
> We are hit by https://issues.apache.org/jira/browse/FLINK-32296 which
> leads to wrong SQL responses in some circumstances.
>
>
>
> Kind regards,
>
> Christian
>
> This e-mail is from Mapp Digital Group and its international legal
> entities and may contain information that is confidential.
> If you are not the intended recipient, do not read, copy or distribute the
> e-mail or any attachments. Instead, please notify the sender and delete the
> e-mail and any attachments.
>


Flink 1.17.2 planned?

2023-08-21 Thread Christian Lorenz via user
Hi team,

are there any infos about a bugfix release 1.17.2 available? E.g. will there be 
another bugfix release of 1.17 / approximate timing?
We are hit by https://issues.apache.org/jira/browse/FLINK-32296 which leads to 
wrong SQL responses in some circumstances.

Kind regards,
Christian
This e-mail is from Mapp Digital Group and its international legal entities and 
may contain information that is confidential.
If you are not the intended recipient, do not read, copy or distribute the 
e-mail or any attachments. Instead, please notify the sender and delete the 
e-mail and any attachments.