Unfortunately, I have to revise my vote to -1, because we found a bug in the request partition state RPC call [1]. This bug lets certain batch jobs fail.
[1] https://issues.apache.org/jira/browse/FLINK-9406 Cheers, Till On Sat, May 19, 2018 at 9:17 AM, Thomas Weise <t...@apache.org> wrote: > +1 > > - verified signatures and hashes > - built Kinesis connector from source archive > - run Kinesis consumer against AWS - PASSED > - run Kinesis consumer against Kinesalite - FAILED > https://issues.apache.org/jira/browse/FLINK-9402 > > Thomas > > > On Thu, May 17, 2018 at 5:50 PM, Till Rohrmann <trohrm...@apache.org> > wrote: > > > Hi everyone, > > > > Please review and vote on the release candidate #4 for the version 1.5.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 [1], > > * the official Apache source release and binary convenience releases to > be > > 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.0-rc3" [5], > > > > Please use this document for coordinating testing efforts: [6] > > > > Since the newly included fixes affect only individual components and are > > covered by tests, I will keep the voting period of the RC3 which goes at > > least until tomorrow 5:30pm CET. It is adopted by majority approval, with > > at least 3 PMC affirmative votes. > > > > Thanks, > > Your friendly Release Manager > > > > [1] > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > projectId=12315522&version=12341764 > > [2] http://people.apache.org/~trohrmann/flink-1.5.0-rc4/ > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS > > [4] https://repository.apache.org/content/repositories/ > > orgapacheflink-1159/ > > [5] > > https://git-wip-us.apache.org/repos/asf?p=flink.git;a=commit;h= > > 953f45316b09072e76f3cf3d37d704a7cb7b32c6 > > [6] > > https://docs.google.com/document/d/13evetGNVeGvSufeqC0bcfiHGS_ > > v8n06I0p6nEtaQzS4/edit?usp=sharing > > > > Pro-tip: you can create a settings.xml file with these contents: > > > > <settings> > > <activeProfiles> > > <activeProfile>flink-1.5.0</activeProfile> > > </activeProfiles> > > <profiles> > > <profile> > > <id>flink-1.5.0</id> > > <repositories> > > <repository> > > <id>flink-1.5.0</id> > > <url> > > > > https://repository.apache.org/content/repositories/orgapacheflink-1159/ > > </url> > > </repository> > > <repository> > > <id>archetype</id> > > <url> > > > > https://repository.apache.org/content/repositories/orgapacheflink-1159/ > > </url> > > </repository> > > </repositories> > > </profile> > > </profiles> > > </settings> > > > > 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. > > >
