spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Cheung <>
Subject Re: [VOTE] Spark 2.3.0 (RC4)
Date Sun, 18 Feb 2018 10:05:22 GMT
Quick questions:

is there search link for sql functions quite right?

this file shouldn't be included?

From: Sameer Agarwal <>
Sent: Saturday, February 17, 2018 1:43:39 PM
To: Sameer Agarwal
Cc: dev
Subject: Re: [VOTE] Spark 2.3.0 (RC4)

I'll start with a +1 once again.

All blockers reported against RC3 have been resolved and the builds are healthy.

On 17 February 2018 at 13:41, Sameer Agarwal <<>>
Please vote on releasing the following candidate as Apache Spark version 2.3.0. The vote is
open until Thursday February 22, 2018 at 8:00:00 am UTC and passes if a majority of at least
3 PMC +1 votes are cast.

[ ] +1 Release this package as Apache Spark 2.3.0

[ ] -1 Do not release this package because ...

To learn more about Apache Spark, please see

The tag to be voted on is v2.3.0-rc4: (44095cb65500739695b0324c177c19dfa1471472)

List of JIRA tickets resolved in this release can be found here:

The release files, including signatures, digests, etc. can be found at:

Release artifacts are signed with the following key:

The staging repository for this release can be found at:

The documentation corresponding to this release can be found at:


What are the unresolved issues targeted for 2.3.0?

Please see At the time of writing, there are currently no known
release blockers.

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.

If you're working in PySpark you can set up a virtual env and install the current RC and see
if anything important breaks, in the Java/Scala you can add the staging repository to your
projects resolvers and test with the RC (make sure to clean up the artifact cache before/after
so you don't end up building with a out of date RC going forward).

What should happen to JIRA tickets still targeting 2.3.0?

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.3.1 or 2.4.0 as appropriate.

Why is my bug not fixed?

In order to make timely releases, we will typically not hold the release unless the bug in
question is a regression from 2.2.0. That being said, if there is something which is a regression
from 2.2.0 and has not been correctly targeted please ping me or a committer to help target
the issue (you can see the open issues listed as impacting Spark 2.3.0 at

Sameer Agarwal
Computer Science | UC Berkeley

View raw message