Thank you for your voting. I have been aware of SPARK-51281 since Wenchen pinged me three days ago.
I just thought it was not going to be ready because the PR was idle for the last two days after my comment. Since SPARK-51281 is not a release blocker of Apache Spark 3.5.5 RC1 vote because - it's not a regression at 3.5.5 (as Wenchen mentioned) and - it didn't have a proper target version and priority field. I don't think we should stop this vote. SPARK-51281 can be a part of Apache Spark 3.5.6 release. I'll keep this vote open. Thanks, Dongjoon. On Sun, Feb 23, 2025 at 6:46 PM Wenchen Fan <cloud0...@gmail.com> wrote: > -0 as I just found a long-standing correctness bug: > https://github.com/apache/spark/pull/50040 > > It's not a regression in 3.5 so technically it's not a release blocker, > but it's better to include it as we are just about to release 3.5.5. > > On Mon, Feb 24, 2025 at 9:11 AM Mich Talebzadeh <mich.talebza...@gmail.com> > wrote: > >> +1 on the basis of Dongjoon statement which I trust >> >> HTH >> >> Dr Mich Talebzadeh, >> Architect | Data Science | Financial Crime | Forensic Analysis | GDPR >> >> view my Linkedin profile >> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> >> >> >> >> >> >> On Mon, 24 Feb 2025 at 00:47, Dongjoon Hyun <dongj...@apache.org> wrote: >> >>> I'll start with my +1. >>> >>> I have thoroughly verified all test results, signatures, checksums, and >>> the recently deprecated configuration. >>> >>> Dongjoon. >>> >>> On 2025/02/24 00:37:57 Dongjoon Hyun wrote: >>> > Please vote on releasing the following candidate as Apache Spark >>> version >>> > 3.5.5. >>> > >>> > The vote is open until February 27th 1AM (PST) 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.5 >>> > [ ] -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.5-rc1 (commit >>> > 7c29c664cdc9321205a98a14858aaf8daaa19db2) >>> > https://github.com/apache/spark/tree/v3.5.5-rc1 >>> > >>> > The release files, including signatures, digests, etc. can be found at: >>> > https://dist.apache.org/repos/dist/dev/spark/v3.5.5-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-1476/ >>> > >>> > The documentation corresponding to this release can be found at: >>> > https://dist.apache.org/repos/dist/dev/spark/v3.5.5-rc1-docs/ >>> > >>> > The list of bug fixes going into 3.5.5 can be found at the following >>> URL: >>> > https://issues.apache.org/jira/projects/SPARK/versions/12355518 >>> > >>> > This release is using the release script of the tag v3.5.5-rc1. >>> > >>> > 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 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.5? >>> > =========================================== >>> > >>> > The current list of open tickets targeted at 3.5.5 can be found at: >>> > https://issues.apache.org/jira/projects/SPARK and search for "Target >>> > Version/s" = 3.5.5 >>> > >>> > 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. >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe e-mail: dev-unsubscr...@spark.apache.org >>> >>>
