[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [VOTE] Release 1.5.4, release candidate #1

+1 (binding)

- Checked all issues that went into the release (I found one JIRA issue that has been incorrectly marked) - Built from source (On my machine SelfJoinDeadlockITCase is failing due to a timeout, in the IDE it works correctly. I guess my machine was just too busy.)
- Run some end-to-end tests locally with success


Am 20.09.18 um 11:24 schrieb Tzu-Li (Gordon) Tai:
+1 (binding)

- Verified checksums / signatures
- Checked announcement PR in flink-web
- No new / changed dependencies
- Built from source (Hadoop-free, Scala 2.11)
- Run end-to-end tests locally, passes

On Thu, Sep 20, 2018 at 5:03 AM Fabian Hueske <fhueske@xxxxxxxxx> wrote:

+1 binding

* I checked the diffs and did not find any added dependencies or updated
dependency versions.
* I checked the sha hash and signatures of all release artifacts.

Best, Fabian

2018-09-15 23:26 GMT+02:00 Till Rohrmann <trohrmann@xxxxxxxxxx>:

Hi everyone,
Please review and vote on the release candidate #1 for the version 1.5.4,
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
deployed to dist.apache.org [2], which are signed with the key
with fingerprint 1F302569A96CFFD5 [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.5.4-rc1" [5],
* website pull request listing the new release and adding announcement
blog post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.5.4/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[5] https://github.com/apache/flink/tree/release-1.5.4-rc1
[6] https://github.com/apache/flink-web/pull/123


Pro-tip: you can create a settings.xml file with these contents:






And reference that in your maven commands via --settings
path/to/settings.xml. This is useful for creating a quickstart based on
staged release and for building against the staged jars.