Re: [DISCUSS] Flink 1.4 and time based release

+1 for that, as long we will be consistent with it :) > On Aug 31, 2017, at 12:22 PM, Aljoscha Krettek wrote: > > +1 On using "Fix Version" for that. I always try to use that already for > things that need fixing in the next release. Also "Blocker" is a thing there. > >>

Re: [DISCUSS] Flink 1.4 and time based release

Haven’t seen much discussion here. I see the benefit of time-based deadlines but also of focussing on release functionality and stability. I like the idea to keep the structure of time-based releases but soften the deadlines. The schedule would not be open-ended but we could wait on the

Re: [DISCUSS] Flink 1.4 and time based release

I also think we shouldn't publish releases regularly, just to have a release regularly. Maybe we can do time-based releases more flexible: Instead of feature-freeze after 3 months, 1 month testing. We could do it like feature-freeze 3 months after the last release, unlimited testing. This

Re: [DISCUSS] Flink 1.4 and time based release

Thanks for starting the discussion Stephan. I agree with you that the last release was probably a bit hasty due to the constraints we put on ourselves with the strict time based release. Therefore and because of some of the incomplete features, I would be in favour of loosening the strict deadline

Re: [DISCUSS] Flink 1.4 and time based release

I would be great to avoid immediate 1.x1 bug fixing release. It cause confusion and raise quality concerns. Also, is there already way to communicate with Amazon EMR for latest release speedy available? I may try to find someone work there is needed. Thanks Chen > On Aug 22, 2017, at 9:32 AM,

[DISCUSS] Flink 1.4 and time based release

Hi all! I want to bring up this discussion because we are approaching the date when there would be a feature freeze following the time based release schedule. To make it short, I would suggest to not follow the time-based schedule for that release. There are a bunch of reasons bringing me to