I think we should consider a patch release of 3.5.10 as well +1.
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 Tue, Nov 10, 2026 at 7:14 PM Jungtaek Lim <[email protected]> wrote: > +1 thanks Szehon! > > On Wed, Nov 11, 2026 at 11:28 AM Wenchen Fan <[email protected]> wrote: > >> +1 >> >> On Wed, Nov 11, 2026 at 3:09 AM Peter Toth <[email protected]> wrote: >> >>> +1, thanks Szehon for driving this. >>> >>> On Tue, Nov 10, 2026 at 3:50 PM Uroš Bojanić via dev < >>> [email protected]> wrote: >>> >>>> +1 for 3.5.10 from my side, I still do think we should go forward with >>>> it! >>>> Unless of course there are any objections or outstanding security >>>> issues. >>>> (which seems like there's not) >>>> >>>> On 2026-10-28 22:10 UTC Szehon Ho wrote: >>>> > Hi all, >>>> > >>>> > Would folks be interested in a Spark 3.5.10 release? >>>> > >>>> > In the earlier 4.1.4 discuss thread >>>> > <https://lists.apache.org/thread/frqlfr9t6z5vs3vfzpdpsth2lmg31hvp>, >>>> Uros >>>> > and I discussed targeting 4.2.1 and 4.1.4 first, then following up on >>>> the >>>> > older branches. Now that those releases and 4.0.5 are out, would this >>>> be a >>>> > good time to revisit 3.5.10? >>>> > >>>> > Since 3.5.9 was released on July 16, branch-3.5 has accumulated 36 >>>> retained >>>> > changes, including security hardening and related fixes. >>>> > >>>> > The approved proposal to extend Spark 3.5 LTS for security fixes >>>> > < >>>> https://docs.google.com/document/d/15fb-7DNztzpQMF1MQovK75UmpC6um7KgO8cg_X5oa1I/edit >>>> > >>>> > provides >>>> > security-only support for 3.5.x through November 2027. >>>> > >>>> > As the Spark 4.3.0 RC3 vote >>>> > <https://lists.apache.org/thread/om9p5coq4z6z9rlmtthflo71ddlr2bg7> is >>>> > currently underway, and this can wait until that vote is finalized. >>>> That >>>> > would give us time to check whether any outstanding security patches >>>> also >>>> > need to be included in 3.5.10 before cutting RC1. >>>> > >>>> > Thoughts? As discussed in the thread, happy to help drive the >>>> release if >>>> > there is. >>>> > >>>> > Thanks, >>>> > Szehon >>>> > >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe e-mail: [email protected] >>>> >>>>
