Should we release version 4.1.1? If we decide to proceed with 4.1.1, we may need to identify valuable patches from recent commits for the 4.1 branch, such as fixes for correctness issues, performance optimizations, and security problems.
If we skip 4.1.1 and instead release 4.2.0, would this imply that we've reached a default agreement to only publish major version releases based on the master branch going forward? Additionally, I have two tickets that may need to be addressed in the next new version: one is HIVE-29145 (Iceberg Rest server cannot work if launched by non-standalone HMS), and the other is HIVE-29213 (HS2 reports 'Failed to get primary keys' when using old beeline client). Thanks, Butao Zhang On 2025/10/22 08:48:19 Denys Kuzmenko wrote: > Hi Stamatis, > > Thanks for bringing this up. > > We already have enough items ready to ship, including JDK 21. > I'm not sure what’s causing the delay. I thought we already had a release > manager, but looks like we don’t. > > Regards, > Denys >
