[ https://issues.apache.org/jira/browse/HBASE-25514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266293#comment-17266293 ]
Viraj Jasani commented on HBASE-25514: -------------------------------------- FYI [~apurtell] > Utility to identify git commit / Jira fixVersion discrepancies for RC > preparation > --------------------------------------------------------------------------------- > > Key: HBASE-25514 > URL: https://issues.apache.org/jira/browse/HBASE-25514 > Project: HBase > Issue Type: Task > Reporter: Viraj Jasani > Assignee: Viraj Jasani > Priority: Major > Fix For: 3.0.0-alpha-1 > > > As part of RC preparation, we need to identify all git commits that landed > on release branch, however their corresponding Jira is either not resolved > yet or does not contain expected fixVersions. Only when we have git commits > and corresponding Jiras with expected fixVersion resolved, we get all such > Jiras included in auto-generated CHANGES.md as per Yetus changelog generator. > Proposal of this Jira is to provide such script that can be useful for all > upcoming RC preparations and list down all Jiras where we need manual > intervention. This utility script should use Jira API to retrieve individual > fields and use git log to loop through commit history. > The script should identify these issues: > # commit is reverted as per commit message > # commit does not contain Jira number format HBASE-XXXX in message > # Jira does not have expected fixVersion > # Jira has expected fixVersion, but it is not yet resolved > It can take inputs as: > # First commit hash to start excluding commits from history > # Fix Version > # JIRA Project Name > # Path of project's working dir > # Jira server url > The script should also identify all Jiras that are marked resolved with given > fixVersion but have no commit present with Jira number included. > RC preparation also needs to find this diff because we don't want to provide > extra Jira in CHANGELOG without any corresponding commits present on git > (unless it is svn checkin and fixVersion is relevant). -- This message was sent by Atlassian Jira (v8.3.4#803005)