+1

2025年9月10日(水) 17:44 Max Gekk <[email protected]>:

> +1
>
> On Wed, Sep 10, 2025 at 8:13 AM Shaoyun Chen <[email protected]> wrote:
>
>> +1
>>
>> SPARK-46941[1] also fixed an issue with incorrect results.
>>
>> 1. https://issues.apache.org/jira/browse/SPARK-46941
>>
>> Yang Jie <[email protected]> 于2025年9月10日周三 11:49写道:
>> >
>> > +1
>> >
>> > On 2025/09/10 02:32:29 Wenchen Fan wrote:
>> > > +1
>> > >
>> > > On Wed, Sep 10, 2025 at 4:13 AM Mich Talebzadeh <
>> [email protected]>
>> > > wrote:
>> > >
>> > > > Agreed +1
>> > > > 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 Tue, 9 Sept 2025 at 16:51, Peter Toth <[email protected]>
>> wrote:
>> > > >
>> > > >> Hi dev list,
>> > > >>
>> > > >> Apache Spark 3.5.6 was released on May 29, 2025, so it's been more
>> than 3
>> > > >> months.
>> > > >> As far as I can see, we have ~40 unreleased commits on the branch
>> and 34
>> > > >> resolved tickets:
>> > > >> https://issues.apache.org/jira/projects/SPARK/versions/12355975
>> > > >> including 3 correctness ones:
>> > > >>
>> https://issues.apache.org/jira/browse/SPARK-52873?jql=fixVersion%20%3D%203.5.7%20and%20project%20%3D%20Spark%20and%20labels%20%3D%20correctness
>> > > >>
>> > > >> I have an open ticket that I would like to fix this week and
>> include in
>> > > >> the next 3.5 release:
>> https://issues.apache.org/jira/browse/SPARK-53399
>> > > >>
>> > > >> But my question is, do you think it's time to release 3.5.7? I'm
>> happy to
>> > > >> volunteer to take the role of release manager if it is.
>> > > >>
>> > > >> Best,
>> > > >> Peter
>> > > >>
>> > > >>
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe e-mail: [email protected]
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe e-mail: [email protected]
>>
>>

Reply via email to