FLINK-26985 was discovered just before last weekend. We will get it resolved first thing after the holiday (tomorrow).
Best Yuan On Tue, Apr 5, 2022 at 5:37 PM Yun Gao <yungao...@aliyun.com.invalid> wrote: > Hi Robert, > > Very sorry for the long delay before the rc1 could be published. > > For the open critical issues, I previously checked with the owners of the > issues > that they are optional to the release, thus the only blocker issue is the > FLINK-26985. > > Besides to the blocker issues we are waiting for the release blog to be > done. As a whole, > if there is no new blocker issues that must be fixed, both of the current > blockers are expected > to be finished as soon as possible inside this week and we'll create the > rc1 immediately > after that. We'll also put more efforts to track and address the remaining > blockers. > > Best, > Yun Gao > > > ------------------------------------------------------------------ > From:Robert Metzger <metrob...@gmail.com> > Send Time:2022 Apr. 5 (Tue.) 13:34 > To:dev <dev@flink.apache.org> > Subject:Re: Flink 1.15 Stabilisation Sync > > Thanks a lot for the update. > > From the burndown board [1] it seems that there's only one blocker left, > which has already a fix in review [2]. > Are we also planning to address the open Critical tickets before opening > the first voting release candidate? > When do you expect 1.15 to be out? > > [1] > > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=505&view=detail&selectedIssue=FLINK-26985 > [2] https://issues.apache.org/jira/browse/FLINK-26985 > > > On Mon, Mar 28, 2022 at 11:18 PM Johannes Moser <j...@ververica.com> wrote: > > > Dear Community, > > > > We are fairly on track with stabilising the 1.15 release, that’s why Yun > > Gao and me think we don’t need the sync anymore. > > > > So we skip it for now, starting from tomorrow. If the situation might > > change. We will let you know. > > > > Best, > > Joe > >
