Hi Bowen,

You're right, I didn't give a lot of thought to Kinesis because there were 
critical bugs in Kafka and incremental checkpointing that needed to be fixed 
quickly. It's not good to neglect another important connector for this, though. 
We should start focusing on the Kinesis issues next week and soon do a 1.3.3 
release that will then mostly contain the Kinesis fixes. What do you think?

Best,
Aljoscha

> On 5. Aug 2017, at 03:38, Greg Hogan <c...@greghogan.com> wrote:
> 
> Thanks Aljoscha!
> 
> +1 (binding)
> 
> - verified source and binary signatures
> - verified source and binary checksums
> - verified LICENSEs
> - verified NOTICEs
> - built from source
> 
> Greg
> 
>> On Aug 4, 2017, at 2:00 AM, Aljoscha Krettek <aljos...@apache.org> wrote:
>> 
>> Hi everyone,
>> 
>> Please review and vote on the release candidate #3 for the version 1.3.2, 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 [1],
>> * the official Apache source release and binary convenience releases to be 
>> deployed to dist.apache.org [2], which is signed with the key with 
>> fingerprint 0xA8F4FD97121D7293 [3],
>> * all artifacts to be deployed to the Maven Central Repository [4],
>> * source code tag "release-1.3.2-rc2" [5],
>> * website pull request listing the new release and adding announcement blog 
>> post [6]. 
>> 
>> The only change in this RC compared to the last is this commit that fixes 
>> copying of the Gelly examples jar: 
>> https://github.com/apache/flink/commit/fda455e23a6192200b85b84d3aee312c9be40c99.
>>  I would therefore like to propose a shorter voting period because the last 
>> RC was seemingly good except for this bug. Please voice your concerns about 
>> this if you have any. The vote will be open for at least 24 hours. It is 
>> adopted by majority approval, with at least 3 PMC affirmative votes.
>> 
>> Please use the provided document, as discussed before, for coordinating the 
>> testing efforts: [7]. I have copied over the cluster testing efforts and 
>> functional testing efforts since the code of this RC is exactly the same as 
>> RC2.
>> 
>> Thanks,
>> Aljoscha
>> 
>> [1] 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12340984
>> [2] http://people.apache.org/~aljoscha/flink-1.3.2-rc3/
>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> [4] https://repository.apache.org/content/repositories/orgapacheflink-1135/
>> [5] 
>> https://git-wip-us.apache.org/repos/asf?p=flink.git;a=tag;h=d0f7528a69a93045f4af686347753f8737ca0b2b
>> [6] https://github.com/apache/flink-web/pull/75
>> [7] 
>> https://docs.google.com/document/d/1OJAE6scAZXbSBaGNNEpU1qhr3Jb7bwbec7keEnT9hmA/edit?usp=sharing
> 

Reply via email to