Hi all, @Konstantin thanks for the extra information, I agree. @Yangze thanks for mentioning that ticket, that's indeed also an important fix. @Yang thanks for the update and merging FLINK-24315.
My conclusion would be that there are no tickets open right now which would block a 1.13.3 release. I only need a PMC member who would like to manage the release. Anyone? Best regards, Martijn On Thu, 23 Sept 2021 at 15:29, Yang Wang <danrtsey...@gmail.com> wrote: > FYI: I have merged FLINK-24315[1]. > > [1]. https://issues.apache.org/jira/browse/FLINK-24315 > > Best, > Yang > > Yangze Guo <karma...@gmail.com> 于2021年9月23日周四 上午11:17写道： > > > Thanks for driving this discussion, Martijn. +1 for releasing Flink > 1.13.3. > > In addition to the issues already listed, > > https://issues.apache.org/jira/browse/FLINK-24005 is also an important > > fix. > > > > Regarding FLINK-24315, @Yang Wang will help with the review. It is > > likely to be merged this week, if not, I don't think it should block > > the release. > > > > Best, > > Yangze Guo > > > > > > On Wed, Sep 22, 2021 at 8:44 PM Konstantin Knauf <kna...@apache.org> > > wrote: > > > > > > Hi Martijn, > > > > > > Thanks for starting the discussion. +1 for a soon Flink 1.13.3. IMHO we > > > don't need to block the release on FLINK-23519 (an improvement), > > > FLINK-21853 (seems like a Minor issue with a test) or FLINK-23946 > > (depends > > > on https://issues.apache.org/jira/browse/FLINK-23946, which is not > > started > > > yet). This would leave FLINK-24315, which I can't judge at all. > > > > > > Cheers, > > > > > > Konstantin > > > > > > On Wed, Sep 22, 2021 at 1:34 PM Martijn Visser <mart...@ververica.com> > > > wrote: > > > > > > > Hi all, > > > > > > > > I would like to start discussing releasing Flink 1.13.3. There are > > > > currently 138 tickets already resolved for 1.13.3, a few important > > fixes > > > > are: > > > > > > > > * https://issues.apache.org/jira/browse/FLINK-24347 (KafkaSource > > cannot > > > > checkpoint if the parallelism is higher than the partition number) > > > > * https://issues.apache.org/jira/browse/FLINK-24303 > (SourceCoordinator > > > > exception may fail Session Cluster) > > > > * https://issues.apache.org/jira/browse/FLINK-24277 (Offset commit > > should > > > > be disabled if consumer group ID is not specified in KafkaSource) > > > > * https://issues.apache.org/jira/browse/FLINK-23802 (Reduce > > > > ReadTimeoutExceptions for Kinesis Consumer) > > > > > > > > There are currently 4 tickets with fix version 1.13.3 that are in > > progress: > > > > > > > > * https://issues.apache.org/jira/browse/FLINK-24315 (Cannot rebuild > > > > watcher > > > > thread while the K8S API server is unavailable) > > > > * https://issues.apache.org/jira/browse/FLINK-23946 (Application > mode > > > > fails > > > > fatally when being shut down) > > > > * https://issues.apache.org/jira/browse/FLINK-23519 (Aggregate State > > > > Backend Latency by State Level) > > > > * https://issues.apache.org/jira/browse/FLINK-21853 (Running HA > > per-job > > > > cluster (rocks, non-incremental) end-to-end test could not finished > in > > 900 > > > > seconds) > > > > > > > > Can Yangze, David, Yun and Till give an update on the status for > those? > > > > > > > > Are there any other open tickets that we should wait for? Is there a > > PMC > > > > member who would like to manage the release? > > > > > > > > Best regards, > > > > > > > > Martijn Visser | Product Manager > > > > > > > > mart...@ververica.com > > > > > > > > <https://www.ververica.com/> > > > > > > > > > > > > Follow us @VervericaData > > > > > > > > -- > > > > > > > > Join Flink Forward <https://flink-forward.org/> - The Apache Flink > > > > Conference > > > > > > > > Stream Processing | Event Driven | Real Time > > > > > > > > > > > > > -- > > > > > > Konstantin Knauf > > > > > > https://twitter.com/snntrable > > > > > > https://github.com/knaufk > > >
