[
https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17374913#comment-17374913
]
Joris Van den Bossche commented on ARROW-1299:
----------------------------------------------
> A crossbow nightly task could push the nightly docs to somewhere, preferably
> to a subdir in apache/arrow-site
We already have a nightly task to build the docs, so I assume we can use that
one to push the docs it built to github pages.
When pushing to the asf-site branch of the repo, I think we will need to
re-initialize the branch (or squash) every time, as otherwise adding a commit
daily with the full doc build might quickly lead to a large repo size?
(although it's maybe not too bad, and can first see how it goes)
I would propose to push the nightly docs in a subdirectory like "/docs/dev/" or
"/docs/version/dev" (and we can later add the builds for released versions
under "docs/5.0/" or "docs/version/5.0").
> though we'd need to have a version selector somewhere on the page.
We would certainly need that eventually (especially when keeping the docs for
past released versions), and there are several other doc sites using the same
sphinx theme that have this. But I don't think we necessarily need to fix that
before tackling this issue (for the nightly dev docs, it's a single url that we
can document that can be checked).
I will open a separate JIRA for a version selector.
> [Doc] Publish nightly documentation against master somewhere
> ------------------------------------------------------------
>
> Key: ARROW-1299
> URL: https://issues.apache.org/jira/browse/ARROW-1299
> Project: Apache Arrow
> Issue Type: Task
> Components: Documentation
> Reporter: Wes McKinney
> Priority: Major
>
> This will help catch problems with the generated documentation prior to
> release time, and also allow users to read the latest prose documentation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
