Re: [VOTE] Release 1.6.0, release candidate #3
After careful consideration, I think that it makes sense to change the order of serialisation for state values with TTL. It will simplify further optimisations and feature improvements.
If it is still possible, I would ask to include this PR to the release candidate:
This change will help to avoid compatibility issues in future.
Sorry for the short notice.
> On 7 Aug 2018, at 10:01, Till Rohrmann <trohrmann@xxxxxxxxxx> wrote:
> Hi everyone,
> Please review and vote on the release candidate #3 for the version 1.6.0,
> as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
> The complete staging area is available for your review, which includes:
> * JIRA release notes ,
> * the official Apache source release and binary convenience releases to be
> deployed to dist.apache.org , which are signed with the key with
> fingerprint 1F302569A96CFFD5 ,
> * all artifacts to be deployed to the Maven Central Repository ,
> * source code tag "release-1.6.0-rc3" ,
> Please use this document for coordinating testing efforts: 
> The vote will be shortened since we only added minor fixes on top of the RC
> 2. It will close on Wednesday 6:30pm CET. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
> Your friendly Release Manager
>  https://dist.apache.org/repos/dist/dev/flink/flink-1.6.0/
>  https://dist.apache.org/repos/dist/release/flink/KEYS
>  https://repository.apache.org/content/repositories/orgapacheflink-1177
>  https://github.com/apache/flink/tree/release-1.6.0-rc3
> Pro-tip: you can create a settings.xml file with these contents:
> And reference that in you maven commands via --settings
> path/to/settings.xml. This is useful for creating a quickstart based on the
> staged release and for building against the staged jars.