Hi, Kent.

Sorry but I need to cast -1 for RC3 inevitably.

Unlike RC0 and RC1 testing, I found that RC3 distribution fails to build
PySpark Docker image.

This is due to the external Java 17 docker image OS change (which happened
two days ago) instead of Spark binaries.

You can see the recent failures in branch-3.5 and branch-3.4 daily CIs, too.

- https://github.com/apache/spark/actions/workflows/build_branch35.yml
- https://github.com/apache/spark/actions/workflows/build_branch34.yml

The patch landed to all live release branches (branch-3.5 and branch-3.4)
now.

https://issues.apache.org/jira/browse/SPARK-49005
[SPARK-49005][K8S][3.5] Use 17-jammy tag instead of 17 to prevent Python
3.12
[SPARK-49005][K8S][3.4] Use `17-jammy` tag instead of `17-jre` to prevent
Python 3.12

FYI, Python 3.12 Support was added to Apache Spark 4.0.0 only and `master`
branch is not affected.

Dongjoon.


On Thu, Jul 25, 2024 at 6:06 AM Kent Yao <y...@apache.org> wrote:

> Hi dev,
>
> Please vote on releasing the following candidate as Apache Spark version
> 3.5.2.
>
> The vote is open until Jul 28, 13:00:00 AM UTC, and passes if a majority +1
> PMC votes are cast, with a minimum of 3 +1 votes.
>
> [ ] +1 Release this package as Apache Spark 3.5.2
> [ ] -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 v3.5.2-rc3 (commit
> ebda6a6a97bf0b3932b970801f4c2f5dc6ae81d4):
> https://github.com/apache/spark/tree/v3.5.2-rc3
>
> The release files, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v3.5.2-rc3-bin/
>
> Signatures used for Spark RCs can be found in this file:
> https://dist.apache.org/repos/dist/dev/spark/KEYS
>
> The staging repository for this release can be found at:
> https://repository.apache.org/content/repositories/orgapachespark-1459/
>
> The documentation corresponding to this release can be found at:
> https://dist.apache.org/repos/dist/dev/spark/v3.5.2-rc3-docs/
>
> The list of bug fixes going into 3.5.2 can be found at the following URL:
> https://issues.apache.org/jira/projects/SPARK/versions/12353980
>
> 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/v3.5.2-rc3-bin/pyspark-3.5.2.tar.gz
> "
> 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 an out of date RC going forward).
>
> ===========================================
> What should happen to JIRA tickets still targeting 3.5.2?
> ===========================================
>
> The current list of open tickets targeted at 3.5.2 can be found at:
> https://issues.apache.org/jira/projects/SPARK and search for
> "Target Version/s" = 3.5.2
>
> 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
> appropriate release.
>
> ==================
> 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.
>
> Thanks,
> Kent Yao
>
> ---------------------------------------------------------------------
> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
>
>

Reply via email to