Hi Weijie,

Thanks for your effort and sharing the status!

Best regards,
Jing

On Fri, May 19, 2023 at 11:50 AM weijie guo <guoweijieres...@gmail.com>
wrote:

> Hi Jing,
>
> Thank you for your attention!
>
> I have cut off the code for release-1.17.1-rc1 and started deploying it to
> the apache repository, while preparing the pull request for the blog post.
> The specific released time depends on the speed at which they are
> completed. VOTE thread will be launched no later than next Monday at the
> latest.
>
> Best regards,
>
> Weijie
>
>
> Jing Ge <j...@ververica.com.invalid> 于2023年5月19日周五 14:48写道:
>
> > Hi Weijie,
> >
> > just wondering how the process is going. Will the RC1 be released today?
> > Thanks for driving this!
> >
> > Best regards,
> > Jing
> >
> > On Wed, May 17, 2023 at 5:02 AM weijie guo <guoweijieres...@gmail.com>
> > wrote:
> >
> > > Hi Kevin,
> > >
> > > If everything goes smoothly, I will release the RC1 version of 1.17.1
> > this
> > > Thursday or Friday.
> > >
> > > Best regards,
> > >
> > > Weijie
> > >
> > >
> > > Kevin Lam <kevin....@shopify.com.invalid> 于2023年5月16日周二 22:53写道:
> > >
> > > > Hi! Thanks for doing this release. I'm looking forward to some of the
> > bug
> > > > fixes, is there a date set for the release of 1.17.1?
> > > >
> > > > On Mon, May 15, 2023 at 6:10 AM Lijie Wang <wangdachui9...@gmail.com
> >
> > > > wrote:
> > > >
> > > > > +1 for the release.
> > > > >
> > > > > Best,
> > > > > Lijie
> > > > >
> > > > > Jing Ge <j...@ververica.com.invalid> 于2023年5月15日周一 17:07写道:
> > > > >
> > > > > > +1 for releasing 1.17.1
> > > > > >
> > > > > > Best Regards,
> > > > > > Jing
> > > > > >
> > > > > > On Thu, May 11, 2023 at 10:03 AM Martijn Visser <
> > > > > martijnvis...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > +1, thanks for volunteering!
> > > > > > >
> > > > > > > On Thu, May 11, 2023 at 9:23 AM Xintong Song <
> > > tonysong...@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > +1
> > > > > > > >
> > > > > > > > I'll help with the steps that require PMC privileges.
> > > > > > > >
> > > > > > > > Best,
> > > > > > > >
> > > > > > > > Xintong
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, May 11, 2023 at 3:12 PM Jingsong Li <
> > > > jingsongl...@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > +1 for releasing 1.17.1
> > > > > > > > >
> > > > > > > > > Best,
> > > > > > > > > Jingsong
> > > > > > > > >
> > > > > > > > > On Thu, May 11, 2023 at 1:29 PM Gyula Fóra <
> > > gyula.f...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > +1 for the release
> > > > > > > > > >
> > > > > > > > > > Gyula
> > > > > > > > > >
> > > > > > > > > > On Thu, 11 May 2023 at 05:35, Yun Tang <myas...@live.com
> >
> > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > +1 for release flink-1.17.1
> > > > > > > > > > >
> > > > > > > > > > > The blocker issue might cause silent incorrect data,
> it's
> > > > > better
> > > > > > to
> > > > > > > > > have a
> > > > > > > > > > > fix release ASAP.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Best
> > > > > > > > > > > Yun Tang
> > > > > > > > > > > ________________________________
> > > > > > > > > > > From: weijie guo <guoweijieres...@gmail.com>
> > > > > > > > > > > Sent: Thursday, May 11, 2023 11:08
> > > > > > > > > > > To: dev@flink.apache.org <dev@flink.apache.org>;
> > > > > > > > tonysong...@gmail.com
> > > > > > > > > <
> > > > > > > > > > > tonysong...@gmail.com>
> > > > > > > > > > > Subject: [DISCUSS] Release Flink 1.17.1
> > > > > > > > > > >
> > > > > > > > > > > Hi all,
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I would like to discuss creating a new 1.17 patch
> release
> > > > > > (1.17.1).
> > > > > > > > The
> > > > > > > > > > > last 1.17 release is nearly two months old, and since
> > then,
> > > > 66
> > > > > > > > tickets
> > > > > > > > > have
> > > > > > > > > > > been closed [1], of which 14 are blocker/critical [2].
> > > Some
> > > > of
> > > > > > > them
> > > > > > > > > are
> > > > > > > > > > > quite important, such as FLINK-31293 [3] and
> FLINK-32027
> > > > [4].
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > I am not aware of any unresolved blockers and there are
> > no
> > > > > > > > in-progress
> > > > > > > > > > > tickets [5].
> > > > > > > > > > > Please let me know if there are any issues you'd like
> to
> > be
> > > > > > > included
> > > > > > > > in
> > > > > > > > > > > this release but still not merged.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > If the community agrees to create this new patch
> > release, I
> > > > > could
> > > > > > > > > > > volunteer as the release manager
> > > > > > > > > > >  and Xintong can help with actions that require a PMC
> > role.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > >
> > > > > > > > > > > Weijie
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > [1]
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/FLINK-32027?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.17.1%20%20and%20resolution%20%20!%3D%20%20Unresolved%20order%20by%20priority%20DESC
> > > > > > > > > > >
> > > > > > > > > > > [2]
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/browse/FLINK-31273?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.17.1%20and%20resolution%20%20!%3D%20Unresolved%20%20and%20priority%20in%20(Blocker%2C%20Critical)%20ORDER%20by%20priority%20%20DESC
> > > > > > > > > > >
> > > > > > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-31293
> > > > > > > > > > >
> > > > > > > > > > > [4] https://issues.apache.org/jira/browse/FLINK-32027
> > > > > > > > > > >
> > > > > > > > > > > [5]
> > > > > > >
> https://issues.apache.org/jira/projects/FLINK/versions/12352886
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

Reply via email to