[
https://issues.apache.org/jira/browse/ARROW-3004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16693824#comment-16693824
]
Uwe L. Korn commented on ARROW-3004:
------------------------------------
I'm wondering how we plan to solve this. I would think that we would rather go
back to a specific commit and would run our docker scripts with this commit
than having scripts that checkout Arrow at a specific hash but don't use its
scripts. The documentation and its build process will always be bound to code
tree. For now I have started in https://github.com/apache/arrow/pull/2856 to
build the documentation into a {{/latest/}} folder. We probably want to be able
to parametrize this and build the documentation for releases into a different
folder.
> [Documentation] dev/gen_apidocs.sh builds docs for master rather than a
> pinned commit
> -------------------------------------------------------------------------------------
>
> Key: ARROW-3004
> URL: https://issues.apache.org/jira/browse/ARROW-3004
> Project: Apache Arrow
> Issue Type: Bug
> Components: Documentation
> Reporter: Wes McKinney
> Priority: Major
> Fix For: 0.13.0
>
>
> This is inflexible because there may be fixed to the documentation build
> scripts
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
