It's certainly not an ideal situation, but I don't believe it's a blocker for the release. The release notes should ideally be comprehensive and list all relevant tickets, but missing a few entries shouldn't, in my opinion, justify a -1 on the RC. That feels excessive.
>From my experience, spinning up a new RC is typically warranted when there's something broken in the code or if there are legal compliance issues. For smaller matters, it's generally up to the Release Manager to decide — especially if there are multiple minor issues to consider. That's my view, of course — we operate as a community, and others may have a different take. But this alone wouldn't stop me from voting +1 if everything else looks good. –Ayush On Mon, 14 Jul 2025 at 19:04, Butao Zhang <zhangbu...@apache.org> wrote: > Hi, Hive dev > > Okumin just discovered several tickets such as [1] that were not updated > in status but had their PRs merged. These tickets were not included in the > release notes. I'd like to ask whether this situation will affect the vote > for Hive 4.1.0 Release Candidate 0? > > [1] https://issues.apache.org/jira/browse/HIVE-26047 > [2] https://github.com/apache/hive/blob/branch-4.1/RELEASE_NOTES.txt > > Thanks, > Butao Zhang >
