Thank you all for your votes, but I'm very sorry to inform you that due to an issue discovered in the rc2 release script, I have decided to abandon RC2.
I will prepare RC3 as soon as possible. Thanks, Jie Yang On 2024/12/16 16:16:03 Dongjoon Hyun wrote: > +1 > > Thank you again. > > Dongjoon > > On Mon, Dec 16, 2024 at 2:36 AM Cheng Pan <pan3...@gmail.com> wrote: > > > +1 (non-binding) > > > > I tested it with Apache Iceberg and Apache Kyuubi. > > > > Thanks, > > Cheng Pan > > > > > > > > On Dec 16, 2024, at 16:33, 杨杰 <yangji...@apache.org> wrote: > > > > Please vote on releasing the following candidate as Apache Spark version > > 3.5.4. > > > > The vote is open until Dec 19, 09: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-rc2 (commit > > 91af6f9c16f773bdf84dce678eb6ab7b6acb90fd): > > https://github.com/apache/spark/tree/v3.5.4-rc2 > > > > The release files, including signatures, digests, etc. can be found at: > > https://dist.apache.org/repos/dist/dev/spark/v3.5.4-rc2-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-1473/ > > > > The documentation corresponding to this release can be found at: > > https://dist.apache.org/repos/dist/dev/spark/v3.5.4-rc2-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-rc2-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 > > > > > > > --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
