Master moves to 4.2.0-SNAPSHOT, no changes as such. If we decide to name the next release 5.0.0, the Release Manager for that version can handle the versioning changes accordingly.
-Ayush On Tue, 24 Jun 2025 at 13:36, Butao Zhang <butaozha...@163.com> wrote: > I would like to reconfirm a question. If the 4.1.0 branch is released, > should the version number of the master branch be changed to 5.0.0-SNAPSHOT > or 4.2.0-SNAPSHOT? > It seems that everyone believes that the name of the next major version > should be 5.0.0-SNAPSHOT. > > Thanks, > Butao Zhang > ---- Replied Message ---- > From Attila Turoczy<aturo...@cloudera.com.INVALID> > <aturo...@cloudera.com.INVALID> > Date 6/23/2025 19:47 > To <dev@hive.apache.org> <dev@hive.apache.org> > Subject Re: [DISCUSS] Hive 4.1.x release > In my view, Hive 5 (high five! 🙂) should represent a major milestone. > Ideally, it would include more impactful changes such as: > > - Making Iceberg the default table format (pending community > consensus), > - Removing legacy configurations and integrations > - Integrating new compaction strategies, among other forward-looking > improvements. > > Given the current scope and feature set, the existing package feels more > aligned with a 4.1 release rather than a true version 5. > > -Attila > > > On Mon, Jun 23, 2025 at 1:36 PM lisoda <lis...@yeah.net> wrote: > >> What if we integrate JDK 21 and then release version 5.x? >> >> >> ---- Replied Message ---- >> From Ayush Saxena<ayush...@gmail.com> <ayush...@gmail.com> >> Date 06/23/2025 19:31 >> To dev@hive.apache.org >> Cc >> Subject Re: [DISCUSS] Hive 4.1.x release >> 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! >> >
