Cancelling RC2. A few more fixes are landing in branch-4.2 that we'd like to include in 4.2.0, so I'll roll RC3 once they're in. Thanks to everyone who tested RC2.
I'll start the RC3 vote thread when the build is ready. Thanks, Huaxin On Thu, Jun 11, 2026 at 10:52 PM <[email protected]> wrote: > Please vote on releasing the following candidate as Apache Spark version > 4.2.0. > > The vote is open until Sun, 14 Jun 2026 23:51:09 PDT and passes if a > majority +1 PMC votes are cast, with > a minimum of 3 +1 votes. > > [ ] +1 Release this package as Apache Spark 4.2.0 > [ ] -1 Do not release this package because ... > > To learn more about Apache Spark, please see https://spark.apache.org/ > > The tag to be voted on is v4.2.0-rc2 (commit 8e1deb8da1d): > https://github.com/apache/spark/tree/v4.2.0-rc2 > > The release files, including signatures, digests, etc. can be found at: > https://dist.apache.org/repos/dist/dev/spark/v4.2.0-rc2-bin/ > > Signatures used for Spark RCs can be found in this file: > https://downloads.apache.org/spark/KEYS > > The staging repository for this release can be found at: > https://repository.apache.org/content/repositories/orgapachespark-1522/ > > The documentation corresponding to this release can be found at: > https://dist.apache.org/repos/dist/dev/spark/v4.2.0-rc2-docs/ > > The list of bug fixes going into 4.2.0 can be found at the following URL: > https://issues.apache.org/jira/projects/SPARK/versions/12356380 > > FAQ > > ========================= > 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 via "pip install > https://dist.apache.org/repos/dist/dev/spark/v4.2.0-rc2-bin/pyspark-4.2.0.tar.gz > " > and see if anything important breaks. > In the Java/Scala, you can add the staging repository to your project's > 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). > > --------------------------------------------------------------------- > To unsubscribe e-mail: [email protected] > >
