hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13140) Version documentation to match software
Date Thu, 30 Jul 2015 19:43:05 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648183#comment-14648183

Sean Busbey commented on HBASE-13140:

What do folks think about just publishing the most recent patch release in a given minor line,
i.e. 1.1.1 for the 1.1 line? The public API shouldn't have changed. The devapidocs may have,
but for the most part folks who need the earlier version should know how to get it (e.g. maven
javadoc jars, the release, etc)

What about for 0.98 where more can change in each 0.98.y release?

> Version documentation to match software
> ---------------------------------------
>                 Key: HBASE-13140
>                 URL: https://issues.apache.org/jira/browse/HBASE-13140
>             Project: HBase
>          Issue Type: Improvement
>          Components: documentation, site
>            Reporter: stack
> Its probably about time that we add in a 0.98 and 1.0 version of documentation.  Currently,
the doc shows as 2.0.0-SNAPSHOT which is a little disorientating. A user on mailing list just
had trouble because doc talked of configs that are in hbase 1.0 but he was on 0.98.
> We have a manually made 0.94 version. It is time to do the work to make it so we can
gen doc by version for the site and it is also similarly time to let doc versions diverge.
> (I think we've only talked of doing this in past but have not as yet filed issue... close
if I have this wrong)

This message was sent by Atlassian JIRA

View raw message