+1

Built from source
Run local examples
Checked version numbers in the poms
Validated check sums and signatures

Minor cosmetic thing to note:

The name of flink-parent (Apache Flink) in the maven build is still not
nice and the inception year is set to 2015 (should be 2014). It seems that
the commit fixing these only made to the master and not to release-0.8.

Reactor Summary:
[INFO]
[INFO] Apache Flink ...................................... SUCCESS [3.917s]
[INFO] flink-shaded ...................................... SUCCESS [3.135s]
[INFO] flink-core ........................................ SUCCESS [22.577s]
...

Best,

Marton


On Tue, Feb 10, 2015 at 5:31 PM, Robert Metzger <rmetz...@apache.org> wrote:

> Please vote on releasing the following candidate as Apache Flink version
> 0.8.1
>
> This is a bugfix release for 0.8.0.
>
> -------------------------------------------------------------
> The commit to be voted on is in the branch "release-0.8.0-rc3"
> (commit 70943ad5
> <http://git-wip-us.apache.org/repos/asf/flink/commit/70943ad5>):
> *http://git-wip-us.apache.org/repos/asf/flink/commit/70943ad5
> <http://git-wip-us.apache.org/repos/asf/flink/commit/70943ad5>*
>
> The release artifacts to be voted on can be found at:
> *http://people.apache.org/~rmetzger/flink-0.8.1-rc0/
> <http://people.apache.org/~rmetzger/flink-0.8.1-rc0/>*
>
> Release artifacts are signed with the following key:
> *https://people.apache.org/keys/committer/rmetzger.asc
> <https://people.apache.org/keys/committer/rmetzger.asc>*
>
> The staging repository for this release can be found at:
> *https://repository.apache.org/content/repositories/orgapacheflink-1029
> <https://repository.apache.org/content/repositories/orgapacheflink-1029>*
> -------------------------------------------------------------
>
>
> Please vote on releasing this package as Apache Flink 0.8.1.
>
> The vote is open for the next 72 hours and passes if a majority of at least
> three +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Flink 0.8.1
> [ ] -1 Do not release this package because ...
>

Reply via email to