You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Martijn Visser <ma...@ververica.com> on 2022/02/01 12:26:35 UTC
Re: [DISCUSS] Releasing Flink 1.13.6
Hi Konstantin,
Thanks for volunteering! There are no Blockers for 1.13.6 so you should be
good to go for creating a release candidate.
Best regards,
Martijn
On Wed, 26 Jan 2022 at 08:32, Jing Zhang <be...@gmail.com> wrote:
> +1 for releasing Flink 1.13.6
> Thanks Martijn and Konstantin for driving this.
>
> Best,
> Jing Zhang
>
> David Morávek <dm...@apache.org> 于2022年1月25日周二 19:13写道：
>
> > Thanks for driving this Martijn, +1 for the release
> >
> > Also big thanks to Konstantin for volunteering
> >
> > Best,
> > D.
> >
> > On Mon, Jan 24, 2022 at 3:24 PM Till Rohrmann <tr...@apache.org>
> > wrote:
> >
> > > +1 for the 1.13.6 release and thanks for volunteering Konstantin.
> > >
> > > Cheers,
> > > Till
> > >
> > > On Mon, Jan 24, 2022 at 2:57 PM Konstantin Knauf <kn...@apache.org>
> > > wrote:
> > >
> > > > Thanks for starting the discussion and +1 to releasing.
> > > >
> > > > I am happy to manage the release aka learn how to do this.
> > > >
> > > > Cheers,
> > > >
> > > > Konstantin
> > > >
> > > > On Mon, Jan 24, 2022 at 2:52 PM Martijn Visser <
> martijn@ververica.com>
> > > > wrote:
> > > >
> > > > > I would like to start a discussion on releasing Flink 1.13.6. Flink
> > > > 1.13.5
> > > > > was the latest release on the 16th of December, which was the
> > emergency
> > > > > release for the Log4j CVE [1]. Flink 1.13.4 was cancelled, leaving
> > > Flink
> > > > > 1.13.3 as the last real bugfix release. This one was released on
> the
> > > 19th
> > > > > of October last year.
> > > > >
> > > > > Since then, there have been 61 fixed tickets, excluding the test
> > > > > stabilities [3]. This includes a blocker and a couple of critical
> > > issues.
> > > > >
> > > > > Is there a PMC member who would like to manage the release? I'm
> more
> > > than
> > > > > happy to help with monitoring the status of the tickets.
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Martijn Visser
> > > > > https://twitter.com/MartijnVisser82
> > > > >
> > > > > [1]
> > https://flink.apache.org/news/2021/12/16/log4j-patch-releases.html
> > > > > [2] https://flink.apache.org/news/2021/10/19/release-1.13.3.html
> > > > > [3] JQL filter: project = FLINK AND resolution = Fixed AND
> > fixVersion =
> > > > > 1.13.6 AND labels != test-stability ORDER BY priority DESC, created
> > > DESC
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Konstantin Knauf
> > > >
> > > > https://twitter.com/snntrable
> > > >
> > > > https://github.com/knaufk
> > > >
> > >
> >
>
Re: [DISCUSS] Releasing Flink 1.13.6
Posted by Konstantin Knauf <kn...@apache.org>.
Hi everyone,
I've created a release candidate, published all Maven artifacts and opened
a PR for the website [1,2,3,4,5]. Python wheels are missing at this point
as I am (like Thomas was) waiting for approval by Azure.
I'll start the formal vote when the Python wheels are available. Of course,
you can already start testing based on what is already there.
Cheers,
Konstantin
[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12351074
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.13.6-rc1/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1486/
[5] https://github.com/apache/flink/tree/release-1.13.6-rc1
[6] https://github.com/apache/flink-web/pull/505
On Tue, Feb 1, 2022 at 1:27 PM Martijn Visser <ma...@ververica.com> wrote:
> Hi Konstantin,
>
> Thanks for volunteering! There are no Blockers for 1.13.6 so you should be
> good to go for creating a release candidate.
>
> Best regards,
>
> Martijn
>
> On Wed, 26 Jan 2022 at 08:32, Jing Zhang <be...@gmail.com> wrote:
>
> > +1 for releasing Flink 1.13.6
> > Thanks Martijn and Konstantin for driving this.
> >
> > Best,
> > Jing Zhang
> >
> > David Morávek <dm...@apache.org> 于2022年1月25日周二 19:13写道：
> >
> > > Thanks for driving this Martijn, +1 for the release
> > >
> > > Also big thanks to Konstantin for volunteering
> > >
> > > Best,
> > > D.
> > >
> > > On Mon, Jan 24, 2022 at 3:24 PM Till Rohrmann <tr...@apache.org>
> > > wrote:
> > >
> > > > +1 for the 1.13.6 release and thanks for volunteering Konstantin.
> > > >
> > > > Cheers,
> > > > Till
> > > >
> > > > On Mon, Jan 24, 2022 at 2:57 PM Konstantin Knauf <kn...@apache.org>
> > > > wrote:
> > > >
> > > > > Thanks for starting the discussion and +1 to releasing.
> > > > >
> > > > > I am happy to manage the release aka learn how to do this.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Konstantin
> > > > >
> > > > > On Mon, Jan 24, 2022 at 2:52 PM Martijn Visser <
> > martijn@ververica.com>
> > > > > wrote:
> > > > >
> > > > > > I would like to start a discussion on releasing Flink 1.13.6.
> Flink
> > > > > 1.13.5
> > > > > > was the latest release on the 16th of December, which was the
> > > emergency
> > > > > > release for the Log4j CVE [1]. Flink 1.13.4 was cancelled,
> leaving
> > > > Flink
> > > > > > 1.13.3 as the last real bugfix release. This one was released on
> > the
> > > > 19th
> > > > > > of October last year.
> > > > > >
> > > > > > Since then, there have been 61 fixed tickets, excluding the test
> > > > > > stabilities [3]. This includes a blocker and a couple of critical
> > > > issues.
> > > > > >
> > > > > > Is there a PMC member who would like to manage the release? I'm
> > more
> > > > than
> > > > > > happy to help with monitoring the status of the tickets.
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > > Martijn Visser
> > > > > > https://twitter.com/MartijnVisser82
> > > > > >
> > > > > > [1]
> > > https://flink.apache.org/news/2021/12/16/log4j-patch-releases.html
> > > > > > [2] https://flink.apache.org/news/2021/10/19/release-1.13.3.html
> > > > > > [3] JQL filter: project = FLINK AND resolution = Fixed AND
> > > fixVersion =
> > > > > > 1.13.6 AND labels != test-stability ORDER BY priority DESC,
> created
> > > > DESC
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Konstantin Knauf
> > > > >
> > > > > https://twitter.com/snntrable
> > > > >
> > > > > https://github.com/knaufk
> > > > >
> > > >
> > >
> >
>
--
Konstantin Knauf
https://twitter.com/snntrable
https://github.com/knaufk