Andrew Wong commented on KUDU-1266:

It'd also be useful to have a /dev version in addition to the release versions, 
or at least publish to the SNAPSHOT site prior to releases with a warning 
indicating its status. Today, it's kind of painful writing docs and having to 
wait 2-3 months for them to see the light of day. Automating site publication 
would make this sort of thing more feasible.

> Figure out per-version docs publishing
> --------------------------------------
>                 Key: KUDU-1266
>                 URL: https://issues.apache.org/jira/browse/KUDU-1266
>             Project: Kudu
>          Issue Type: Task
>          Components: documentation
>            Reporter: Jean-Daniel Cryans
>            Assignee: Mike Percy
>            Priority: Minor
> Right now we just push the documentation in master to the website, but 
> ideally we'd want to have documentation available for each version. What's 
> the best way to do this?

This message was sent by Atlassian JIRA

Reply via email to