Re: [VOTE] Mark Hive 3.x as EOL

2024-10-01 Thread Denys Kuzmenko
+1 (Binding)

Re: [VOTE] Mark Hive 3.x as EOL

2024-10-01 Thread Simhadri G
+1 for EoL of Hive 3 (non-binding) Thanks, Simhadri G On Tue, Oct 1, 2024 at 9:41 PM Ayush Saxena wrote: > Hi All, > Following several discussions, this is the formal thread to mark the > Hive 3.x release line as End of Life (EOL). > > Marking a release line as EOL means there will be no furth

[RESULT][VOTE] Apache Hive 4.0.1 Release Candidate 0

2024-10-01 Thread Zhihua Deng
Hi Everyone, The voting for Hive 4.0.1 has ended, and we have received a total of 8 votes, with 4 binding and 4 non-binding. Binding: Denys Kuzmenko Ayush Saxena Krisztian Kasa Stamatis Zampetakis Non-binding: Simhadri G Butao Zhang Shohei Okumiya (Okumin) Dmitriy Fingerman (difin)

Re: [EXTERNAL] Re: [DISCUSS] Hive 3.x release

2024-10-01 Thread Ayush Saxena
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

[VOTE] Mark Hive 3.x as EOL

2024-10-01 Thread Ayush Saxena
Hi All, Following several discussions, this is the formal thread to mark the Hive 3.x release line as End of Life (EOL). Marking a release line as EOL means there will be no further releases for this version. However, it does not affect any existing users who can continue using it as they have bee

Re: [VOTE] Apache Hive 4.0.1 Release Candidate 0

2024-10-01 Thread Stamatis Zampetakis
Since there is no legal issue with the .iml files I am changing by vote to +1 (binding). Best, Stamatis On Tue, Oct 1, 2024 at 10:41 AM Denys Kuzmenko wrote: > > Since the licensing concerns were addressed I would propose to return to the > original thread. I don't think it's worth the effort t

Re: [VOTE] Apache Hive 4.0.1 Release Candidate 0

2024-10-01 Thread Stamatis Zampetakis
The -1 on releases is not a veto [1]. It's up to the release manager to take the final decision to proceed with release or not. The thread has already 3 +1 (binding) votes so my -1 has an advisory tone. The files that are present in the release sources are not contributed explicitly to the project

Re: [VOTE] Apache Hive 4.0.1 Release Candidate 0

2024-10-01 Thread Ayush Saxena
Hi Stamatis, I have an answer here [1], I was checking some archives with similar issues, [2] has similar stuff & so does a couple of more. -Ayush [1] https://issues.apache.org/jira/browse/LEGAL-683?focusedCommentId=17886047&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#c

Re: [VOTE] Apache Hive 4.0.1 Release Candidate 0

2024-10-01 Thread Zhihua Deng
Hi everyone, As we have confirmed that the "impl" file in release sources couldn't be the licensing concerns, I've reverted the release sources back to its first version, so the (non-)binding votes are still valid. Again thanks to everyone for the verification and tests! Best Regards, Zhihu

Re: [VOTE] Apache Hive 4.0.1 Release Candidate 0

2024-10-01 Thread Denys Kuzmenko
Since the licensing concerns were addressed I would propose to return to the original thread. I don't think it's worth the effort to create and validate a new RC. WDYT?

Re: [VOTE] Apache Hive 4.0.1 Release Candidate 0

2024-10-01 Thread Denys Kuzmenko
My take on this is that we do not need a new RC since the code hasn't changed, `impl` files were removed just from packaged sources. Maybe we could start a new vote, but there is no need for a new RC. We don't need to repeat tests on binaries, just build from sources and do the checks. And by