Thanks Leonard for volunteering to release 1.13.3. I can also help from the PMC side if you need.
Best, Jark On Fri, 1 Oct 2021 at 10:32, Leonard Xu <[email protected]> wrote: > > From the SQL primary key issue side, all backports are merged. Feel free > to proceed with the release. > > > The changelog ordering mechanism is pretty important for SQL users, thanks > Timo for the backports effort. > > >> I can help Leonard with the PMC bits for the 1.13.3 release. > > Thanks Chesnay for the help from PMC side. > As the first week of October is a traditional holiday in China, many > developers, committers, and PMCs from China are on vacation, which may > result in not enough votes. I will start preparing for release first, and > start voting after they back to office. > > Best, > Leonard > > > > >> On 27/09/2021 21:26, Martijn Visser wrote: > >>> Hi Timo, > >>> > >>> Sounds good to me. > >>> > >>> However, I still need a PMC to make to the release. I definitely > volunteer > >>> to help out with keeping track of things, communication etc. Hopefully > >>> there's a PMC who can help. > >>> > >>> Best regards, > >>> > >>> Martijn > >>> > >>> Op ma 27 sep. 2021 om 11:32 schreef Timo Walther <[email protected]> > >>> > >>>> Hi Martijn, > >>>> > >>>> we are currently in the process of backporting a couple of PRs to the > >>>> 1.13 branch to fix the partially broken primary key support in Flink > >>>> SQL. See FLINK-20374 for more information. > >>>> > >>>> I hope we can finalize this in one or two days. It should be completed > >>>> in 1.13.3 to avoid confusion for backported commits that would spread > >>>> multiple releases otherwise. > >>>> > >>>> Thanks, > >>>> Timo > >>>> > >>>> On 24.09.21 07:44, Yun Tang wrote: > >>>>> Hi Martijn, > >>>>> > >>>>> Thanks for your reminder of FLINK-23519[1], this ticket has been > merged > >>>> in release-1.13 before but not yet merged into release-1.14 as we > have not > >>>> release Flink-1.14.0 officially. > >>>>> That's why the ticket is still in status IN-PROGRESS, and I think > this > >>>> would not block the release of flink-1.13.3. > >>>>> > >>>>> [1] https://issues.apache.org/jira/browse/FLINK-23519 > >>>>> > >>>>> Best > >>>>> Yun Tang > >>>>> ________________________________ > >>>>> From: Leonard Xu <[email protected]> > >>>>> Sent: Friday, September 24, 2021 10:22 > >>>>> To: +dev <[email protected]> > >>>>> Subject: Re: [DISCUSS] Releasing Flink 1.13.3 > >>>>> > >>>>> > >>>>>> 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? > >>>>> Hello, Matijn > >>>>> > >>>>> I am willing to help release 1.13.3 if possible, but maybe I need > some > >>>> assistance from PMC member. > >>>>> Best, > >>>>> Leonard > >>>>> > >>>>> > >>>>> > >>>>>> Best regards, > >>>>>> > >>>>>> Martijn > >>>>>> > >>>>>> On Thu, 23 Sept 2021 at 15:29, Yang Wang <[email protected]> > wrote: > >>>>>> > >>>>>>> FYI: I have merged FLINK-24315[1]. > >>>>>>> > >>>>>>> [1]. https://issues.apache.org/jira/browse/FLINK-24315 > >>>>>>> > >>>>>>> Best, > >>>>>>> Yang > >>>>>>> > >>>>>>> Yangze Guo <[email protected]> 于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 < > [email protected]> > >>>>>>>> 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 < > >>>> [email protected]> > >>>>>>>>> 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 > >>>>>>>>>> > >>>>>>>>>> [email protected] > >>>>>>>>>> > >>>>>>>>>> <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 > >>>>> > >>>> -- > >>> Martijn Visser | Product Manager > >>> > >>> [email protected] > >>> > >>> <https://www.ververica.com/> > >>> > >>> > >>> Follow us @VervericaData > >>> > >>> -- > >>> > >>> Join Flink Forward <https://flink-forward.org/> - The Apache Flink > >>> Conference > >>> > >>> Stream Processing | Event Driven | Real Time > >>> > > > >
