[
https://issues.apache.org/jira/browse/HBASE-22986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16945000#comment-16945000
]
Toshihiro Suzuki commented on HBASE-22986:
------------------------------------------
I thought we could have the ref guide in the next release, but I'm not very
familiar with the ref guide release flow actually. What I knew is that ref
guide modifications should be committed only to the master branch, but you mean
this is not correct, right? Do we need to have different docs for both versions
HBase 1.y and HBase 2.y?
We have hbtop for both versions HBase 1.y and HBase 2.y and for now, the
features are almost the same, so having the same documentation for both
versions is fine. But in the future, we might have features that HBase 2.y has
but HBase 1.y doesn't have. So that means we need to have different docs for
both versions? And in this case, do we need to put the images in both the
master branch and branch-1 in the main repo, right?
> Add documentation for hbtop
> ---------------------------
>
> Key: HBASE-22986
> URL: https://issues.apache.org/jira/browse/HBASE-22986
> Project: HBase
> Issue Type: Sub-task
> Components: documentation, hbtop
> Reporter: Toshihiro Suzuki
> Assignee: Toshihiro Suzuki
> Priority: Minor
>
> We already have README for hbtop, so we can make the refguide refer to this:
> [https://github.com/apache/hbase/blob/master/hbase-hbtop/README.md]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
