I don’t have a strict preference around the version number — the important thing is that we get the release out. That said, this feels quite last-minute. Most of us have been planning with 4.1 in mind.
While 5.x does open the door to removing deprecated methods/configs and gives us more freedom to make breaking changes, I think we should proceed with 4.1 as originally planned. Even if the work for 5.x seems small now, properly thinking through what all we might want to include in a major release could end up pushing timelines further. Unless we decide to do a last-minute major version bump without looking out what more can be scoped — which I don’t think would be very community-friendly — it's better to keep things simple and focused. From what I can tell, most of the folks don't have a particularly strong preference, so let’s not overcomplicate things 2 days before the code freeze. Let’s aim to release 4.1 next week as planned, and we can save the more ambitious ideas for 5.x 🙂 (Outside scope info): As far as I know, Hadoop is also planning to drop JDK 8 only in the 3.4 release [1]. -Ayush [1] https://lists.apache.org/thread/5543x33nv6196bc5xyxdqjoh2dht0kbg On Mon, 23 Jun 2025 at 16:48, Shohei Okumiya <oku...@apache.org> wrote: > > Thank you all! > > I also think Iceberg REST Catalog is not a blocker. It is nice to have, and > HIVE-29019 verified that no critical bugs, such as metadata corruptions, > exist in the current effective endpoint. Improving the release cadence sounds > more important. > > Regarding 4.1 vs 5.0, I also don't have a firm preference. If we go with 5.0, > isn't the extra work significant? We may have to change the fix versions of > all tickets, update some documents mentioning 4.1.0(such as the following > one), that's all? In that case, it sounds technically possible. > - https://hive.apache.org/docs/latest/capture-lineage-info/ > > I'm excited about the next release. Hopefully, everyone shares the thought! > > Best, > Okumin > > > On Mon, Jun 23, 2025 at 7:13 PM Butao Zhang <butaozha...@163.com> wrote: >> >> Thanks for the advice! >> I just sent out the notification email regarding the code freeze[1]. >> >> Additionally, regarding Stamatis' suggestion: "I feel that the current >> content deserves a major version bump (instead of 4.1.0 we should probably >> consider 5.0.0)." I don't have strong feelings either for or against this. >> Given the significant changes in this release, whether it would be more >> meaningful to define it as version 5.0 may require further discussion. >> Perhaps we should initiate a community email vote on whether to name it >> 4.1.0 or 5.0.0? >> >> [1]https://lists.apache.org/thread/c166fz9hr3yft75qo3lcmhrbm1howpol >> >> Thanks, >> Butao Zhang >> ---- Replied Message ---- >> FromAyush Saxena<ayush...@gmail.com> >> Date6/23/2025 17:23 >> To<dev@hive.apache.org> >> SubjectRe: [DISCUSS] Hive 4.1.x release >> >> Could we consider sending out a notification email? >> >> >> Let’s have Butao Zhang, with their Release Manager hat on, do the >> honors here. :-) >> >> Butao Zhang, could you please send out a [NOTICE] email announcing >> that the code freeze for 4.1.0 is set for the 25th? >> Post that, only critical items will be considered for the release and >> must be cherry-picked to the release branch (alongside master, where >> applicable). >> Feel free to phrase it accordingly. >> >> –Ayush >> >> On Mon, 23 Jun 2025 at 14:33, Denys Kuzmenko <dkuzme...@apache.org> wrote: >> >> >> HIVE-29038 is more like an open discussion. >> >> 25th sounds good! Could we consider sending out a notification email? >> >> Thanks!
