[DISCUSS] Releasing Flink 1.3.3 with only critical fixes

[Aljoscha Krettek-2]

Hi,

We fixed a critical bug in the ZooKeeper checkpoint store but never released a 1.3.x version of Flink with the fix. I'm proposing to release 1.3.3 with only fixes for this issue so that users can benefit from the fix and we have the least amount of overhead in release verification as possible.

The fixes in question are:

 - https://issues.apache.org/jira/browse/FLINK-7783: Don't always remove checkpoints in ZooKeeperCompletedCheckpointStore#recover()
 - https://issues.apache.org/jira/browse/FLINK-8807: ZookeeperCompleted checkpoint store can get stuck in infinite loop
 - https://issues.apache.org/jira/browse/FLINK-8890: Compare checkpoints with order in CompletedCheckpoint.checkpointsMatch()
 - https://issues.apache.org/jira/browse/FLINK-8487: State loss after multiple restart attempts

What do you think?

Best,
Aljoscha

[bowen.li]

+1

On Thu, Mar 8, 2018 at 7:36 AM, Aljoscha Krettek <[hidden email]>
wrote:

> Hi,
>
> We fixed a critical bug in the ZooKeeper checkpoint store but never
> released a 1.3.x version of Flink with the fix. I'm proposing to release
> 1.3.3 with only fixes for this issue so that users can benefit from the fix
> and we have the least amount of overhead in release verification as
> possible.
>
> The fixes in question are:
>
>  - https://issues.apache.org/jira/browse/FLINK-7783: Don't always remove
> checkpoints in ZooKeeperCompletedCheckpointStore#recover()
>  - https://issues.apache.org/jira/browse/FLINK-8807: ZookeeperCompleted
> checkpoint store can get stuck in infinite loop
>  - https://issues.apache.org/jira/browse/FLINK-8890: Compare checkpoints
> with order in CompletedCheckpoint.checkpointsMatch()
>  - https://issues.apache.org/jira/browse/FLINK-8487: State loss after
> multiple restart attempts
>
> What do you think?
>
> Best,
> Aljoscha

[Ted Yu]

+1 to Aljoscha's proposal.

[Fabian Hueske-2]

+1

2018-03-08 10:20 GMT-08:00 Ted Yu <[hidden email]>:

> +1 to Aljoscha's proposal.
>

[Tzu-Li (Gordon) Tai]

+1 to have a minimal 1.3.3 release with the listed issues. I can also help
manage this release.

It seems like we don't have any objections with Aljoscha's proposal so far.
Will wait a little bit more for any other opinions, and try to open a RC by
the end of the week.

Cheers,
Gordon

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
不含病毒。www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Fri, Mar 9, 2018 at 4:21 AM, Fabian Hueske <[hidden email]> wrote:

> +1
>
> 2018-03-08 10:20 GMT-08:00 Ted Yu <[hidden email]>:
>
> > +1 to Aljoscha's proposal.
> >
>

[Chesnay Schepler-3]

Bear in mind that we have to update all JIRAs that were marked as
resolved for 1.3.3.

On 09.03.2018 08:47, Tzu-Li (Gordon) Tai wrote:

> +1 to have a minimal 1.3.3 release with the listed issues. I can also help
> manage this release.
>
> It seems like we don't have any objections with Aljoscha's proposal so far.
> Will wait a little bit more for any other opinions, and try to open a RC by
> the end of the week.
>
> Cheers,
> Gordon
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> 不含病毒。www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Fri, Mar 9, 2018 at 4:21 AM, Fabian Hueske <[hidden email]> wrote:
>
>> +1
>>
>> 2018-03-08 10:20 GMT-08:00 Ted Yu <[hidden email]>:
>>
>>> +1 to Aljoscha's proposal.
>>>