Thanks for volunteering Butao! As usual I have a slightly different perspective regarding the scope for the release. If there are no regressions or other serious blockers in the current master we could cut the release ASAP. We don't need to delay the release for getting new features in. Once JDK-17 (or any other kind of major feature) is ready we can merge it to master and cut a new release (that being 4.2, 4.3, 5.0 or whatever makes sense at that point). Nobody will complain if we get a shiny new release out really soon :)
Best, Stamatis On Thu, Dec 12, 2024 at 1:00 PM Akshat m <akshatats...@gmail.com> wrote: > > Hi Team, > > Thanks for the productive discussion! > I’d like to provide a quick update on JDK-17. The initial review comments > have been addressed, and to stay aligned with ongoing upstream changes, we’ve > rebased the PR onto the latest master. After the recent rebase, we did > encounter multiple test failures, but that issue has now been resolved and > the CI tests are running again. > > While we await a green build, we’d really appreciate it if the community > could begin the secondary review process. Your insights are invaluable, and > we start to address any new feedback as soon as possible. > > Regards > Akshat > > On Thu, Dec 12, 2024 at 11:56 AM Butao Zhang <zhangbu...@apache.org> wrote: >> >> Thanks! >> IMO, JDK-17(HIVE-26473) should definitely be included in this release. I am >> also watching it. Maybe we can cut the branch-4.1 at some point after the >> JDK-17 is finished. >> >> >> Thanks, >> Butao Zhang >> >> On 2024/12/11 14:22:55 Denys Kuzmenko wrote: >> > Thanks Butao! >> > We'll support you all the way. >> > >> > ATM we should probably finalize the scope for the release (create new >> > label hive-4.1.0-must) and focus of getting those items prioritised. >> > >> > There is also ongoing discussion on JDK-8 and JDK-17. Would be great if we >> > manage to add support for JDK-17 in that release. >> >
