Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E0048200C4C for ; Tue, 4 Apr 2017 12:10:42 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DE8A7160B90; Tue, 4 Apr 2017 10:10:42 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D9E9D160B81 for ; Tue, 4 Apr 2017 12:10:41 +0200 (CEST) Received: (qmail 3694 invoked by uid 500); 4 Apr 2017 10:10:41 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 3682 invoked by uid 99); 4 Apr 2017 10:10:40 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Apr 2017 10:10:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 1B28D1A0041 for ; Tue, 4 Apr 2017 10:10:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.48 X-Spam-Level: ** X-Spam-Status: No, score=2.48 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=okkam-it.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id bPJOLI_cDm6g for ; Tue, 4 Apr 2017 10:10:35 +0000 (UTC) Received: from mail-vk0-f52.google.com (mail-vk0-f52.google.com [209.85.213.52]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 18C8C5FCD7 for ; Tue, 4 Apr 2017 10:10:34 +0000 (UTC) Received: by mail-vk0-f52.google.com with SMTP id s68so169094405vke.3 for ; Tue, 04 Apr 2017 03:10:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=okkam-it.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=PBWEfQdheo7uyRpKWOfk1Ohd6rMKgtVvyB29cVXBL58=; b=AhaWPo7Z4HDy/MlyFUFNaP2mnOAHTEHMEgxzbvnWv0KN7fmxFcqCwqXUvvJOW1u3VH ONrr8dcqQeN4UNt9cO5s3W5+mPjsWiRRgS/kcZaG9JUTXJDZAGAtB/fYP6wbWGxfTtzo sKl8k3hIShT1oqvxAV26UWVry4beptP7/jVUKTIpD2PwnoFsbXZ3jNXgK5dk2BXz+0wi TJhQT3p48PIeIwsdeMftmjjfLQoC85ZnrCa8llAMDBSHfoDG9WG07fw97aVlS+purdR1 w1/0EQ2j60VPt21kOu5pYvPgsstDmSQWP5LxYUkfLUD595VwkN/zO5069QoPu5fEizvK KM1g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=PBWEfQdheo7uyRpKWOfk1Ohd6rMKgtVvyB29cVXBL58=; b=OR5eMypdxLL7ASd1HvvkYkkMQHg3y/R8dS9Hgr69ICN9kWt8xiK4NkSewzjhOJ5dPm TU92g624m82NR9Z8/ODfo/PJSkB4TJj4CH+NU3HTh2Qkd1dEXUldr15Rv8S18VB4sil2 h1+XZaPBmq1RlLuQYSxSQMDOAIYDEUn7x08XrCV4KyQIZ6x91AMB5FYIWykd/ZGqVi2k Md6S+nDDtBHkce2D5y9UmjL7l9UycJfn8b6pVOlV8zz5RiiDpPdt6ua10qdARi+RVQ9Z QqVo9mI/dj6CCejTMPP64eB7PeKnFn+Q+gtHPiHCqJKgehqFuCP58LrsqzYlU54Vg4qo 5FIA== X-Gm-Message-State: AFeK/H1NOqIvMD5zSflTXIvO6Ceh73dqpuwqBcKiDLzem1TVBt360HAwCqhia5gNlJjO/UaxfTDs1Kot5boaUA== X-Received: by 10.176.64.34 with SMTP id h31mr11334123uad.89.1491300632793; Tue, 04 Apr 2017 03:10:32 -0700 (PDT) MIME-Version: 1.0 Received: by 10.31.137.83 with HTTP; Tue, 4 Apr 2017 03:10:12 -0700 (PDT) X-Originating-IP: [77.43.114.114] In-Reply-To: <58E36F8A.3080509@apache.org> References: <1490892629.2131341.928869232.60FFA7F9@webmail.messagingengine.com> <1490987182.1268448.930215936.2DE7B015@webmail.messagingengine.com> <1BBAF8A2-D66E-4510-8287-F13B16CB14A4@data-artisans.com> <77F23C7E-D0C1-4E9B-BE1A-5F33CC193A67@apache.org> <58E36F8A.3080509@apache.org> From: Flavio Pompermaier Date: Tue, 4 Apr 2017 12:10:12 +0200 Message-ID: Subject: Re: [VOTE] Release Apache Flink 1.2.1 (RC1) To: dev@flink.apache.org Content-Type: multipart/alternative; boundary=94eb2c122e4e78bc2a054c547cbb archived-at: Tue, 04 Apr 2017 10:10:43 -0000 --94eb2c122e4e78bc2a054c547cbb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Would it be possible to merge also the PR to fix FLINK-6103 ( https://github.com/apache/flink/pull/3598)....? On Tue, Apr 4, 2017 at 12:03 PM, Chesnay Schepler wrote: > We can merge the metric changes; I'll rebase the branch and merge them > within the next hours. > > On 04.04.2017 11:57, Robert Metzger wrote: > >> Thank you for opening a PR for this. >> >> Chesnay, do you need more reviews for the metrics changes / backports? >> >> Are there any other release blockers for 1.2.1, or are we good to go? >> >> On Mon, Apr 3, 2017 at 6:48 PM, Aljoscha Krettek >> wrote: >> >> I created a PR for the revert: https://github.com/apache/flink/pull/3664 >>> >>> On 3. Apr 2017, at 18:32, Stephan Ewen wrote: >>>> >>>> +1 for options (1), but also invest the time to fix it properly for >>>> 1.2.2 >>>> >>>> >>>> On Mon, Apr 3, 2017 at 9:10 AM, Kostas Kloudas < >>>> >>> k.kloudas@data-artisans.com> >>> >>>> wrote: >>>> >>>> +1 for 1 >>>>> >>>>> On Apr 3, 2017, at 5:52 PM, Till Rohrmann >>>>>> >>>>> wrote: >>> >>>> +1 for option 1) >>>>>> >>>>>> On Mon, Apr 3, 2017 at 5:48 PM, Fabian Hueske >>>>>> >>>>> wrote: >>> >>>> +1 to option 1) >>>>>>> >>>>>>> 2017-04-03 16:57 GMT+02:00 Ted Yu : >>>>>>> >>>>>>> Looks like #1 is better - 1.2.1 would be at least as stable as 1.2.= 0 >>>>>>>> >>>>>>>> Cheers >>>>>>>> >>>>>>>> On Mon, Apr 3, 2017 at 7:39 AM, Aljoscha Krettek < >>>>>>>> >>>>>>> aljoscha@apache.org> >>> >>>> wrote: >>>>>>>> >>>>>>>> Just so we=E2=80=99re all on the same page. ;-) >>>>>>>>> >>>>>>>>> There was https://issues.apache.org/jira/browse/FLINK-5808 which >>>>>>>>> >>>>>>>> was >>> >>>> a >>>>> >>>>>> bug that we initially discovered in Flink 1.2 which was/is about >>>>>>>>> >>>>>>>> missing >>>>>>> >>>>>>>> verification for the correctness of the combination of parallelism >>>>>>>>> >>>>>>>> and >>> >>>> max-parallelism. Due to lacking test coverage this introduced two >>>>>>>>> >>>>>>>> more >>> >>>> bugs: >>>>>>>> >>>>>>>>> - https://issues.apache.org/jira/browse/FLINK-6188: Some >>>>>>>>> setParallelism() methods can't cope with default parallelism >>>>>>>>> - https://issues.apache.org/jira/browse/FLINK-6209: >>>>>>>>> StreamPlanEnvironment always has a parallelism of 1 >>>>>>>>> >>>>>>>>> IMHO, the options are: >>>>>>>>> 1) revert the changes made for FLINK-5808 on the release-1.2 bran= ch >>>>>>>>> >>>>>>>> and >>>>>>> >>>>>>>> live with the bug still being present >>>>>>>>> 2) put in more work to fix FLINK-5808 which requires fixing some >>>>>>>>> >>>>>>>> problems >>>>>>>> >>>>>>>>> that have existed for a long time with how the parallelism is set >>>>>>>>> in >>>>>>>>> streaming programs >>>>>>>>> >>>>>>>>> Best, >>>>>>>>> Aljoscha >>>>>>>>> >>>>>>>>> On 31. Mar 2017, at 21:34, Robert Metzger >>>>>>>>>> >>>>>>>>> wrote: >>>>>>> >>>>>>>> I don't know what is best to do, but I think releasing 1.2.1 with >>>>>>>>>> potentially more bugs than 1.2.0 is not a good option. >>>>>>>>>> I suspect a good workaround for FLINK-6188 >>>>>>>>>> is setting th= e >>>>>>>>>> parallelism manually for operators that can't cope with the >>>>>>>>>> default >>>>>>>>>> >>>>>>>>> -1 >>>>>>> >>>>>>>> parallelism. >>>>>>>>>> >>>>>>>>>> On Fri, Mar 31, 2017 at 9:06 PM, Aljoscha Krettek < >>>>>>>>>> >>>>>>>>> aljoscha@apache.org >>>>>>> >>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> You mean reverting the changes around FLINK-5808 [1]? This is wh= at >>>>>>>>>>> introduced the follow-up FLINK-6188 [2]. >>>>>>>>>>> >>>>>>>>>>> [1] https://issues.apache.org/jira/browse/FLINK-5808 >>>>>>>>>>> [2]https://issues.apache.org/jira/browse/FLINK-6188 >>>>>>>>>>> >>>>>>>>>>> On Fri, Mar 31, 2017, at 19:10, Robert Metzger wrote: >>>>>>>>>>> >>>>>>>>>>>> I think reverting FLINK-6188 for the 1.2 branch might be a goo= d >>>>>>>>>>>> >>>>>>>>>>> idea. >>>>>>> >>>>>>>> FLINK-6188 introduced two new bugs, so undoing the FLINK-6188 fix >>>>>>>>>>>> >>>>>>>>>>> will >>>>>>>> >>>>>>>>> lead >>>>>>>>>>>> only to one known bug in 1.2.1, instead of an uncertain number >>>>>>>>>>>> of >>>>>>>>>>>> >>>>>>>>>>> issues. >>>>>>>>> >>>>>>>>>> So 1.2.1 is not going to be worse than 1.2.0 >>>>>>>>>>>> >>>>>>>>>>>> The fix will hopefully make it into 1.2.2 then. >>>>>>>>>>>> >>>>>>>>>>>> Any other thoughts on this? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Mar 31, 2017 at 6:46 PM, Fabian Hueske < >>>>>>>>>>>> >>>>>>>>>>> fhueske@gmail.com> >>> >>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> I merged the fix for FLINK-6044 to the release-1.2 and >>>>>>>>>>>>> >>>>>>>>>>>> release-1.1 >>> >>>> branch. >>>>>>>>>>> >>>>>>>>>>>> 2017-03-31 15:02 GMT+02:00 Fabian Hueske : >>>>>>>>>>>>> >>>>>>>>>>>>> We should also backport the fix for FLINK-6044 to Flink 1.2.1= . >>>>>>>>>>>>>> >>>>>>>>>>>>>> I'll take care of that. >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2017-03-30 18:50 GMT+02:00 Aljoscha Krettek < >>>>>>>>>>>>>> >>>>>>>>>>>>> aljoscha@apache.org >>> >>>> : >>>>>>>> >>>>>>>>> https://issues.apache.org/jira/browse/FLINK-6188 turns out to >>>>>>>>>>>>>>> >>>>>>>>>>>>>> be >>>>>>> >>>>>>>> a >>>>>>>> >>>>>>>>> bit >>>>>>>>>>> >>>>>>>>>>>> more involved, see my comments on the PR: >>>>>>>>>>>>>>> https://github.com/apache/flink/pull/3616. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> As I said there, maybe we should revert the commits regardi= ng >>>>>>>>>>>>>>> parallelism/max-parallelism changes and release and then fi= x >>>>>>>>>>>>>>> >>>>>>>>>>>>>> it >>> >>>> later. >>>>>>>>>>> >>>>>>>>>>>> On Wed, Mar 29, 2017, at 23:08, Aljoscha Krettek wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I commented on FLINK-6214: I think it's working as intende= d, >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> although >>>>>>>>>>> >>>>>>>>>>>> we >>>>>>>>>>>>> >>>>>>>>>>>>>> could fix the javadoc/doc. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Wed, Mar 29, 2017, at 17:35, Timo Walther wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> A user reported that all tumbling and slinding window >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> assigners >>>>>>> >>>>>>>> contain >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> a pretty obvious bug about offsets. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/FLINK-6214 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> I think we should also fix this for 1.2.1. What do you >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> think? >>> >>>> Regards, >>>>>>>>>>>>>>>>> Timo >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Am 29/03/17 um 11:30 schrieb Robert Metzger: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Hi Haohui, >>>>>>>>>>>>>>>>>> I agree that we should fix the parallelism issue. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Otherwise, >>> >>>> the >>>>>>>>>>> >>>>>>>>>>>> 1.2.1 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> release would introduce a new bug. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Tue, Mar 28, 2017 at 11:59 PM, Haohui Mai < >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> ricetons@gmail.com> >>>>>>>>>>> >>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -1 (non-binding) >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> We recently found out that all jobs submitted via UI wi= ll >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> have a >>>>>>>>>>> >>>>>>>>>>>> parallelism of 1, potentially due to FLINK-5808. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Filed FLINK-6209 to track it. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> ~Haohui >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> On Mon, Mar 27, 2017 at 2:59 AM Chesnay Schepler < >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> chesnay@apache.org> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> If possible I would like to include FLINK-6183 & >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> FLINK-6184 >>> >>>> as >>>>>>>>>>> >>>>>>>>>>>> well. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> They fix 2 metric-related issues that could arise when a >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Task is >>>>>>>>>>> >>>>>>>>>>>> cancelled very early. (like, right away) >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> FLINK-6183 fixes a memory leak where the TaskMetricGro= up >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> was >>>>>>> >>>>>>>> never closed >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> FLINK-6184 fixes a NullPointerExceptions in the buffer >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> metrics >>>>>>>>>>> >>>>>>>>>>>> PR here: https://github.com/apache/flink/pull/3611 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> On 26.03.2017 12:35, Aljoscha Krettek wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I opened a PR for FLINK-6188: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> https://github.com/apache/ >>> >>>> flink/pull/3616 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> This improves the previously very sparse test coverag= e >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> for >>> >>>> timestamp/watermark assigners and fixes the bug. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> On 25 Mar 2017, at 10:22, Ufuk Celebi >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> I agree with Aljoscha. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> -1 because of FLINK-6188 >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> On Sat, Mar 25, 2017 at 9:38 AM, Aljoscha Krettek < >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> aljoscha@apache.org> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I filed this issue, which was observed by a user: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> https://issues.apache.org/jira/browse/FLINK-6188 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> I think that=E2=80=99s blocking for 1.2.1. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> On 24 Mar 2017, at 18:57, Ufuk Celebi < >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> uce@apache.org> >>> >>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> RC1 doesn't contain Stefan's backport for the >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Asynchronous >>>>>>>>>>> >>>>>>>>>>>> snapshots >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> for heap-based keyed state that has been merged. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Should >>> >>>> we >>>>>>>>>>> >>>>>>>>>>>> create >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> RC2 >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> with that fix since the voting period only starts on >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Monday? >>>>>>>>>>> >>>>>>>>>>>> I think >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> it would only mean rerunning the scripts on your >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> side, >>> >>>> right? >>>>>>>>>>>>> >>>>>>>>>>>>>> =E2=80=93 Ufuk >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> On Fri, Mar 24, 2017 at 3:05 PM, Robert Metzger < >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> rmetzger@apache.org> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Dear Flink community, >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> Please vote on releasing the following candidate = as >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Apache >>>>>>>>>>> >>>>>>>>>>>> Flink >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> version 1.2 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> .1. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> The commit to be voted on: >>>>>>>>>>>>>>>>>>>>>>>>> *732e55bd* (* >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> http://git-wip-us.apache.org/r >>>>>>>>>>>>>>>>>>>> epos/asf/flink/commit/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> 732e55bd >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> repos/asf/flink/commit/732e55b >>>>>>>>>>>>> >>>>>>>>>>>>>> d>*) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Branch: >>>>>>>>>>>>>>>>>>>>>>>>> release-1.2.1-rc1 >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> The release artifacts to be voted on can be found >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> at: >>> >>>> *http://people.apache.org/~ >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> rmetzger/flink-1.2.1-rc1/ >>> >>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> rmetzger/flink-1.2.1-rc1/ >>> >>>> * >>>>>>>> >>>>>>>>> The release artifacts are signed with the key with >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> fingerprint >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> D9839159: >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> http://www.apache.org/dist/flink/KEYS >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> The staging repository for this release can be >>>>>>>>>>>>>>>>>>>>>>>>> found >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> at: >>>>>>>>>>> >>>>>>>>>>>> https://repository.apache.org/ >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> content/repositories/orgapache >>>>>>>>>>> >>>>>>>>>>>> flink-1116 >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>> >>>>>>>>>>>>>> - >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> The vote ends on Wednesday, March 29, 2017, 3pm >>>>>>>>>>>>>>>>>>>>>>>>> CET. >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>> [ ] +1 Release this package as Apache Flink 1.2.1 >>>>>>>>>>>>>>>>>>>>>>>>> [ ] -1 Do not release this package, because ... >>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>> >>>>> >>> > --=20 Flavio Pompermaier Development Department OKKAM S.r.l. Tel. +(39) 0461 1823908 --94eb2c122e4e78bc2a054c547cbb--