[
https://issues.apache.org/jira/browse/ARROW-5548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16861390#comment-16861390
]
Wes McKinney commented on ARROW-5548:
-------------------------------------
I don't think it's important (or even necessarily a good idea) to publish docs
for non-released versions of the project on arrow.apache.org. From the
perspective of Apache Arrow, the software "does not exist" until it is
released. It'd be easier and more manageable for a third party to host
developer docs. Perhaps we (Ursa Labs affiliates) can create a "Developer
Resources" page linked off ursalabs.org containing links to nightly package
builds, nightly docs, and other resources that are non-PMC-sanctioned
> [Documentation] http://arrow.apache.org/docs/latest/ is not latest
> ------------------------------------------------------------------
>
> Key: ARROW-5548
> URL: https://issues.apache.org/jira/browse/ARROW-5548
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Documentation, Website
> Reporter: Neal Richardson
> Assignee: Neal Richardson
> Priority: Major
> Fix For: 0.14.0
>
>
> In testing out the Dockerfile for building the docs, I noticed it created an
> asf-site/docs/latest directory at the end. Out of curiosity, I went to
> [http://arrow.apache.org/docs/latest/], and it reports a version of
> {{0.11.1.dev473+g6ed02454}}, which is not close to "latest".
> I'd like to see this "latest" site get updated automatically. I'm working on
> getting this Docker setup complete (cf.
> https://issues.apache.org/jira/browse/ARROW-5497), and once that's working,
> it should be feasible to add a Travis-CI job to update /docs/latest on every
> commit to master to apache/arrow.
> cc [~wesmckinn]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
