> I don't think we have the necessary (human & CI) resources to maintain > multiple release lines so from my perspective when 4.2.0 goes out 4.1.0 > should go automatically EOL;
Fully agree > Regarding HIVE-29145 and HIVE-29213, I posted some thoughts under the > respective tickets and I would encourage others to do that as well. The filter below returns additional tickets with 4.1.0 listed as the affected version. We should consider reviewing those as well: https://issues.apache.org/jira/issues/?jql=project%20%3D%20HIVE%20and%20affectedVersion%20%3D%204.1.0%20and%20type%20%3D%20Bug%20and%20resolution%20%3D%20Unresolved%20order%20BY%20created%20DESC Regarding the Spark issue. Frankly, I’m not too concerned about their design choice to include Hive 2.3 jars in Spark 3.5/4.0 while aiming for HMS 4.0 compatibility. Here’s some further context: https://github.com/apache/iceberg/issues/12878 Regards, Denys
