[
https://issues.apache.org/jira/browse/HUDI-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965070#comment-16965070
]
Ethan Guo edited comment on HUDI-320 at 11/1/19 8:18 PM:
---------------------------------------------------------
I can take this up. Found the other ticket for versioning the docs:
https://issues.apache.org/jira/browse/HUDI-226
Agree that may not be necessary to merge asf-site into master. Let me think
about the right way to do this (also automate it if possible).
Should I close this ticket and track the progress on the other one?
was (Author: guoyihua):
I can take this up. Found the other ticket for versioning the docs:
https://issues.apache.org/jira/browse/HUDI-226
Agree that may not be necessary to merge asf-site into master. Let me think
about the right way to do this (also automate it if possible).
Should I close this ticket and track the progress on the other one?
> 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)
