I just realised that the source release is ridiculously huge (it includes the binary ruby dependencies of the documentation, by accident). I'll create a new RC.
> On 27. Nov 2017, at 14:59, Stefan Richter <s.rich...@data-artisans.com> wrote: > > Hi, > > thanks for creating this PR Aljoscha! I tested Flink in a cluster setup on > Google Cloud, YARN-per-job, checked that for all backends that HA, recovery, > at-least-once, end-to-end exactly once (with Kafka11 Producer), savepoints, > externalized checkpoints, and rescaling work correctly. No problems found in > RC1. > > +1 (non-binding) from me. > > Best, > Stefan > >> Am 24.11.2017 um 14:53 schrieb Ted Yu <yuzhih...@gmail.com>: >> >> Long weekend should end this Sunday. >> Closing vote Wednesday would be great. >> Thanks >> -------- Original message --------From: Aljoscha Krettek >> <aljos...@apache.org> Date: 11/24/17 5:34 AM (GMT-08:00) To: >> dev@flink.apache.org Subject: Re: [VOTE] Release 1.4.0, release candidate #1 >> How long will the long weekend be? I thought about closing the vote on >> Wednesday, i.e. not count the weekend. Would that work? >> >> Best, >> Aljoscha >> >>> On 24. Nov 2017, at 12:18, Ted Yu <yuzhih...@gmail.com> wrote: >>> >>> Aljoscha: >>> Thanks for spinning RC. >>> >>> bq. The vote will be open for at least 72 hours >>> >>> As you are aware, it is long weekend in US. >>> >>> Is it possible to extend by 24 hours so that developers in US can >>> participate in validation ? >>> >>> Cheers >>> >>> On Fri, Nov 24, 2017 at 2:57 AM, Aljoscha Krettek <aljos...@apache.org> >>> wrote: >>> >>>> Hi everyone, >>>> >>>> Please review and vote on release candidate #1 for the version 1.4.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 F2A67A8047499BBB3908D17AA8F4FD97121D7293 [3], >>>> * all artifacts to be deployed to the Maven Central Repository [4], >>>> * source code tag "release-1.4.0-rc1" [5], >>>> * website pull request listing the new release [6]. >>>> >>>> Please have a careful look at the website PR because I changed some >>>> wording and we're now also releasing a binary without Hadoop dependencies. >>>> >>>> Please use this document for coordinating testing efforts: [7] >>>> >>>> The vote will be open for at least 72 hours. 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=12340533 >>>> [2] http://people.apache.org/~aljoscha/flink-1.4.0-rc1/ >>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS >>>> [4] https://repository.apache.org/content/repositories/orgapacheflink-1139 >>>> [5] https://git-wip-us.apache.org/repos/asf?p=flink.git;a=tag;h= >>>> a0b322cf77851d3b8589812a0c8e443e9e320e67 >>>> [6] https://github.com/apache/flink-web/pull/95 >>>> [7] https://docs.google.com/document/d/16fU1cpxoYf3o9cCDyakj7ZDnUoJTj >>>> 4_CEmMTpCkY81s/edit?usp=sharing >>>> >>>> Pro-tip: you can create a settings.xml file with these contents: >>>> >>>> <settings> >>>> <activeProfiles> >>>> <activeProfile>flink-1.4.0</activeProfile> >>>> </activeProfiles> >>>> <profiles> >>>> <profile> >>>> <id>flink-1.4.0</id> >>>> <repositories> >>>> <repository> >>>> <id>flink-1.4.0</id> >>>> <url> >>>> https://repository.apache.org/content/repositories/ >>>> orgapacheflink-1139/ >>>> </url> >>>> </repository> >>>> <repository> >>>> <id>archetype</id> >>>> <url> >>>> https://repository.apache.org/content/repositories/ >>>> orgapacheflink-1139/ >>>> </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. >> >
