Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

Chesnay, I would propose to look into a CI solution for Windows. I'll try out appveyor.com for my Flink fork and report back how well it works (let me know if you want to look into it). On Tue, May 9, 2017 at 10:05 AM, Stephan Ewen wrote: > @Renjie What functionality are you

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

I'm just looking forward basic functionalities, e.g. a single web port for all flink jobs. On Tue, May 9, 2017 at 4:05 PM Stephan Ewen wrote: > @Renjie What functionality are you looking for? Most stuff should work in > the normal master branch. > > > On Tue, May 9, 2017 at

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

@Renjie What functionality are you looking for? Most stuff should work in the normal master branch. On Tue, May 9, 2017 at 10:02 AM, Renjie Liu wrote: > Stephan: > This means that we can use FLIP 6 for basic functionality now? Any > document for setting up that? Will

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

Stephan: This means that we can use FLIP 6 for basic functionality now? Any document for setting up that? Will FLIP 6 be finished in release 1.3? On Tue, May 9, 2017 at 3:43 PM Stephan Ewen wrote: > @Renjie Liu: A good part of the FLIP-6 code is in there, but not all. > > It

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

This RC (and 1.4-SNAPSHOT for that matter) cannot be compiled on Windows due to the rat-plugin not detecting certain test savepoints as binary files. The files in question are the "savepoints" created by the StreamOperatorTestHarness. This is not a new problem and has happened before, but we

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

@Renjie Liu: A good part of the FLIP-6 code is in there, but not all. It does run well on Yarn, Mesos, Docker, etc. We need to finish the FLIP-6 work mainly for full elasticity. On Tue, May 9, 2017 at 5:24 AM, Renjie Liu wrote: > Hi, does this include the FLIP6? > >

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

Hi, does this include the FLIP6? On Tue, May 9, 2017 at 2:29 AM Stephan Ewen wrote: > Did a quick test: Simply adding the > "org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer" > helps with NOTICE files, > but does not add the required BSD licence copies.

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

Did a quick test: Simply adding the "org.apache.maven.plugins.shade.resource.ApacheNoticeResourceTransformer" helps with NOTICE files, but does not add the required BSD licence copies. On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen wrote: > I did the first pass for the legal

Re: [DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

I did the first pass for the legal check. - Source LICENSE and NOTICE are okay - In the shaded JAR files, we are not bundling the license and notice files of the dependencies we include in the shaded jars. => Not a problem for Guava (Apache Licensed) => I think is a problem for ASM

[DISCUSS] Release 1.3.0 RC0 (Non voting, testing release candidate)

Hi Devs, I've created a first non-voting release candidate for Flink 1.3.0. Please use this RC to test as much as you can and provide feedback to the Flink community. The more we find and fix now, the better Flink 1.3.0 wil be :) I've CC'ed the user@ mailing list to get more people to test it.