Given that we still rely on internals of Spark in some places, I think we will have to continue to have a module per Spark version. LTS + rolling window of 2 minors seems reasonable to me too.
+1 on getting 4.2 support in to unlock development and dropping 4.0 after that. - Anton пн, 15 черв. 2026 р. о 07:30 Anurag Mantripragada < [email protected]> пише: > And I think whether to dropping Spark 4.0 support does not block adding >> Spark 4.2 support (with current RC state) > > > +1, we can review and merge Spark 4.2 support first. I will start a vote > to remove Spark 4.0 after the community sync tomorrow. > > Thanks, > Anurag > > On Mon, Jun 15, 2026 at 1:08 AM Cheng Pan <[email protected]> wrote: > >> Keep support for Spark last LTS + 2 latest minors sounds reasonable, if >> Iceberg could have a roughly 3 months release periods, which is similar to >> Spark and Flink, otherwise, it requires a wider version range to avoid >> version jumping when upgrading Iceberg. >> >> And I think whether to dropping Spark 4.0 support does not block adding >> Spark 4.2 support (with current RC state), I see at least two committer >> expressed the willingness on merging the spark 4.2 connector code as-is to >> unblock subsequent developing, and no objections, so, merge Spark 4.2 >> support first? And then start a vote thread for deleting Spark 4.0 support, >> if necessary? >> >> Thanks, >> Cheng Pan >> >>
