[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075316#comment-17075316 ] Neal Richardson commented on ARROW-1299: IMO having some automated nightly docs without CUDA is better than not having them at all because we insist on building with CUDA. > [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)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075311#comment-17075311 ] Wes McKinney commented on ARROW-1299: - The docs need CUDA so not sure that GHA cron will work unless self-hosted. > [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)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17075223#comment-17075223 ] Krisztian Szucs commented on ARROW-1299: My idea is to update arrow-site to host the documentation for the last three releases and one for master which could be updated regularly by a github actions cron job. > [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)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16932363#comment-16932363 ] Antoine Pitrou commented on ARROW-1299: --- cc [~npr] > [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 >Assignee: Neal Richardson >Priority: Major > Fix For: 1.0.0 > > > 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)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747317#comment-16747317 ] Wes McKinney commented on ARROW-1299: - We could set up Netlify static hosting on a different domain/subdomain and push the nightly build from one of our CUDA-enabled servers. This is for development anyway, so there's not much benefit to having the nightly docs hosted on ASF infrastructure? > [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 (v7.6.3#76005)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16747226#comment-16747226 ] Uwe L. Korn commented on ARROW-1299: [~wesmckinn] Any ideas on which infrastructure we could do this? Should we concat INFRA for this or do we have other means? > [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 (v7.6.3#76005)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738739#comment-16738739 ] Wes McKinney commented on ARROW-1299: - Since the documentation is kind of large (10s of megabytes), we might consider hosting on a different domain under a simple HTTP server. Otherwise the site of arrow-site will grow really massive over time > [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 (v7.6.3#76005)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738255#comment-16738255 ] Uwe L. Korn commented on ARROW-1299: At the moment I'm uploading them manually to http://arrow.apache.org/docs/latest/ We could also auto-upload it there but that requires someone to place his ASF credentials for uploading where the cron-job runs. > [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 (v7.6.3#76005)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738217#comment-16738217 ] Antoine Pitrou commented on ARROW-1299: --- I don't know. It could be github-pages, but the setup is a bit unorthodox (we would probably have to create a separate repo for doc builds and push to it automatically). I don't think ReadTheDocs allows pushing already built docs. There's a simplistic [Sphinx extension|https://www.sphinx-doc.org/en/master/usage/extensions/githubpages.html] too :) > [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 (v7.6.3#76005)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738209#comment-16738209 ] Krisztian Szucs commented on ARROW-1299: Where do We want to host it? > [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 (v7.6.3#76005)
[jira] [Commented] (ARROW-1299) [Doc] Publish nightly documentation against master somewhere
[ https://issues.apache.org/jira/browse/ARROW-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738167#comment-16738167 ] Antoine Pitrou commented on ARROW-1299: --- cc [~kszucs] > [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 (v7.6.3#76005)
