Dear Flink community,

Please vote on releasing the following candidate as Apache Flink version 1.0.2.

The commit to be voted on:
80211d64e5d9f0e4f7f5e41085fc6a0e61bcdc02

Branch:
release-1.0.2-rc1 (see
https://git1-us-west.apache.org/repos/asf/flink/?p=flink.git;a=shortlog;h=refs/heads/release-1.0.2-rc1)

The release artifacts to be voted on can be found at:
http://home.apache.org/~uce/flink-1.0.2-rc1/

The release artifacts are signed with the key with fingerprint 9D403309:
http://www.apache.org/dist/flink/KEYS

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/orgapacheflink-1090

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

The vote is open for the next 72 hours and passes if a majority of at least
three +1 PMC votes are cast.

The vote ends on Tuesday April 19, 2016 (not counting the weekend).

[ ] +1 Release this package as Apache Flink 1.0.2
[ ] -1 Do not release this package because ...

===================================

The following commits have been added since the 1.0.1 release (excluding docs),
most notably a performance optimization for the RocksDB state backend and a fix
for proper passing of dynamic YARN properties to the Client.

* ea50ed3 - [FLINK-3716] [kafka consumer] Decreasing socket timeout so
testFailOnNoBroker() will pass before JUnit timeout (29 hours ago)
<Todd Lisonbee>
* ff38202 - [FLINK-3730] Fix RocksDB Local Directory Initialization
(29 hours ago) <Aljoscha Krettek>
* 4f9c198 - [FLINK-3712] Make all dynamic properties available to the
CLI frontend (3 days ago) <Robert Metzger>
* 1554c9b - [FLINK-3688] WindowOperator.trigger() does not emit
Watermark anymore (6 days ago) <Konstantin Knauf>
* 43093e3 - [FLINK-3697] Properly access type information for nested
POJO key selection (6 days ago) <Robert Metzger>
* 17909aa - [FLINK-3654] Disable Write-Ahead-Log in RocksDB State (7
days ago) <Aljoscha Krettek>
* e0dc5c1 - [FLINK-3595] [runtime] Eagerly destroy buffer pools on
cancelling (10 days ago) <Ufuk Celebi>

Reply via email to