Please vote on releasing the following candidate as Apache Spark version 3.1.1.
The vote is open until February 15th 5PM PST and passes if a majority +1 PMC votes are cast, with a minimum of 3 +1 votes.
Note that it is 7 days this time because it is a holiday season in several countries including South Korea (where I live), China etc., and I would like to make sure people do not miss it because it is a holiday season.
[ ] +1 Release this package as Apache Spark 3.1.1
[ ] -1 Do not release this package because ...
The tag to be voted on is v3.1.1-rc2 (commit cf0115ac2d60070399af481b14566f33d22ec45e):
The release files, including signatures, digests, etc. can be found at:
Signatures used for Spark RCs can be found in this file:
The staging repository for this release can be found at:
The documentation corresponding to this release can be found at:
The list of bug fixes going into 3.1.1 can be found at the following URL:
This release is using the release script of the tag v3.1.1-rc2.
What happened to 3.1.0?
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
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 an out of date RC going forward).
What should happen to JIRA tickets still targeting 3.1.1?
The current list of open tickets targeted at 3.1.1 can be found at:
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 an
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 the previous
release. That being said, if there is something which is a regression
that has not been correctly targeted please ping me or a committer to
help target the issue.