You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by Dawid Wysakowicz <dw...@apache.org> on 2021/01/13 14:47:56 UTC
[DISCUSS] Planning Flink 1.13
Hi all,
With the 1.12 being released some time ago already I thought it would be
a good time to kickstart the 1.13 release cycle.
What do you think about Guowei and me being the release managers for
Flink 1.13? We are happy to volunteer for it.
The second topic I wanted to raise was the rough timeline for the
release. According to our usual 3 months + the release
testing/stabilising period
we should aim with the feature freeze for the end of March/beginning of
April. Does that work for everyone?
Let me know what you think.
Best,
Dawid
Re: [DISCUSS] Planning Flink 1.13
Posted by Dawid Wysakowicz <dw...@apache.org>.
Hey Roman,
Thanks for the idea! Personally I am a bit torn about this. We have
never done something like this before. In principle I like the idea of
shorter release cycles. However I am bit skeptical about the timing to
do it now. Do we know what would be included in such a release? I am a
bit afraid it would come as a surprise for many teams unaware of plans
for a shorter release. How would we make sure that features of such
teams that ends up on master in the meantime won't interfere with the
finished features of the teams that were prepared for that shorter cycle?
What do others think about having a shorter release?
Best,
Dawid
On 14/01/2021 11:17, Khachatryan Roman wrote:
> Thanks for doing this!
>
> Some teams are currently doing (or already finalizing) the "usability
> sprint". I was wondering whether it makes sense to release the implemented
> features without waiting for the major changes. If it works well we could
> decide to shorten the next release as well.
>
> Regards,
> Roman
>
>
> On Thu, Jan 14, 2021 at 10:28 AM Till Rohrmann <tr...@apache.org> wrote:
>
>> Thanks for volunteering as the release managers for the 1.13 release Guowei
>> and Dawid. I'd also be in favour of targeting the end of March as the
>> feature freeze date.
>>
>> I've created a 1.13 wiki page [1] where we can collect the features we want
>> to complete for the 1.13 release.
>>
>> [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
>>
>> Cheers,
>> Till
>>
>> On Thu, Jan 14, 2021 at 3:27 AM Xintong Song <to...@gmail.com>
>> wrote:
>>
>>> Thanks for kicking off the 1.13 release cycle and volunteering as the
>>> release managers.
>>>
>>> +1 for Dawid & Guowei as the 1.13 release managers.
>>> +1 for targeting feature freeze at the end of March
>>>
>>> Thank you~
>>>
>>> Xintong Song
>>>
>>>
>>>
>>> On Wed, Jan 13, 2021 at 10:48 PM Dawid Wysakowicz <
>> dwysakowicz@apache.org>
>>> wrote:
>>>
>>>> Hi all,
>>>> With the 1.12 being released some time ago already I thought it would
>> be
>>>> a good time to kickstart the 1.13 release cycle.
>>>>
>>>> What do you think about Guowei and me being the release managers for
>>>> Flink 1.13? We are happy to volunteer for it.
>>>>
>>>> The second topic I wanted to raise was the rough timeline for the
>>>> release. According to our usual 3 months + the release
>>>> testing/stabilising period
>>>> we should aim with the feature freeze for the end of March/beginning of
>>>> April. Does that work for everyone?
>>>>
>>>> Let me know what you think.
>>>>
>>>> Best,
>>>> Dawid
>>>>
>>>>
>>>>
Re: [DISCUSS] Planning Flink 1.13
Posted by Xingbo Huang <hx...@gmail.com>.
Thanks for being our release managers for the 1.13 release Dawid & Guowei!
The end of March as the feature freeze date sounds good to me.
Best,
Xingbo
Jark Wu <im...@gmail.com> 于2021年1月14日周四 下午6:21写道：
> Thanks for starting the 1.13 release cycle and volunteering as the release
> managers!
>
> The feature freeze date sounds good to me.
>
> Best,
> Jark
>
> On Thu, 14 Jan 2021 at 18:19, Khachatryan Roman <
> khachatryan.roman@gmail.com>
> wrote:
>
> > Thanks for doing this!
> >
> > Some teams are currently doing (or already finalizing) the "usability
> > sprint". I was wondering whether it makes sense to release the
> implemented
> > features without waiting for the major changes. If it works well we could
> > decide to shorten the next release as well.
> >
> > Regards,
> > Roman
> >
> >
> > On Thu, Jan 14, 2021 at 10:28 AM Till Rohrmann <tr...@apache.org>
> > wrote:
> >
> > > Thanks for volunteering as the release managers for the 1.13 release
> > Guowei
> > > and Dawid. I'd also be in favour of targeting the end of March as the
> > > feature freeze date.
> > >
> > > I've created a 1.13 wiki page [1] where we can collect the features we
> > want
> > > to complete for the 1.13 release.
> > >
> > > [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
> > >
> > > Cheers,
> > > Till
> > >
> > > On Thu, Jan 14, 2021 at 3:27 AM Xintong Song <to...@gmail.com>
> > > wrote:
> > >
> > > > Thanks for kicking off the 1.13 release cycle and volunteering as the
> > > > release managers.
> > > >
> > > > +1 for Dawid & Guowei as the 1.13 release managers.
> > > > +1 for targeting feature freeze at the end of March
> > > >
> > > > Thank you~
> > > >
> > > > Xintong Song
> > > >
> > > >
> > > >
> > > > On Wed, Jan 13, 2021 at 10:48 PM Dawid Wysakowicz <
> > > dwysakowicz@apache.org>
> > > > wrote:
> > > >
> > > > > Hi all,
> > > > > With the 1.12 being released some time ago already I thought it
> would
> > > be
> > > > > a good time to kickstart the 1.13 release cycle.
> > > > >
> > > > > What do you think about Guowei and me being the release managers
> for
> > > > > Flink 1.13? We are happy to volunteer for it.
> > > > >
> > > > > The second topic I wanted to raise was the rough timeline for the
> > > > > release. According to our usual 3 months + the release
> > > > > testing/stabilising period
> > > > > we should aim with the feature freeze for the end of
> March/beginning
> > of
> > > > > April. Does that work for everyone?
> > > > >
> > > > > Let me know what you think.
> > > > >
> > > > > Best,
> > > > > Dawid
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Jark Wu <im...@gmail.com>.
Thanks for starting the 1.13 release cycle and volunteering as the release
managers!
The feature freeze date sounds good to me.
Best,
Jark
On Thu, 14 Jan 2021 at 18:19, Khachatryan Roman <kh...@gmail.com>
wrote:
> Thanks for doing this!
>
> Some teams are currently doing (or already finalizing) the "usability
> sprint". I was wondering whether it makes sense to release the implemented
> features without waiting for the major changes. If it works well we could
> decide to shorten the next release as well.
>
> Regards,
> Roman
>
>
> On Thu, Jan 14, 2021 at 10:28 AM Till Rohrmann <tr...@apache.org>
> wrote:
>
> > Thanks for volunteering as the release managers for the 1.13 release
> Guowei
> > and Dawid. I'd also be in favour of targeting the end of March as the
> > feature freeze date.
> >
> > I've created a 1.13 wiki page [1] where we can collect the features we
> want
> > to complete for the 1.13 release.
> >
> > [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
> >
> > Cheers,
> > Till
> >
> > On Thu, Jan 14, 2021 at 3:27 AM Xintong Song <to...@gmail.com>
> > wrote:
> >
> > > Thanks for kicking off the 1.13 release cycle and volunteering as the
> > > release managers.
> > >
> > > +1 for Dawid & Guowei as the 1.13 release managers.
> > > +1 for targeting feature freeze at the end of March
> > >
> > > Thank you~
> > >
> > > Xintong Song
> > >
> > >
> > >
> > > On Wed, Jan 13, 2021 at 10:48 PM Dawid Wysakowicz <
> > dwysakowicz@apache.org>
> > > wrote:
> > >
> > > > Hi all,
> > > > With the 1.12 being released some time ago already I thought it would
> > be
> > > > a good time to kickstart the 1.13 release cycle.
> > > >
> > > > What do you think about Guowei and me being the release managers for
> > > > Flink 1.13? We are happy to volunteer for it.
> > > >
> > > > The second topic I wanted to raise was the rough timeline for the
> > > > release. According to our usual 3 months + the release
> > > > testing/stabilising period
> > > > we should aim with the feature freeze for the end of March/beginning
> of
> > > > April. Does that work for everyone?
> > > >
> > > > Let me know what you think.
> > > >
> > > > Best,
> > > > Dawid
> > > >
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Khachatryan Roman <kh...@gmail.com>.
Thanks for doing this!
Some teams are currently doing (or already finalizing) the "usability
sprint". I was wondering whether it makes sense to release the implemented
features without waiting for the major changes. If it works well we could
decide to shorten the next release as well.
Regards,
Roman
On Thu, Jan 14, 2021 at 10:28 AM Till Rohrmann <tr...@apache.org> wrote:
> Thanks for volunteering as the release managers for the 1.13 release Guowei
> and Dawid. I'd also be in favour of targeting the end of March as the
> feature freeze date.
>
> I've created a 1.13 wiki page [1] where we can collect the features we want
> to complete for the 1.13 release.
>
> [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
>
> Cheers,
> Till
>
> On Thu, Jan 14, 2021 at 3:27 AM Xintong Song <to...@gmail.com>
> wrote:
>
> > Thanks for kicking off the 1.13 release cycle and volunteering as the
> > release managers.
> >
> > +1 for Dawid & Guowei as the 1.13 release managers.
> > +1 for targeting feature freeze at the end of March
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Wed, Jan 13, 2021 at 10:48 PM Dawid Wysakowicz <
> dwysakowicz@apache.org>
> > wrote:
> >
> > > Hi all,
> > > With the 1.12 being released some time ago already I thought it would
> be
> > > a good time to kickstart the 1.13 release cycle.
> > >
> > > What do you think about Guowei and me being the release managers for
> > > Flink 1.13? We are happy to volunteer for it.
> > >
> > > The second topic I wanted to raise was the rough timeline for the
> > > release. According to our usual 3 months + the release
> > > testing/stabilising period
> > > we should aim with the feature freeze for the end of March/beginning of
> > > April. Does that work for everyone?
> > >
> > > Let me know what you think.
> > >
> > > Best,
> > > Dawid
> > >
> > >
> > >
> >
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Piotr Nowojski <pn...@apache.org>.
+1 for both proposals. Thanks!
Piotrek
pon., 18 sty 2021 o 11:04 Yun Tang <my...@live.com> napisał(a):
> +1 for the proposed date and thanks for Dawid & Guowei as the release
> manager.
>
> Best
> Yun Tang
> ________________________________
> From: Yangze Guo <ka...@gmail.com>
> Sent: Friday, January 15, 2021 9:50
> To: dev <de...@flink.apache.org>
> Subject: Re: [DISCUSS] Planning Flink 1.13
>
> Thanks for being the release managers, Guowei and Dawid.
>
> +1 for the proposed feature freeze date
>
> Best,
> Yangze Guo
>
> On Fri, Jan 15, 2021 at 2:01 AM Zhu Zhu <re...@gmail.com> wrote:
> >
> > +1 for Dawid and Guowei being the release managers and +1 for the
> proposed
> > feature freeze date
> >
> > Thanks,
> > Zhu
> >
> > Leonard Xu <xb...@gmail.com> 于2021年1月15日周五 上午12:02写道：
> >
> > > Thanks Dawid & Guowei for starting the release cycle and volunteering
> as
> > > the release managers.
> > >
> > > +1 for the rought feature freeze date.
> > >
> > > Best,
> > > Leonard
> > >
> > > > 在 2021年1月14日，21:04，Aljoscha Krettek <al...@apache.org> 写道：
> > > >
> > > > On 2021/01/14 10:28, Till Rohrmann wrote:
> > > >> I've created a 1.13 wiki page [1] where we can collect the features
> we
> > > want
> > > >> to complete for the 1.13 release.
> > > >>
> > > >> [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
> > > >
> > > > Thanks! I've starting adding things to this.
> > >
> > >
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Yun Tang <my...@live.com>.
+1 for the proposed date and thanks for Dawid & Guowei as the release manager.
Best
Yun Tang
________________________________
From: Yangze Guo <ka...@gmail.com>
Sent: Friday, January 15, 2021 9:50
To: dev <de...@flink.apache.org>
Subject: Re: [DISCUSS] Planning Flink 1.13
Thanks for being the release managers, Guowei and Dawid.
+1 for the proposed feature freeze date
Best,
Yangze Guo
On Fri, Jan 15, 2021 at 2:01 AM Zhu Zhu <re...@gmail.com> wrote:
>
> +1 for Dawid and Guowei being the release managers and +1 for the proposed
> feature freeze date
>
> Thanks,
> Zhu
>
> Leonard Xu <xb...@gmail.com> 于2021年1月15日周五 上午12:02写道：
>
> > Thanks Dawid & Guowei for starting the release cycle and volunteering as
> > the release managers.
> >
> > +1 for the rought feature freeze date.
> >
> > Best,
> > Leonard
> >
> > > 在 2021年1月14日，21:04，Aljoscha Krettek <al...@apache.org> 写道：
> > >
> > > On 2021/01/14 10:28, Till Rohrmann wrote:
> > >> I've created a 1.13 wiki page [1] where we can collect the features we
> > want
> > >> to complete for the 1.13 release.
> > >>
> > >> [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
> > >
> > > Thanks! I've starting adding things to this.
> >
> >
Re: [DISCUSS] Planning Flink 1.13
Posted by Yangze Guo <ka...@gmail.com>.
Thanks for being the release managers, Guowei and Dawid.
+1 for the proposed feature freeze date
Best,
Yangze Guo
On Fri, Jan 15, 2021 at 2:01 AM Zhu Zhu <re...@gmail.com> wrote:
>
> +1 for Dawid and Guowei being the release managers and +1 for the proposed
> feature freeze date
>
> Thanks,
> Zhu
>
> Leonard Xu <xb...@gmail.com> 于2021年1月15日周五 上午12:02写道：
>
> > Thanks Dawid & Guowei for starting the release cycle and volunteering as
> > the release managers.
> >
> > +1 for the rought feature freeze date.
> >
> > Best,
> > Leonard
> >
> > > 在 2021年1月14日，21:04，Aljoscha Krettek <al...@apache.org> 写道：
> > >
> > > On 2021/01/14 10:28, Till Rohrmann wrote:
> > >> I've created a 1.13 wiki page [1] where we can collect the features we
> > want
> > >> to complete for the 1.13 release.
> > >>
> > >> [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
> > >
> > > Thanks! I've starting adding things to this.
> >
> >
Re: [DISCUSS] Planning Flink 1.13
Posted by Zhu Zhu <re...@gmail.com>.
+1 for Dawid and Guowei being the release managers and +1 for the proposed
feature freeze date
Thanks,
Zhu
Leonard Xu <xb...@gmail.com> 于2021年1月15日周五 上午12:02写道：
> Thanks Dawid & Guowei for starting the release cycle and volunteering as
> the release managers.
>
> +1 for the rought feature freeze date.
>
> Best,
> Leonard
>
> > 在 2021年1月14日，21:04，Aljoscha Krettek <al...@apache.org> 写道：
> >
> > On 2021/01/14 10:28, Till Rohrmann wrote:
> >> I've created a 1.13 wiki page [1] where we can collect the features we
> want
> >> to complete for the 1.13 release.
> >>
> >> [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
> >
> > Thanks! I've starting adding things to this.
>
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Leonard Xu <xb...@gmail.com>.
Thanks Dawid & Guowei for starting the release cycle and volunteering as the release managers.
+1 for the rought feature freeze date.
Best,
Leonard
> 在 2021年1月14日，21:04，Aljoscha Krettek <al...@apache.org> 写道：
>
> On 2021/01/14 10:28, Till Rohrmann wrote:
>> I've created a 1.13 wiki page [1] where we can collect the features we want
>> to complete for the 1.13 release.
>>
>> [1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
>
> Thanks! I've starting adding things to this.
Re: [DISCUSS] Planning Flink 1.13
Posted by Aljoscha Krettek <al...@apache.org>.
On 2021/01/14 10:28, Till Rohrmann wrote:
>I've created a 1.13 wiki page [1] where we can collect the features we
>want
>to complete for the 1.13 release.
>
>[1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
Thanks! I've starting adding things to this.
Re: [DISCUSS] Planning Flink 1.13
Posted by Till Rohrmann <tr...@apache.org>.
Thanks for volunteering as the release managers for the 1.13 release Guowei
and Dawid. I'd also be in favour of targeting the end of March as the
feature freeze date.
I've created a 1.13 wiki page [1] where we can collect the features we want
to complete for the 1.13 release.
[1] https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
Cheers,
Till
On Thu, Jan 14, 2021 at 3:27 AM Xintong Song <to...@gmail.com> wrote:
> Thanks for kicking off the 1.13 release cycle and volunteering as the
> release managers.
>
> +1 for Dawid & Guowei as the 1.13 release managers.
> +1 for targeting feature freeze at the end of March
>
> Thank you~
>
> Xintong Song
>
>
>
> On Wed, Jan 13, 2021 at 10:48 PM Dawid Wysakowicz <dw...@apache.org>
> wrote:
>
> > Hi all,
> > With the 1.12 being released some time ago already I thought it would be
> > a good time to kickstart the 1.13 release cycle.
> >
> > What do you think about Guowei and me being the release managers for
> > Flink 1.13? We are happy to volunteer for it.
> >
> > The second topic I wanted to raise was the rough timeline for the
> > release. According to our usual 3 months + the release
> > testing/stabilising period
> > we should aim with the feature freeze for the end of March/beginning of
> > April. Does that work for everyone?
> >
> > Let me know what you think.
> >
> > Best,
> > Dawid
> >
> >
> >
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Xintong Song <to...@gmail.com>.
Thanks for kicking off the 1.13 release cycle and volunteering as the
release managers.
+1 for Dawid & Guowei as the 1.13 release managers.
+1 for targeting feature freeze at the end of March
Thank you~
Xintong Song
On Wed, Jan 13, 2021 at 10:48 PM Dawid Wysakowicz <dw...@apache.org>
wrote:
> Hi all,
> With the 1.12 being released some time ago already I thought it would be
> a good time to kickstart the 1.13 release cycle.
>
> What do you think about Guowei and me being the release managers for
> Flink 1.13? We are happy to volunteer for it.
>
> The second topic I wanted to raise was the rough timeline for the
> release. According to our usual 3 months + the release
> testing/stabilising period
> we should aim with the feature freeze for the end of March/beginning of
> April. Does that work for everyone?
>
> Let me know what you think.
>
> Best,
> Dawid
>
>
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Khachatryan Roman <kh...@gmail.com>.
Hey Dawid,
Replying to your penultimate message:
> We have never done something like this before
I thought releasing usability features can be such an experiment. My
reasoning is the following. As each release requires coordination of all
the participating teams, it will not scale beyond some point. And Flink is
growing rapidly. So we need to cut the scope of each release:
- either by sub-project (i.e. separate release for each component; I think
no one wants it?)
- or by time/feature set (i.e. more frequent lightweight releases)
> However I am bit skeptical about the timing to do it now.
I guess you are right. We should probably start release planning before the
previous one is completed. So maybe 1.14 :)
I think if anyone else is interested we can continue discussion in a
separate thread.
Thanks again for driving this effort!
Regards,
Roman
On Mon, Jan 18, 2021 at 3:59 PM Dawid Wysakowicz <dw...@apache.org>
wrote:
> Hi all,
>
> Thank you all for a warm reception as release managers. We are also glad
> that the majority agrees we should aim for the end of March as the feature
> freeze date.
>
> 1. Till created a page in our wiki to gather potential features that
> we want to include in the release. Thank you Till! We'd kindly ask all
> committers to fill in the page with features that they intend to work on.
> We'd prefer if only new features end up there and not all bugs/tasks
> separately so that the page is not over bloated. Of course, unless fixing a
> bug is a really big or important one equivalent to implementing a
> completely new feature. In our opinion a good rule of thumb would be that
> each entry in the page could (but does not have to) be later on included in
> a release blog post.
>
> The page can be accessed at:
> https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
>
> It would really help us if we knew what are the most critical features in
> the release, so that we could keep a closer eye on those as potential
> reasons for a delay or make a decision to cut the scope sooner. We were
> thinking if it would be possible to mark certain features as "release
> blockers". There should be no more than a single, unfinished one per
> committer at a time. What do you think of that idea?
>
>
> 1. Similarly to the previous release we would like to emphasize the
> importance of keeping the build and tests stable. We think that worked
> pretty well in the last release. Starting this week we will monitor any
> build and/or test instabilities. Please expect nagging for a fix ;)
>
> You can check the current blockers in a dedicated kanban board here:
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=445
>
>
> 1. One of the biggest complaints for the past release(s) was lack of
> proper documentation. Some features don't have a proper documentation even
> though they were implemented a couple of releases ago. We'd like to remind
> everyone that a decent documentation should always come hand in hand with
> the code. We have even a checkmark for it in our PR template. ;) Lets try
> to improve the situation a bit here! We should no longer allow ourselves to
> postpone writing documentation to after the feature freeze.
>
> Your release managers,
> Guowei & Dawid
>
Re: [DISCUSS] Planning Flink 1.13
Posted by Dawid Wysakowicz <dw...@apache.org>.
Hi all,
Thank you all for a warm reception as release managers. We are also glad
that the majority agrees we should aim for the end of March as the
feature freeze date.
1. Till created a page in our wiki to gather potential features that we
want to include in the release. Thank you Till! We'd kindly ask all
committers to fill in the page with features that they intend to
work on. We'd prefer if only new features end up there and not all
bugs/tasks separately so that the page is not over bloated. Of
course, unless fixing a bug is a really big or important one
equivalent to implementing a completely new feature. In our opinion
a good rule of thumb would be that each entry in the page could (but
does not have to) be later on included in a release blog post.
The page can be accessed at:
https://cwiki.apache.org/confluence/display/FLINK/1.13+Release
It would really help us if we knew what are the most critical
features in the release, so that we could keep a closer eye on those
as potential reasons for a delay or make a decision to cut the scope
sooner. We were thinking if it would be possible to mark certain
features as "release blockers". There should be no more than a
single, unfinished one per committer at a time. What do you think of
that idea?
2. Similarly to the previous release we would like to emphasize the
importance of keeping the build and tests stable. We think that
worked pretty well in the last release. Starting this week we will
monitor any build and/or test instabilities. Please expect nagging
for a fix ;)
You can check the current blockers in a dedicated kanban board here:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=445
3. One of the biggest complaints for the past release(s) was lack of
proper documentation. Some features don't have a proper
documentation even though they were implemented a couple of releases
ago. We'd like to remind everyone that a decent documentation should
always come hand in hand with the code. We have even a checkmark for
it in our PR template. ;) Lets try to improve the situation a bit
here! We should no longer allow ourselves to postpone writing
documentation to after the feature freeze.
Your release managers,
Guowei & Dawid
Re: [DISCUSS] Planning Flink 1.13
Posted by Aljoscha Krettek <al...@apache.org>.
+1 to the rough feature freeze date and the proposed release managers
Thanks for taking care of this!
Best,
Aljoscha
On 2021/01/13 15:47, Dawid Wysakowicz wrote:
>Hi all,
>With the 1.12 being released some time ago already I thought it would be
>a good time to kickstart the 1.13 release cycle.
>
>What do you think about Guowei and me being the release managers for
>Flink 1.13? We are happy to volunteer for it.
>
>The second topic I wanted to raise was the rough timeline for the
>release. According to our usual 3 months + the release
>testing/stabilising period
>we should aim with the feature freeze for the end of March/beginning of
>April. Does that work for everyone?
>
>Let me know what you think.
>
>Best,
>Dawid
>
>