[ 
https://issues.apache.org/jira/browse/STORM-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15205246#comment-15205246
 ] 

ASF GitHub Bot commented on STORM-1617:
---------------------------------------

Github user d2r commented on the pull request:

    https://github.com/apache/storm/pull/1234#issuecomment-199506435
  
    Checked documentation roots and javadocs were of the correct versions on a 
server @revans2 set up to test. +1



> storm.apache.org has no release specific documentation
> ------------------------------------------------------
>
>                 Key: STORM-1617
>                 URL: https://issues.apache.org/jira/browse/STORM-1617
>             Project: Apache Storm
>          Issue Type: Bug
>          Components: asf-site
>            Reporter: Robert Joseph Evans
>            Assignee: Robert Joseph Evans
>
> Our current documentation on http://storm.apache.org/ has no place to put 
> release specific documentation.  Ever other project I know of has a little 
> bit of generic information, but most of the site is tied to a specific 
> release.  I would like to copy that model and I propose that the following 
> files be maintained only on the asf-site branch.  All other files will be 
> moved to a documentation directory on the individual branches, and a copy of 
> each, along with the generated javadocs, will be copied to a release specific 
> directory for each release.
> ./index.html
> ./releases.html (Combined downloads + documentation for each release)
> ./contribute/BYLAWS.md
> ./contribute/Contributing-to-Storm.md
> ./contribute/People.md (Perhaps just PMC for this)
> ./_posts
> ./news.html
> ./feed.xml
> ./getting-help.html
> ./LICENSE.html (Apache License)
> ./talksAndVideos.md
> Possibly also:
> ./about/deployment.md
> ./about/fault-tolerant.md
> ./about/free-and-open-source.md
> ./about/guarantees-data-processing.md
> ./about/integrates.md
> ./about/multi-language.md
> ./about/scalable.md
> ./about/simple-api.md
> ./about.md



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to