We indeed set the July 25 deadline as a fixed deadline. We wanted to get
back in the quicker cadence of releasing.
Op di 31 mei 2022 om 09:03 schreef Robert Metzger :
> >
> > Is the feature freeze deadline on July 25 fixed or will it be adjusted
> > accordingly?
>
>
> Ideally we try not to push th
>
> Is the feature freeze deadline on July 25 fixed or will it be adjusted
> accordingly?
Ideally we try not to push the deadline too much into the future. So I
prefer to consider it fixed.
On Mon, May 30, 2022 at 7:08 PM Jing Ge wrote:
> Thanks Robert for the reminder. Thanks Martijn for shar
Thanks Robert for the reminder. Thanks Martijn for sharing the link.
Is the feature freeze deadline on July 25 fixed or will it be adjusted
accordingly?
Best regards,
Jing
On Mon, May 30, 2022 at 4:56 PM Martijn Visser
wrote:
> Yes, we will have the release meeting tomorrow. Looking forward to
Yes, we will have the release meeting tomorrow. Looking forward to everyone
who wants to participate. For those that are looking for the invite link,
see https://cwiki.apache.org/confluence/display/FLINK/1.16+Release
Best regards,
Martijn
Op ma 30 mei 2022 om 16:39 schreef Robert Metzger :
> I
I assume we'll have the next release planning meeting tomorrow?
I'm also bringing this up also as a reminder for other folks who might be
interested in joining.
On Wed, May 11, 2022 at 5:55 AM Xintong Song wrote:
> I'd like to kindly remind that, if someone adds / modifies release notes of
> a
I'd like to kindly remind that, if someone adds / modifies release notes of
a JIRA ticket close to or after the release finalization, it would be
important to sync with the release managers and make sure that change
appears in the final release notes.
We have recently discovered a breaking change
Thanks Chesnay, Godfrey, Xingbo and Martijn for volunteering as release
managers.
I would also recommend to have an eye on the "Release Notes:" fields in JIRA
for related issues early, as this is used to assemble the final release notes.
I'd also like to take the chance to ask contributors to fi
Hi everyone,
With Flink 1.15 released last week, we're starting with the next release
cycle for what will become Flink 1.16. As previously discussed [1] Chesnay,
Godfrey, Xingbo and myself have volunteered as release managers. We're
aiming to cut the release branch on the 25th of July. If needed,
Hi everyone,
Xingbo, Becket, Chesnay, Martijn, Godfrey and myself briefly talked offline
and we would propose that Xingbo, Godfrey, Martijn and Chesnay take on the
release management for the next release. Six people seemed like an overkill
but having a bit of high availability in both Europe and A
Thanks for kicking off the topic, Konstantin and Chesnay.
Also thanks Martijn, Godfrey and Xingbo for volunteering to be the release
manager. Given that release 1.16 would likely be a beefy release with a
bunch of major features already on their way, it might make sense to have
more release manage
Thanks Konstantin and Chesnay for starting the discussion. I'm also willing
to volunteer as the release manager if this is still open.
Regarding the feature freeze date, +1 to the end of mid August.
Best,
Xingbo
Zhu Zhu 于2022年4月29日周五 11:01写道：
> +1 for a 5 months release cycle.
> +1 target the
+1 for a 5 months release cycle.
+1 target the feature freeze date 1.5 months before the release date. It
can better guard the release date.
Therefore, also +1 for mid August as the feature freeze date of 1.16
Thanks,
Zhu
Jark Wu 于2022年4月28日周四 22:24写道：
> I'm also fine with the end of July for t
I'm also fine with the end of July for the feature freeze.
Best,
Jark
On Thu, 28 Apr 2022 at 21:00, Martijn Visser wrote:
> +1 for continuing to strive for a 5 months release cycle.
>
> And +1 to have the planned feature freeze mid August, which I would propose
> to have happen on Monday the 15
+1 for continuing to strive for a 5 months release cycle.
And +1 to have the planned feature freeze mid August, which I would propose
to have happen on Monday the 15th of August 2022. I would also already
state that even though we know this is a holiday period, we should not
extend this deadline f
Thanks for the check.
> Continue to strive for a 5 months release cycle and 1.5 months before to the
> desired release date
Sounds good to me!
Best,
Jingsong
On Thu, Apr 28, 2022 at 7:06 PM Konstantin Knauf wrote:
>
> Hi everyone,
>
> thank you for the feedback so far. I've checked the length
Hi everyone,
thank you for the feedback so far. I've checked the length of the previous
last release cycles. Up until Flink 1.14, we've actually been incredibly
good at maintaining a 5 months release cycle (see below). Interestingly,
the community is officially targeting a 4 months release cycle [
Thanks Konstantin and Chesnay for starting the discussion. And thanks
Konstantin, Chesnay, Godfrey, Martijn for volunteering.
The 1.16 release at the end of July means that there are currently
only 3 months to fully commit to 1.16 development, and I'm a little
concerned that this is too short a ti
Thanks Konstantin and Chesnay for starting the discussion and volunteering.
The timeline proposal sounds reasonable :+1:
Best,
D.
On Tue, Apr 26, 2022 at 1:37 PM Martijn Visser
wrote:
> Hi everyone,
>
> Thanks for starting this discussion. I would also volunteer to help out as
> a release manag
Hi Konstantin,
Feature freeze end of July sounds reasonable.
I think what we learned with the 1.15 release pushing it to a later point in
time
due to holidays etc., might set the tone early.
Best,
Joe
> On 26.04.2022, at 12:23, Konstantin Knauf wrote:
>
> Hi everyone,
>
> With Flink 1.15 a
Hi everyone,
Thanks for starting this discussion. I would also volunteer to help out as
a release manager for the 1.16 release.
Best regards,
Martijn Visser
https://twitter.com/MartijnVisser82
https://github.com/MartijnVisser
On Tue, 26 Apr 2022 at 13:19, godfrey he wrote:
> Hi Konstantin &
Hi Konstantin & Chesnay,
Thanks for driving this discussion, I am willing to volunteer as the
release manager for 1.16.
Best,
Godfrey
Konstantin Knauf 于2022年4月26日周二 18:23写道：
>
> Hi everyone,
>
> With Flink 1.15 about to be released, the community has started planning &
> developing features fo
Hi everyone,
With Flink 1.15 about to be released, the community has started planning &
developing features for the next release, Flink 1.16. As such, I would like
to start a discussion around managing this release.
Specifically, Chesnay & myself would like to volunteer as release managers.
Our f
22 matches
Mail list logo
