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

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

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

rmetzger0
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert

Reply | Threaded
Open this post in threaded view
|

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

Stephan Ewen
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert


Reply | Threaded
Open this post in threaded view
|

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

Stephan Ewen
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 <[hidden email]> wrote:
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert



Reply | Threaded
Open this post in threaded view
|

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

Renjie Liu
Hi, does this include the FLIP6?

On Tue, May 9, 2017 at 2:29 AM Stephan Ewen <[hidden email]> 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.


On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen <[hidden email]> wrote:
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert



--
Liu, Renjie
Software Engineer, MVAD
Reply | Threaded
Open this post in threaded view
|

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

Stephan Ewen
@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 <[hidden email]> wrote:
Hi, does this include the FLIP6?

On Tue, May 9, 2017 at 2:29 AM Stephan Ewen <[hidden email]> 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.


On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen <[hidden email]> wrote:
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert



--
Liu, Renjie
Software Engineer, MVAD

Reply | Threaded
Open this post in threaded view
|

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

Chesnay Schepler
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 need a better way to deal with this than me fixing it afterwards whenever it pops up. We may want to exclude all files without extensions in the test/resource folders, or look into a CI option to verify that the compilation on Windows works.

On 09.05.2017 09:43, Stephan Ewen wrote:
@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 <[hidden email]> wrote:
Hi, does this include the FLIP6?

On Tue, May 9, 2017 at 2:29 AM Stephan Ewen <[hidden email]> 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.


On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen <[hidden email]> wrote:
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert


--
Liu, Renjie
Software Engineer, MVAD


Reply | Threaded
Open this post in threaded view
|

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

Renjie Liu
In reply to this post by Stephan Ewen
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 <[hidden email]> wrote:
@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 <[hidden email]> wrote:
Hi, does this include the FLIP6?

On Tue, May 9, 2017 at 2:29 AM Stephan Ewen <[hidden email]> 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.


On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen <[hidden email]> wrote:
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert



--
Liu, Renjie
Software Engineer, MVAD

--
Liu, Renjie
Software Engineer, MVAD
Reply | Threaded
Open this post in threaded view
|

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

Stephan Ewen
@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 <[hidden email]> wrote:
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 <[hidden email]> wrote:
@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 <[hidden email]> wrote:
Hi, does this include the FLIP6?

On Tue, May 9, 2017 at 2:29 AM Stephan Ewen <[hidden email]> 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.


On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen <[hidden email]> wrote:
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert



--
Liu, Renjie
Software Engineer, MVAD

--
Liu, Renjie
Software Engineer, MVAD

Reply | Threaded
Open this post in threaded view
|

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

Renjie Liu
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 <[hidden email]> wrote:
@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 <[hidden email]> wrote:
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 <[hidden email]> wrote:
@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 <[hidden email]> wrote:
Hi, does this include the FLIP6?

On Tue, May 9, 2017 at 2:29 AM Stephan Ewen <[hidden email]> 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.


On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen <[hidden email]> wrote:
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 (redistribution in binary form, hence needs a notice of the copy)

  - The Table API / SQL module needs more entries for Janino / Reflections (both BSD licensed)

So that is definitely a blocker.


On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]> wrote:
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. DO NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.

I will prepare a google document to synchronize the testing effort a bit more.

Depending on the number of issues we identify, I hope that we can do the first VOTEing RC early next week.

---------------------------------------------------------------------

The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4, located here: http://git-wip-us.apache.org/repos/asf/flink/commit/f94c0029

The artifacts are located here: http://people.apache.org/~rmetzger/flink-1.3.0-rc0/ 


---------------------------------------------------------------------

Happy testing!

Regards,
Robert



--
Liu, Renjie
Software Engineer, MVAD

--
Liu, Renjie
Software Engineer, MVAD

--
Liu, Renjie
Software Engineer, MVAD
Reply | Threaded
Open this post in threaded view
|

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

rmetzger0
In reply to this post by Stephan Ewen
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 <[hidden email]> wrote:
@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 <[hidden email]> wrote:

> 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 <[hidden email]> wrote:
>
>> @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 <[hidden email]>
>> wrote:
>>
>>> Hi, does this include the FLIP6?
>>>
>>> On Tue, May 9, 2017 at 2:29 AM Stephan Ewen <[hidden email]> 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.
>>>>
>>>>
>>>> On Mon, May 8, 2017 at 8:25 PM, Stephan Ewen <[hidden email]> wrote:
>>>>
>>>>> 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 (redistribution in binary form,
>>>>> hence needs a notice of the copy)
>>>>>
>>>>>   - The Table API / SQL module needs more entries for Janino /
>>>>> Reflections (both BSD licensed)
>>>>>
>>>>> So that is definitely a blocker.
>>>>>
>>>>>
>>>>> On Mon, May 8, 2017 at 12:14 PM, Robert Metzger <[hidden email]>
>>>>> wrote:
>>>>>
>>>>>> 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. DO
>>>>>> NOT USE THIS RELEASE CANDIDATE IN PRODUCTION.
>>>>>>
>>>>>> I will prepare a google document to synchronize the testing effort a
>>>>>> bit more.
>>>>>>
>>>>>> Depending on the number of issues we identify, I hope that we can do
>>>>>> the first VOTEing RC early next week.
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> The release commit is f94c002991dcce9f1104f8e61b43efb2f8247cb4,
>>>>>> located here: http://git-wip-us.apache.org/repos/asf/flink/
>>>>>> commit/f94c0029
>>>>>>
>>>>>> The artifacts are located here: http://people.apache.
>>>>>> org/~rmetzger/flink-1.3.0-rc0/
>>>>>>
>>>>>> The maven staging repository is here: https://repository.
>>>>>> apache.org/content/repositories/orgapacheflink-1118
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> Happy testing!
>>>>>>
>>>>>> Regards,
>>>>>> Robert
>>>>>>
>>>>>>
>>>>>
>>>> --
>>> Liu, Renjie
>>> Software Engineer, MVAD
>>>
>>
>> --
> Liu, Renjie
> Software Engineer, MVAD
>