[
https://issues.apache.org/jira/browse/HBASE-18828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16428659#comment-16428659
]
Sean Busbey commented on HBASE-18828:
-------------------------------------
bq. What command you running?
{{git hist origin/branch-2.0 origin/master rel/1.0.0 > some_file.txt}}
then editing some_file.txt to make the elided bits w/counts.
{{git hist}} is an alias I have local:
{code}
hist = log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s
%Cgreen(%cr)%Creset' --abbrev-commit --date=relative
{code}
{quote}
Currently I'm thinking I need to figure what is in hbase1 that is also in
hbase2 and remove 2.0.0 from JIRA for those commits. You suggesting otherwise?
{quote}
you mean like remove things that landed in any branch-1 release? or just the
stuff from the 1.0.0 related release?
> [2.0] Generate CHANGES.txt
> --------------------------
>
> Key: HBASE-18828
> URL: https://issues.apache.org/jira/browse/HBASE-18828
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Priority: Blocker
> Fix For: 2.0.0
>
> Attachments: changelog.md, hbase_branches.svg, releasenotes.md
>
>
> See [~busbey] writeup on generating CHANGES.txt here HBASE-14025 (fold it
> into refguide while at it..)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
