[
https://issues.apache.org/jira/browse/HBASE-23120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16951373#comment-16951373
]
Sakthi edited comment on HBASE-23120 at 10/14/19 9:35 PM:
----------------------------------------------------------
Add the procedure for - "comparing changes logged in git and those accounted
for in jira" along the lines of [~busbey+li...@cloudera.com] 's comments
[here|https://issues.apache.org/jira/browse/HBASE-23012?focusedCommentId=16939838&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16939838]
was (Author: jatsakthi):
Add the procedure for - "comparing changes logged in git and those accounted
for in jira"
> Fix ref guide - Release process
> -------------------------------
>
> Key: HBASE-23120
> URL: https://issues.apache.org/jira/browse/HBASE-23120
> Project: HBase
> Issue Type: Sub-task
> Reporter: Sakthi
> Assignee: Sakthi
> Priority: Minor
> Fix For: 3.0.0, 2.3.0, 2.1.8, 1.5.1, 2.2.3
>
>
> The example is of a sample ~/.m2/settings.xml file.
> {code:java}
> <!- To publish a snapshot of some part of Maven -->
> {code}
> is not a proper comment.
> Also I think here,
> {code:java}
> <!--Keyname is something like this ... 00A5F21E... do gpg --list-keys to find
> it-->
> {code}
> the double hyphened --list-keys shouldn't be used. It leads to FATAL error
> like the one below:
> {code:java}
> [FATAL] Non-parseable settings
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
