While I agree with the overall sentiment and reasoning that we can all focus on Hive 4.x I would like to register my protest about this decision. There are 411 commits in branch-3 which are not in branch-3.1 most of those are bug fixes on 3.1.3. The work/effort to backport these is already been done and this is not a new effort that we are asking from the community. If all that is needed is to cut a branch, validate it and make a release out of it, I feel that that effort is small enough to be taken up and then officially mark Hive 3.x as EOL.
On Tue, Oct 1, 2024 at 9:32 PM Ayush Saxena <ayush...@gmail.com> wrote: > Marking the 3.x release line EOL has no impact on existing users; they > are free to continue using it as they have for the past two years. > This decision is primarily about development focus—we’re officially > acknowledging that we won’t be dedicating efforts to 3.x anymore, > which has already been the case for some time. > > The processes are designed to support the project's long-term health, > and without formally closing this chapter, we risk negatively > affecting the project's future. Every good thing comes to an end, and > it's better to conclude this phase on a positive note rather than > letting it become a burden. > > Let’s push forward together and focus on Hive 4.x! I will start a vote > thread for marking the end of 3.x soon. > > > -Ayush > > On Mon, 30 Sept 2024 at 13:29, Denys Kuzmenko <dkuzme...@apache.org> > wrote: > > > > Hive 3.1 is certainly the most widely adopted release line, however, we > do not see any activity on this line, even in terms of providing security > fixes and CVE backports. Hive 3.1.3, the most recent release of the 3.x, > was released on 2022-06-17. > > > > We don't want to scatter our resources so we focus on Hive 4.0 and would > like to encourage everyone to start using Hive 4.0 where we resolved > numerous critical bug and security fixes, introduced number of improvements > and new features. >
