+1 for driving this and for volunteering On Sat, Jan 10, 2026 at 4:34 AM Ángel Álvarez Pascua < [email protected]> wrote:
> +1 > > El sáb, 10 ene 2026, 13:30, Kent Yao <[email protected]> escribió: > >> +1, thank you for driving this, Dongjoon >> >> Kent >> >> On 2026/01/10 09:31:46 Holden Karau wrote: >> > +1 thanks for taking it on :) >> > >> > Twitter: https://twitter.com/holdenkarau >> > Fight Health Insurance: https://www.fighthealthinsurance.com/ >> > <https://www.fighthealthinsurance.com/?q=hk_email> >> > Books (Learning Spark, High Performance Spark, etc.): >> > https://amzn.to/2MaRAG9 <https://amzn.to/2MaRAG9> >> > YouTube Live Streams: https://www.youtube.com/user/holdenkarau >> > Pronouns: she/her >> > >> > >> > On Sat, Jan 10, 2026 at 1:23 AM Hyukjin Kwon <[email protected]> >> wrote: >> > >> > > +1 >> > > >> > > On Sat, Jan 10, 2026 at 10:21 AM Dongjoon Hyun < >> [email protected]> >> > > wrote: >> > > >> > >> Hi all. >> > >> >> > >> Since Apache Spark v3.5.7 tag was created on 2025-09-18, a total of >> 34 >> > >> patches have been merged, including several correctness and security >> fixes. >> > >> A subset of these changes has already been validated through the >> Apache >> > >> Spark 4.1.0 and 4.1.1 release processes. >> > >> >> > >> https://github.com/apache/spark/releases/tag/v3.5.7 (2025-09-18) >> > >> >> > >> $ git log --oneline v3.5.7..HEAD | wc -l >> > >> 34 >> > >> >> > >> In addition to the recent discussion on 3.5.x LTS maintenance (see >> > >> “[DISCUSS]: Extend LTS release support period w/security fixes”), our >> > >> established release cadence also suggests that it is an appropriate >> time to >> > >> prepare the next maintenance release, Apache Spark 3.5.8, targeting >> around >> > >> 2026-01-18. >> > >> >> > >> With that context, I would like to propose proceeding with the Apache >> > >> Spark 3.5.8 release, and I volunteer to serve as the release manager. >> > >> >> > >> Feedback is very welcome. >> > >> >> > >> Best regards, >> > >> Dongjoon >> > >> >> > > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe e-mail: [email protected] >> >> -- John Zhuge
