[
https://issues.apache.org/jira/browse/HBASE-22853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17266517#comment-17266517
]
Viraj Jasani commented on HBASE-22853:
--------------------------------------
Wow, how I forgot about this super awesome script is beyond me. In fact, this
is so good and has everything under requirements.txt without having to let user
worry about it. What I have is very small script written in just few hr of time
for urgently looking into discrepancies for ongoing RC preparations in both
HBase and Phoenix (looping through git log output until loop reaches user
specified commit hash and use Jira API to get fields of each Jira, that's it).
I don't think it is anywhere close to this one in terms of quality.
Thanks for pointing out [~ndimiduk] and [~stack], I will mark HBASE-25514 as
duplicate later and will try playing around with this script in the meanwhile.
It seems we already have multiple improvements checked-in throughout last year,
that's nice!
FYI [~apurtell]
> 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)
