You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hudi.apache.org by "Ethan Guo (Jira)" <ji...@apache.org> on 2019/11/01 00:27:00 UTC

[jira] [Commented] (HUDI-320) Keep docs on master instead of asf-site branch

    [ https://issues.apache.org/jira/browse/HUDI-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964472#comment-16964472 ] 

Ethan Guo commented on HUDI-320:
--------------------------------

It happened to me that my colleague followed the latest docs to use the renamed package name for running incremental pulls in production, where the release we're using is pre-0.5.0.  Then I realized that there's a gap here. 

 

[~vinoth] [~vbalaji]  Do you think we should do this going forward?

> Keep docs on master instead of asf-site branch
> ----------------------------------------------
>
>                 Key: HUDI-320
>                 URL: https://issues.apache.org/jira/browse/HUDI-320
>             Project: Apache Hudi (incubating)
>          Issue Type: Improvement
>          Components: Docs
>            Reporter: Ethan Guo
>            Priority: Minor
>
> Given that each version has new features and improvements, some involving configuration and parameter changes, compared to previous versions, it would be good to keep the docs for each version.  This can be achieved by having the docs on master, so each release has its version of docs.  Developers can always refer to the docs of a specific release if they would like to.
>  
> Currently we only have one version of docs kept at the asf-site branch for the latest release.  This can create confusion for users using a previous release of Hudi.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)