Apart from latest Jiras mentioned by Istvan for fixVersion discrepancies, when I used this script [1], I could see more such discrepancies, meaning CHANGES.md is out of sync from git commits landed on branch 4.16.
As of now, I can see: 37 Jiras missing fixVersion 4.16 4 git commits without Jira number 2 Jiras not resolved yet but corresponding commits are present 6 reverted commits (need to verify Jira status) 4 Jiras marked resolved but have no relevant commits present (false positive case for svn checkins though) Xinyi, let me spend some time today to fix some of these discrepancies. If the completion status is unknown for some Jira, i will ping you on it. This might not be strong point to sink the RC, but if we have some way to re-generate and update CHANGES.md after fixing Jira status, we should consider it (if not sink the RC) but it might be bit of a manual task I believe. 1. https://github.com/apache/phoenix/tree/master/dev/misc_utils On 2021/01/28 05:09:44, Xinyi Yan <yanxi...@apache.org> wrote: > Hello Everyone, > > This is a call for a vote on Apache Phoenix 4.16.0 RC0. This is the next > minor release of Phoenix 4, compatible with Apache HBase 1.3, 1.4, 1.5 > and 1.6. > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache phoenix 4.16.0 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 4.16.0RC0 > https://github.com/apache/phoenix/tree/4.16.0RC0 > > The release files, including signatures, digests, as well as CHANGES.md > and RELEASENOTES.md included in this RC can be found at: > https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC0/ > > For a complete list of changes, see: > https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC0/CHANGES.md > > Artifacts are signed with my "CODE SIGNING KEY": > E4882DD3AB711587 > > KEYS file available here: > https://dist.apache.org/repos/dist/dev/phoenix/KEYS > > > Thanks, > Xinyi >
