[jira] [Comment Edited] (HBASE-25514) Utility to identify git commit / Jira fixVersion discrepancies for RC preparation

["Viraj Jasani (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-25514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266007#comment-17266007 ] 

Viraj Jasani edited comment on HBASE-25514 at 1/15/21, 2:38 PM:
----------------------------------------------------------------

I have one working script as part of PHOENIX-6314 and PHOENIX-6316 (which I used for 2.4.1 and 2.3.4 RCs). Output of such script will have to be manually verified by RM before rolling RC. If someone has better idea, please let me know.


was (Author: vjasani):
I have one working script as part of PHOENIX-6314 and PHOENIX-6316. Output of such script will have to be manually verified by RM before rolling RC. If someone has better idea, please let me know.

> 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
>
> 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)