Thanks for starting the discussion Ayush. Having frequent releases is definitely needed so we should keep the momentum going.
I had the impression from other threads that the next Hive release would be 4.1.0 and that it would be cut from master. I would like to understand how 4.0.1 is different and if it is, what is the contribution pattern that contributors and committers should follow? If the idea is to maintain and commit in two (or more) branches the steps should be documented and CI should be running on those branches. Best, Stamatis On Wed, Apr 10, 2024 at 1:18 PM Denys Kuzmenko <dkuzme...@apache.org> wrote: > > We might need it sooner as identified some critical issues in the recent code: > 1. HIVE-28166: Truncate on Iceberg table disregards the branch name and > operates on a main; > 2. HIVE-28190: Materialized view rebuild lock heart-beating is broken;
