spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Graves <>
Subject Re: [VOTE] Apache Spark 2.1.1 (RC4)
Date Fri, 28 Apr 2017 14:16:52 GMT
Tom Graves 

    On Thursday, April 27, 2017 5:37 PM, vaquar khan <> wrote:

Regards, Vaquar khan
On Apr 27, 2017 4:11 PM, "Holden Karau" <> wrote:

+1 (non-binding) PySpark packaging issue from the earlier RC seems to have been fixed.
On Thu, Apr 27, 2017 at 1:23 PM, Dong Joon Hyun <> wrote:

I’ve got the same result (Scala/R test) on JDK 1.8.0_131 at this time.
From: Reynold Xin <>
Date: Thursday, April 27, 2017 at 1:06 PM
To: Michael Armbrust <>, "" <>
Subject: Re: [VOTE] Apache Spark 2.1.1 (RC4)

On Thu, Apr 27, 2017 at 11:59 AM Michael Armbrust <> wrote:

I'll also +1
On Thu, Apr 27, 2017 at 4:20 AM, Sean Owen <> wrote:

+1 , same result as with the last RC. All checks out for me.

On Thu, Apr 27, 2017 at 1:29 AM Michael Armbrust <> wrote:

Please vote on releasing the following candidate as Apache Spark version 2.1.1. The vote is
open until Sat, April 29th, 2018 at 18:00 PST and passes if a majority of at least 3 +1 PMC votes are
[ ] +1 Release this package as Apache Spark 2.1.1[ ] -1 Do not release this package because

To learn more about Apache Spark, please see
The tag to be voted on is v2.1.1-rc4 (267aca5bd504230 3a718d10635bc0d1a1596853f)
List of JIRA tickets resolved can be found with this filter.
The release files, including signatures, digests, etc. can be found at:
ll/spark-releases/spark-2.1.1- rc4-bin/
Release artifacts are signed with the following key: /committer/pwendell.asc
The staging repository for this release can be found at: content/repositories/orgapache
The documentation corresponding to this release can be found at:
dell/spark-releases/spark-2.1. 1-rc4-docs/

How can I help test this release?
If you are a Spark user, you can help us test this release by taking an existing Spark workload
and running on this release candidate, then reporting any regressions.
What should happen to JIRA tickets still targeting 2.1.1?
Committers should look at those and triage. Extremely important bug fixes, documentation,
and API tweaks that impact compatibility should be worked on immediately. Everything else
please retarget to 2.1.2 or 2.2.0.
But my bug isn't fixed!??!
In order to make timely releases, we will typically not hold the release unless the bug in
question is a regression from 2.1.0.
What happened to RC1?
There were issues with the release packaging and as a result was skipped.

Cell : 425-233-8271Twitter: holdenkarau

View raw message