[
https://issues.apache.org/jira/browse/HBASE-23012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16939838#comment-16939838
]
Sean Busbey commented on HBASE-23012:
-------------------------------------
Here's how I work through comparing changes logged in git and those accounted
for in jira as of the 1.4.11 RCs. The goal is for jira to be the source of
truth so that we can use it to generate release notes. HBASE-14025 has steps
for doing the comparison for a new minor release. This is specific to a
maintenance release.
1. Make a text file with the list of jiras in the fix version
- Browse to project home -> versions -> 1.4.11 -> Release Notes -> Configure
Release Notes -> format: text -> Create (leads to these [text release notes for
1.4.11|https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345617&styleName=Text&projectId=12310753&Create=Create]
- the text box at the bottom will have the contents to copy
- filter to just have jira keys (this example is OS X specific)
{code}
pbpaste | grep -o -E "\[HBASE-[0-9]*\]" | grep -o -E "HBASE-[0-9]*" | sort -u >
~/tmp/hbase-release-process/CHANGES_1.4.11_jira.txt
{code}
2. Make a test file with the list of jiras in git commit messages
{code}
$ git checkout branch-1.4
$ git log --oneline rel/1.4.10...HEAD | grep -o -E '^[^ ]* HBASE-[0-9]* ' |
grep -o -E 'HBASE-[0-9]*' | sort -u >
~/tmp/hbase-release-process/CHANGES_1.4.11_git.txt
{code}
3. use the two files to list those things in jira but not git
{code}
$ comm -1 -3 ~/tmp/hbase-release-process/CHANGES_1.4.11_git.txt
~/tmp/hbase-release-process/CHANGES_1.4.11_jira.txt
{code}
4. use the two files to list those things in git but not in jira
{code}
$ comm -2 -3 ~/tmp/hbase-release-process/CHANGES_1.4.11_git.txt
~/tmp/hbase-release-process/CHANGES_1.4.11_jira.txt
{code}
> Release 1.3.6
> -------------
>
> Key: HBASE-23012
> URL: https://issues.apache.org/jira/browse/HBASE-23012
> Project: HBase
> Issue Type: Task
> Components: community
> Reporter: Sakthi
> Assignee: Sakthi
> Priority: Major
> Fix For: 1.3.6
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
