Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

@Cliff: I think this is critical. There should be a 1.3.2 followup very soon (ideally next week, once that fix is in). On Fri, Jun 23, 2017 at 2:06 PM, Robert Metzger wrote: > I've created a PR for the release announcement. I'll publish it in ~3 > hours. >

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

I've created a PR for the release announcement. I'll publish it in ~3 hours. https://github.com/apache/flink-web/pull/68 On Thu, Jun 22, 2017 at 5:59 PM, Robert Metzger wrote: > Thanks for reporting the issue. > Sadly, the 1.3.1 vote has just passed and its going out now.

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

Thanks for reporting the issue. Sadly, the 1.3.1 vote has just passed and its going out now. However, I'll start a thread for the 1.3.2 release right away. On Thu, Jun 22, 2017 at 5:43 PM, Cliff Resnick wrote: > I'm also for adding

[RESULT][VOTE] Release Apache Flink 1.3.1 (RC2)

The vote time has passed and we've collected enough votes to release this RC as Flink 1.3.1. +1 votes: - Timo (binding) - Greg (binding) - Ismael (non-binding) - Gordon (non-binding) - Robert (binding) That's 5 votes, 3 binding ones. No 0 or -1 votes. On Thu, Jun 22, 2017 at 4:50 PM, Timo

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

+1 (binding) I tested the following: - built from source - tested the web interface - ran some streaming programs It seems that Flink cannot be built if the path contains spaces. I added an issue for this (https://issues.apache.org/jira/browse/FLINK-6987). It seems that this error was

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

+1 (binding) - verified source and binary signatures - verified source and binary checksums - verified LICENSEs - verified NOTICEs - built from source Greg > On Jun 21, 2017, at 3:46 AM, Robert Metzger wrote: > > Dear Flink community, > > Please vote on releasing the

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

+1`(non-binding) Checked signatures Run `mvn clean verify -Prelease` in a Ubuntu 17.04 LTS with kernel 4.8.0-56-generic and Oracle JDK 1.8.0_131 everything runs ok. On Thu, Jun 22, 2017 at 9:45 AM, Tzu-Li (Gordon) Tai wrote: > +1 > > - Built source with Scala 2.10 / Scala

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

+1 - Built source with Scala 2.10 / Scala 2.11, tests pass - Re-run serializer tests performed in RC1, tests pass - Tested FLINK-6921, FLINK-6948 (upgraded enum by appending new constants, restore successful) Best, Gordon On 22 June 2017 at 1:17:12 AM, Ted Yu (yuzhih...@gmail.com) wrote: +1

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

+1 Ran unit test suite which passed. On Wed, Jun 21, 2017 at 8:27 AM, Robert Metzger wrote: > +1 (binding) > > - Checked staging repository: ES5 connector is present > - quickstart-java points to 1.3.1 > - yarn session starts > - per-job YARN submission works / log files

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

+1 (binding) - Checked staging repository: ES5 connector is present - quickstart-java points to 1.3.1 - yarn session starts - per-job YARN submission works / log files look good. - Executed all tests listed here [1] without any issues / log files looked good afterwards - The source doesn't

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

+1 to release 1.3.1 as is. On 21.06.2017 17:06, Robert Metzger wrote: I see that this is an issue we should address, but on the other hand, there's a large list of issues we need to address with 1.3.1 already. If we keep delaying minor releases for every issue we find, we'll never release it :)

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

I see that this is an issue we should address, but on the other hand, there's a large list of issues we need to address with 1.3.1 already. If we keep delaying minor releases for every issue we find, we'll never release it :) On Wed, Jun 21, 2017 at 3:51 PM, Stefan Richter

Re: [VOTE] Release Apache Flink 1.3.1 (RC2)

Hi, I suggest to include https://issues.apache.org/jira/browse/FLINK-6964 to the release. Best, Stefan > Am 21.06.2017 um 09:46 schrieb Robert Metzger : > > Dear Flink community, > > Please vote on releasing the

[VOTE] Release Apache Flink 1.3.1 (RC2)

Dear Flink community, Please vote on releasing the following candidate as Apache Flink version 1.3.1. The commit to be voted on: *http://git-wip-us.apache.org/repos/asf/flink/commit/1ca6e5b6 * Branch: release-1.3.1-rc2 The release

Re: [CANCELLED] [VOTE] Release Apache Flink 1.3.1

Thanks @ Robert! @Fabian @Jack do you think the PRs are good to merged. I think we should try to merge these two PRs today. Best， SunJincheng 2017-06-19 20:56 GMT+08:00 Robert Metzger : > Thanks everybody for the testing of the RC1! > > I'm hereby cancelling the first RC

Re: [VOTE] Release Apache Flink 1.3.1

If we really have to introduce a special path in the serializer config for 1.3.1 to 1.3.2, then I would indeed suggest to cancel the RC1. If only this one commit is different between RC1 and RC2, we can do a reduced voting period for RC2. On Mon, Jun 19, 2017 at 2:02 PM, Till Rohrmann

Re: [VOTE] Release Apache Flink 1.3.1

No, I meant that if we include FLINK-6921 / FLINK-6948 in 1.3.1, we also still need to bump the version due to changes in FLINK-6948. So, that the version needs to be bumped would not be a reason to block 1.3.1 on it, because we have to do it either way. On 19 June 2017 at 7:33:25 PM, Till

Re: [VOTE] Release Apache Flink 1.3.1

Do you mean that we have to bump the version also without including FLINK-6921 and FLINK-6948? Wouldn't that be a release blocker then? I think that we actually introduced FLINK-6921 with [1]. Thus, the `ArrayIndexOutOfBoundsException` is specific to this release. However, I agree that the

Re: [VOTE] Release Apache Flink 1.3.1

The ScalaEnumSerializerConfigSnapshot would need a version bump regardless of whether or not the fixes are included in 1.3.1. In other words, we still need to bump the version if we include it for 1.3.1. I’m not against including FLINK-6921 and FLINK-6948 in for 1.3.1, but then as usual the

Re: [VOTE] Release Apache Flink 1.3.1

I think the EnumValueSerializer [1, 2] is broken in the current RC. This basically means that Flink programs won’t properly notice that state migration is required and or fail with obscure exceptions at migration check or runtime. This definitely will be enough reason for another bug fix release

Re: [VOTE] Release Apache Flink 1.3.1

+1 Tested the following blockers of 1.3.1: Serializers & checkpointing - Verified Scala jobs using Scala types as state (Scala collections, case classes, Either, Try, etc.) can restore from savepoints taken with Flink 1.2.1 & 1.3.1. Tested with Scala 2.10 & 2.11. - Tested restore of POJO types

Re: [VOTE] Release Apache Flink 1.3.1

+1 Ran unit test suite which passed. On Wed, Jun 14, 2017 at 7:14 AM, Robert Metzger wrote: > Dear Flink community, > > Please vote on releasing the following candidate as Apache Flink version > 1.3.1. > > The commit to be voted on: >

Re: [VOTE] Release Apache Flink 1.3.1

+1 (binding) - verified source and binary signatures - verified source and binary checksums - verified LICENSEs - verified NOTICEs - built from source Greg > On Jun 14, 2017, at 10:14 AM, Robert Metzger wrote: > > Dear Flink community, > > Please vote on releasing the

[VOTE] Release Apache Flink 1.3.1

Dear Flink community, Please vote on releasing the following candidate as Apache Flink version 1.3.1. The commit to be voted on: http://git-wip-us.apache.org/repos/asf/flink/commit/7cfe62b9 Branch: release-1.3.1-rc1 The release artifacts to be voted on can be found at: