You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2015/07/04 23:32:04 UTC
[jira] [Comment Edited] (HBASE-14025) Update CHANGES.txt for 1.2
[ https://issues.apache.org/jira/browse/HBASE-14025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614061#comment-14614061 ]
Sean Busbey edited comment on HBASE-14025 at 7/4/15 9:31 PM:
-------------------------------------------------------------
this pipeline does a better job of avoiding false positives for jiras that show up in git log messages:{code}
$ git log --oneline 8166142...branch-1.2 | grep -o -E '^[a-z0-9]{7} HBASE-[0-9]* ' | grep -o -E 'HBASE-[0-9]*' | sort -u > in_1.2.0.txt
{code}
was (Author: busbey):
this pipeline does a better job of avoiding false positives for jiras that show up in git log messages:{code}
$ git log --oneline 8166142...branch-1.2 | grep -o -E '[a-z0-9]{7} HBASE-[0-9]* ' | grep -o -E 'HBASE-[0-9]*' | sort -u > in_1.2.0.txt
{code}
> Update CHANGES.txt for 1.2
> --------------------------
>
> Key: HBASE-14025
> URL: https://issues.apache.org/jira/browse/HBASE-14025
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Affects Versions: 1.2.0
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Fix For: 1.2.0
>
>
> Since it's more effort than I expected, making a ticket to track actually updating CHANGES.txt so that new RMs have an idea what to expect.
> Maybe will make doc changes if there's enough here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)