[jira] [Commented] (HBASE-22853) Git/Jira Release Audit Tool

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

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

Hudson commented on HBASE-22853:
--------------------------------

Results for branch master
	[build #1611 on builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1611/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(x) {color:red}-1 general checks{color}
-- For more information [see general report|https://builds.apache.org/job/HBase%20Nightly/job/master/1611//General_Nightly_Build_Report/]




(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1611//JDK8_Nightly_Build_Report_(Hadoop2)/]


(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://builds.apache.org/job/HBase%20Nightly/job/master/1611//JDK8_Nightly_Build_Report_(Hadoop3)/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


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