[ https://issues.apache.org/jira/browse/HBASE-22853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17268032#comment-17268032 ]
Nick Dimiduk commented on HBASE-22853: -------------------------------------- [~vjasani] also, you need {{--populate-from-git=true}} if you want the tool to read the git repo at all. With it's {{false}}, the tool skips git. Likewise, with {{--populate-from-jira=false}} the tool will skip populating the database from jira. > Git/Jira Release Audit Tool > --------------------------- > > Key: HBASE-22853 > URL: https://issues.apache.org/jira/browse/HBASE-22853 > Project: HBase > Issue Type: Task > Components: build > Reporter: Michael Stack > Assignee: Nick Dimiduk > Priority: Minor > Fix For: 3.0.0-alpha-1 > > > Before cutting RC, need to make reconciliation between what's in JIRA and > then what has been actually committed to ensure JIRA is accurate before > starting the RC build (in order to ensure CHANGES/RELEASENOTES are accurate, > etc.). > Would be good to have a tool that compared git log for the release to > fixVersion in JIRA (and then fixVersion in JIRA to what is in git) to ensure > matching mentions in both places. It can get complicated when there has been > reverts in git or when an issue is an umbrella issue w/ no direct patch > associated in JIRA but tool could start out simple dumping out a list of > hashes/JIRAs for the RM to 'check' where anomalies; i.e. mention in one > system but not in the other. This would save on a bunch of work aligning the > two systems. Could also do stuff like check git log to ensure all commits > have associated JIRA, and so on. > (Should there be a PR component?). -- This message was sent by Atlassian Jira (v8.3.4#803005)