+1
Although I would hope that it can be more than just "anticipated".
Best,
Aljoscha
On 19.02.20 15:40, Till Rohrmann wrote:
Thanks for volunteering as one of our release managers Zhijiang.
+1 for the *anticipated feature freeze date* end of April. As we go along
and collect more data points we might be able to strengthen our
initial anticipation.
Cheers,
Till
On Wed, Feb 19, 2020 at 4:44 AM Zhijiang <wangzhijiang...@aliyun.com.invalid>
wrote:
Thanks for kicking off the next release and the introduction, @Stephan!
It's my pleasure to become the release manager and involve in other
community works. I am working together with @Piotr for a long time, so
very happy to cooperate for the release manager work again. The previous
release work was always well done, and I can learn a lot from these rich
experiences.
+1 for the "feature freeze date" around end of April.
Although we have the FF SF in the meantime, fortunately there are no long
public holidays during this period in China.
Best,
Zhijiang
------------------------------------------------------------------
From:Stephan Ewen <se...@apache.org>
Send Time:2020 Feb. 19 (Wed.) 01:15
To:dev <dev@flink.apache.org>
Cc:zhijiang <zhiji...@apache.org>; pnowojski <pnowoj...@apache.org>
Subject:[DISCUSS] Kicking off the 1.11 release cycle
Hi all!
Now that the 1.10 release is out (congrats again, everyone!), I wanted to
bring up some questions about organizing the next release cycle.
The most important questions at the beginning would be
- Who would volunteer as Release Managers
- When would be the release date.
For the release managers, Piotrek and Zhijiang have mentioned previously
that they would be interested, so I am copying them here to chime in.
@Piotr and @Zhijiang could you confirm if you are interested in helping
out with this?
About the release date: By our original "3 months release cycle"
assumption, we should aim for a release **Mid May**, meaning a feature
freeze no later than end of April.
That would be indeed a shorter release cycle than 1.10, and the assumption
of a shorter testing period. But aiming for a shorter release cycle than
1.10 would actually be nice, in my opinion. 1.10 grew very big in the end,
which caused also a very long testing period (plus Christmas and Chinese
New Year are also partially to blame).
The exact feature freeze date is anyways a community discussion later, but
what do you think about starting with an "anticipated feature freeze date"
around end of April, so that committers, contributors, and users know
roughly what to expect?
Best,
Stephan
