You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/02/03 16:47:51 UTC

[jira] [Commented] (FLINK-5575) in old releases, warn users and guide them to the latest stable docs

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

ASF GitHub Bot commented on FLINK-5575:
---------------------------------------

Github user uce commented on the issue:

    https://github.com/apache/flink/pull/3242
  
    Good addition. Could you post a screenshot of how this looks now?
    
    Given that we are very unlikely to provide any fixes for older versions than 1.0.0, I would vote to simply redirect to the latest stable version instead of still hosting the docs for those versions; especially because the docs before 1.0.0 are in very bad shape. If any user is interested in those docs, it's possible to check out the source code and manually build them. What do you think?
    
    @rmetzger Would it be possible to have a redirect via the `ci` infra?


> in old releases, warn users and guide them to the latest stable docs
> --------------------------------------------------------------------
>
>                 Key: FLINK-5575
>                 URL: https://issues.apache.org/jira/browse/FLINK-5575
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: David Anderson
>            Assignee: David Anderson
>
> Old versions of Flink (especially version 0.8) are being frequently studied, downloaded, and used by new users (because google leads them there). I propose to guide folks to the latest stable release by adding a link on every documentation page in the old docs that links to the home page of the latest stable docs. 
> The redirect lives at flink.apache.org/q/stable-docs.html, and will need to be modified with each major release (e.g. when 1.2 is released).
> This problem affects all releases before 1.1, but the stats show that 0.8, 0.9, 0.10, and 1.0 are the most important to deal with.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)