[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-310) redirect /latest to /reference where the latest released docs can be found

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/TOOLSDOC-310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770187#comment-12770187 ] 

Nick Boldt commented on TOOLSDOC-310:
-------------------------------------

Seems Fred trusts me more than Max does. :)

As to the "root of jbosstools-documentation" == "root of docs.jboss.org/tools/" I think it's always been that way. There is no rsync script, it's just pushed by hand by myself or [~mmurray] (or in the past, Isaac opened an eng-ops ticket w/ an attached zip).
                
> redirect /latest to /reference where the latest released docs can be found
> --------------------------------------------------------------------------
>
>                 Key: TOOLSDOC-310
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-310
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>            Reporter: Max Rydahl Andersen
>            Assignee: Max Rydahl Andersen
>
> for some reason https://github.com/jbosstools/jbosstools-documentation/pull/48 removed the latest link assuming latest is used to point to the nightly build.
> That is not what it is for.
> It is to point to the latest docs made available.
> This link (before: http://docs.jboss.org/tools/latest/) was used to point to the last latest documentation.
> I believe this should be put back since this is how other docs refer to the latest version.
> We could even go so ar to create a docs.jboss.org/tools/4.0, docs.jboss.org/tools/3.3 etc. folder each with their /latest link in them.
> Latest links are trivial to make with sftp as part of the release upload anyway thus should be all possible to script if it is too cumbersome to remember.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira