Re: Release Flink 1.0.0

2016-02-08 Thread Robert Metzger
Okay, I didn't check the individual PRs closely. I agree that we should not merge big core changes if we are not certain about their stability. On Mon, Feb 8, 2016 at 12:04 PM, Fabian Hueske wrote: > Regarding FLINK-2237 (hash-based combiner), I think we need a bit more > time. > It is a fairly

Re: Release Flink 1.0.0

2016-02-08 Thread Fabian Hueske
Regarding FLINK-2237 (hash-based combiner), I think we need a bit more time. It is a fairly large contribution and touches/adds core functionality. I started reviewing the PR and will suggest a few changes in the next days. 2016-02-08 11:48 GMT+01:00 Robert Metzger : > There are still some 8 ope

Re: Release Flink 1.0.0

2016-02-08 Thread Robert Metzger
There are still some 8 open blockers for the 1.0 release: https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20resolution%20%3D%20Unresolved%20AND%20priority%20%3D%20Blocker%20ORDER%20BY%20key%20DESC I also think that there are some pull requests which are almost ready to merge

Re: Release Flink 1.0.0

2016-02-02 Thread Robert Metzger
Hi, I think that getting the stop signal in would be very nice. I would like to postpone the feature freeze till end of this week and create the first RC on Monday. There are many open pull requests with fixes that need to go in (stop signal, rocksdb state backend, interface annotations, streamin

Re: Release Flink 1.0.0

2016-01-25 Thread Matthias J. Sax
Hi, I also would like to get the STOP signal in. But I do not have time to work in it this week... According to Till's comments, this will be the last round of reviewing required. So I should be able to finish it till 3rd Feb, but not sure. What do you think about it? -Matthias On 01/25/2016 04

Re: Release Flink 1.0.0

2016-01-25 Thread Aljoscha Krettek
Hi, I think the refactoring of Partitioned State and the WindowOperator on state work is almost ready. I also have the RocksDB state backend working. I’m running some tests now on the cluster and should be able to open a PR tomorrow. > On 25 Jan 2016, at 15:36, Stephan Ewen wrote: > > I agree

Re: Release Flink 1.0.0

2016-01-25 Thread Stephan Ewen
I agree, with Gyula, one out-of-core state backend should be in. We are pretty close to that. Aljoscha has done good work on extending test coverage for state backends, so we should be pretty comfortable that it works as well, once we integrate new state backends with the tests. There is a bit of

Re: Release Flink 1.0.0

2016-01-25 Thread Gyula Fóra
Hi, I agree that getting Flink 1.0.0 out soon would be great as Flink is in a pretty solid state right now. I wonder whether it would make sense to include an out-of-core state backend in streaming core that can be used with partitioned/window states. I think if we are releasing 1.0.0 we should h

Release Flink 1.0.0

2016-01-25 Thread Robert Metzger
Hi, I would like to release 1.0.0 in the next weeks. Looking at the JIRAs, I think we are going to close a lot of blocking issues soon. How about we do a first release candidate on Wednesday, 3. February? The first release candidate is most likely not going to pass the vote, the primary goal will