Thank you everyone for your votes. But I have found that branch-3.5 is missing the fix for the issue introduced in https://github.com/apache/spark/pull/48767, which is addressed by https://github.com/apache/spark/pull/49021，and this has caused a regression on branch-3.5.
So I suggest abandoning current release candidate. If possible, I plan to release the next release candidate (RC2) on Monday, December 16th, 2024. Best Regards, Jie Yang On 2024/12/10 01:39:02 Ruifeng Zheng wrote: > +1 > > Thank you so much, Lucifer! > > On Tue, Dec 10, 2024 at 12:18 AM Dongjoon Hyun <dongj...@apache.org> wrote: > > > +1 > > > > It looks good to me. Thank you so much, Jie. > > > > Dongjoon. > > > > On 2024/12/09 12:21:07 Terry Wang wrote: > > > +1 (non-binding) > > > > > > Have checked release files, including signatures, digests all are valid! > > > > > > Thanks! > > > > > > On Mon, Dec 9, 2024 at 3:07 PM Kent Yao <y...@apache.org> wrote: > > > > > > > +1(binding). Thank you, Jie > > > > > > > > Kent > > > > > > > > 杨杰 <yangji...@apache.org> 于2024年12月9日周一 14:37写道： > > > > > > > >> Please vote on releasing the following candidate as Apache Spark > > version > > > >> 3.5.4. > > > >> > > > >> The vote is open until Dec 12, 7:00:00 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.4 > > > >> [ ] -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.4-rc1 (commit > > > >> 929a19fe1604e07adf9ed2798ec0c1b53e0bd60d): > > > >> https://github.com/apache/spark/tree/v3.5.4-rc1 > > > >> > > > >> The release files, including signatures, digests, etc. can be found > > at: > > > >> https://dist.apache.org/repos/dist/dev/spark/v3.5.4-rc1-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-1471/ > > > >> > > > >> The documentation corresponding to this release can be found at: > > > >> https://dist.apache.org/repos/dist/dev/spark/v3.5.4-rc1-docs/ > > > >> > > > >> The list of bug fixes going into 3.5.4 can be found at the following > > URL: > > > >> https://issues.apache.org/jira/projects/SPARK/versions/12355093 > > > >> > > > >> 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.4-rc1-bin/pyspark-3.5.4.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 a out of date RC going forward). > > > >> > > > >> =========================================== > > > >> What should happen to JIRA tickets still targeting 3.5.4? > > > >> =========================================== > > > >> > > > >> The current list of open tickets targeted at 3.5.4 can be found at: > > > >> "Target Version/s" = 3.5.4 > > > >> > > > >> 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, > > > >> Jie Yang > > > >> > > > > > > > > > > -- > > > Best Regards, > > > Terry Wang > > > > > > > --------------------------------------------------------------------- > > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
