Tallying up the results above,
+1, 9 binding and 8 non-binding
no 0 or -1 votes
The vote passes.

I'll coordinate with folks to remove Spark 3.4 after the 1.11 release.

Best,
Kevin Liu



On Thu, Jan 8, 2026 at 11:28 AM Kevin Liu <[email protected]> wrote:

> Hey folks,
>
> Based on the response above, it seems like there's support to fully remove
> Spark 3.4 and mark it as "End-of-life".
>
> I've added an update on removing Spark 3.4 in the discuss thread,
> https://lists.apache.org/thread/2ppvhglts8qr5vdwm7wbdb56b9w0ddg4
> We will remove Spark 3.4 immediately after the 1.11 release.
>
> Best,
> Kevin Liu
>
>
> On Wed, Oct 15, 2025 at 9:27 AM Manu Zhang <[email protected]>
> wrote:
>
>> +1 (non-binding)
>>
>> When will 1.11 be released? If Spark 4.1 is released earlier, I don't
>> think we can keep Spark 3.4 when 4.1 is in.
>> It looks there's no issue based on my draft PR[1] for 4.1 support. Of
>> course, we can also push 4.1 support to later versions.
>>
>> 1. https://github.com/apache/iceberg/pull/14155
>>
>> Best,
>> Manu
>>
>> On Wed, Oct 15, 2025 at 3:23 PM Jean-Baptiste Onofré <[email protected]>
>> wrote:
>>
>>> +1 (non binding)
>>>
>>> I would suggest to keep 3.4 in 1.11 and remove in 1.12.
>>> A couple of releases of "deprecation" gives enough time to users (one
>>> release is maybe short).
>>>
>>> Regards
>>> JB
>>>
>>> On Tue, Oct 7, 2025 at 4:59 PM Kevin Liu <[email protected]> wrote:
>>> >
>>> > Hey folks,
>>> >
>>> > We have just marked Spark 3.4 as "Deprecated",
>>> https://iceberg.apache.org/multi-engine-support/#apache-spark
>>> > I would like to start this vote thread to remove Spark 3.4 from the
>>> repository. This means Spark 3.4 will be considered “End of Life” in the
>>> upcoming 1.11 release.
>>> >
>>> > I’ve gathered feedback from recent contributors to spark/v3.4. All
>>> (except one) have responded on the Slack thread, and support removing Spark
>>> 3.4. The last contributor has not yet responded.
>>> >
>>> > Please share your thoughts!
>>> >
>>> > Best,
>>> > Kevin Liu
>>> >
>>> >
>>>
>>

Reply via email to