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 66431200D49 for ; Fri, 10 Nov 2017 05:58:56 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 64C46160C02; Fri, 10 Nov 2017 04:58:56 +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 84AB2160BEF for ; Fri, 10 Nov 2017 05:58:55 +0100 (CET) Received: (qmail 34525 invoked by uid 500); 10 Nov 2017 04:58:53 -0000 Mailing-List: contact dev-help@spark.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list dev@spark.apache.org Received: (qmail 34514 invoked by uid 99); 10 Nov 2017 04:58:53 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Nov 2017 04:58:53 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 9997918300A for ; Fri, 10 Nov 2017 04:58:52 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.379 X-Spam-Level: ** X-Spam-Status: No, score=2.379 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id zh_EG0YgeiSz for ; Fri, 10 Nov 2017 04:58:51 +0000 (UTC) Received: from mail-lf0-f50.google.com (mail-lf0-f50.google.com [209.85.215.50]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 7BB8E5F3CC for ; Fri, 10 Nov 2017 04:58:50 +0000 (UTC) Received: by mail-lf0-f50.google.com with SMTP id o66so1462470lfg.0 for ; Thu, 09 Nov 2017 20:58:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=xYIMi+RefNkC/F4lJ1RhpCOOoN4DNLOuLRfr0KLAwP8=; b=gBuE6jjBTaKD754l2NdK+oLg1WdDXHT1sUuUGhkGIQd1Tz9i4cPDFCsjsiJsp5P6+Q Ymml/vWOAczvwH401PvFnKI/pg60FtuWt/FQDYUZXrQhzG+gTXcRfrky+Q1IZHHhu3ju 6kyvaccgWf2ZGkfbOP/cUH854HQJG6TmY+k4tVhWJNKLuu59tjAvIa7lZ+Jt1DxQ+e77 pOOBbixgmvMxn79QIzlu8CfrdlEg+266HdJCVs3/7zjzkV0KtJ+JuvsIkFZl69dA42oE 4cVIiVQdMVIMVlc9vS7FEzF+7ywQV+dMLPaqVG6LhzRS2XWI/2kzdGbk9Fdi7mWMY4Rt DkfQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=xYIMi+RefNkC/F4lJ1RhpCOOoN4DNLOuLRfr0KLAwP8=; b=ItZP8BjmCNsNBiyYB40Da/fyk2hPRDFVfzfns4szvc7SBYloR/1IVH7WbQxAf03lJ7 zjs/iOaPl3C6uqlrKzQ+PeWIOMiUFo4PxyZlvU6674L8VWVxJ76UV+3I3lqX+Kp32MOv d8xyZnayW2PyepxRMq7V+0PGEkQSMFoqLtJAfk/1K0FP976tLg0IHGdk+bdKfI+AZ11y +PgEo94C62yeqHe+Z8CJUNjGzd5IWN0cir/5UxKMryxg+bmmT8WDMTrdHnDJY6J/muWK zjI6Hy9OPaooFVNHQJUXArbg0EKyzPQ2nFTOE6pjVG+18q9Mv7EkdYIWaq0f4maAkY5e r3dQ== X-Gm-Message-State: AJaThX46Vju1feuSIj9mf9Iyvi1RoR13FikAcM9PWX25izegA2NGjPEp ODR96NK0qwtJIkMDM3AgNm/gz/ThuTpOKQY/M7sdgA== X-Google-Smtp-Source: AGs4zMYESeEh1/Yn84A1BTHfa4ble4UQ7Wi2a6ytcvVKfWpZCShEz1E82RDApsNt6z8Rkx2WpBjBwzGMYUpTOKH3Os0= X-Received: by 10.46.23.153 with SMTP id 25mr1045879ljx.3.1510289929074; Thu, 09 Nov 2017 20:58:49 -0800 (PST) MIME-Version: 1.0 References: <194E0DA2-C730-4E84-B328-44542B05F1C7@protectwise.com> In-Reply-To: From: Nick Pentreath Date: Fri, 10 Nov 2017 04:58:38 +0000 Message-ID: Subject: Re: Timeline for Spark 2.3 To: dev Content-Type: multipart/alternative; boundary="94eb2c0804b4bafd61055d99c6a0" archived-at: Fri, 10 Nov 2017 04:58:56 -0000 --94eb2c0804b4bafd61055d99c6a0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable +1 I think that=E2=80=99s practical On Fri, 10 Nov 2017 at 03:13, Erik Erlandson wrote: > +1 on extending the deadline. It will significantly improve the logistics > for upstreaming the Kubernetes back-end. Also agreed, on the general > realities of reduced bandwidth over the Nov-Dec holiday season. > Erik > > On Thu, Nov 9, 2017 at 6:03 PM, Matei Zaharia > wrote: > >> I=E2=80=99m also +1 on extending this to get Kubernetes and other featur= es in. >> >> Matei >> >> > On Nov 9, 2017, at 4:04 PM, Anirudh Ramanathan >> wrote: >> > >> > This would help the community on the Kubernetes effort quite a bit - >> giving us additional time for reviews and testing for the 2.3 release. >> > >> > On Thu, Nov 9, 2017 at 3:56 PM, Justin Miller < >> justin.miller@protectwise.com> wrote: >> > That sounds fine to me. I=E2=80=99m hoping that this ticket can make i= t into >> Spark 2.3: https://issues.apache.org/jira/browse/SPARK-18016 >> > >> > It=E2=80=99s causing some pretty considerable problems when we alter t= he >> columns to be nullable, but we are OK for now without that. >> > >> > Best, >> > Justin >> > >> >> On Nov 9, 2017, at 4:54 PM, Michael Armbrust >> wrote: >> >> >> >> According to the timeline posted on the website, we are nearing branc= h >> cut for Spark 2.3. I'd like to propose pushing this out towards mid to >> late December for a couple of reasons and would like to hear what people >> think. >> >> >> >> 1. I've done release management during the Thanksgiving / Christmas >> time before and in my experience, we don't actually get a lot of testing >> during this time due to vacations and other commitments. I think beginni= ng >> the RC process in early January would give us the best coverage in the >> shortest amount of time. >> >> 2. There are several large initiatives in progress that given a littl= e >> more time would leave us with a much more exciting 2.3 release. >> Specifically, the work on the history server, Kubernetes and continuous >> processing. >> >> 3. Given the actual release date of Spark 2.2, I think we'll still ge= t >> Spark 2.3 out roughly 6 months after. >> >> >> >> Thoughts? >> >> >> >> Michael >> > >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe e-mail: dev-unsubscribe@spark.apache.org >> >> > --94eb2c0804b4bafd61055d99c6a0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
+1 I think that=E2=80=99s practical=C2=A0

<= div class=3D"gmail_quote">
On Fri, 10 Nov 2017 at 03:13, Erik Erlandson= <eerlands@redhat.com> wro= te:
+1 on extending the d= eadline. It will significantly improve the logistics for upstreaming the Ku= bernetes back-end.=C2=A0 Also agreed, on the general realities of reduced b= andwidth over the Nov-Dec holiday season.
Erik

On Thu, Nov 9, 2= 017 at 6:03 PM, Matei Zaharia <matei.zaharia@gmail.com> wrote:
=
I=E2=80=99m also +1 on extending this to get= Kubernetes and other features in.

Matei

> On Nov 9, 2017, at 4:04 PM, Anirudh Ramanathan <foxish@google.com.I= NVALID> wrote:
>
> This would help the community on the Kubernetes effort quite a bit - g= iving us additional time for reviews and testing for the 2.3 release.
>
> On Thu, Nov 9, 2017 at 3:56 PM, Justin Miller <justin.miller@protectwise.co= m> wrote:
> That sounds fine to me. I=E2=80=99m hoping that this ticket can make i= t into Spark 2.3: https://issues.apache.org/jira/br= owse/SPARK-18016
>
> It=E2=80=99s causing some pretty considerable problems when we alter t= he columns to be nullable, but we are OK for now without that.
>
> Best,
> Justin
>
>> On Nov 9, 2017, at 4:54 PM, Michael Armbrust <michael@databricks.com> w= rote:
>>
>> According to the timeline posted on the website, we are nearing br= anch cut for Spark 2.3.=C2=A0 I'd like to propose pushing this out towa= rds mid to late December for a couple of reasons and would like to hear wha= t people think.
>>
>> 1. I've done release management during the Thanksgiving / Chri= stmas time before and in my experience, we don't actually get a lot of = testing during this time due to vacations and other commitments. I think be= ginning the RC process in early January would give us the best coverage in = the shortest amount of time.
>> 2. There are several large initiatives in progress that given a li= ttle more time would leave us with a much more exciting 2.3 release. Specif= ically, the work on the history server, Kubernetes and continuous processin= g.
>> 3. Given the actual release date of Spark 2.2, I think we'll s= till get Spark 2.3 out roughly 6 months after.
>>
>> Thoughts?
>>
>> Michael
>
>


---------------------------------------------------------------= ------
To unsubscribe e-mail: dev-unsubscribe@spark.apache.org


--94eb2c0804b4bafd61055d99c6a0--