GitHub user alpinegizmo opened a pull request:

    https://github.com/apache/flink/pull/3242

    [FLINK-5575][docs] reworked the mechanism that warns users about …

    …newer docs so that only the most recent out-of-date release has to be 
updated when a new release is made available.
    
    Defining latest_stable_url wasn't a very scalable approach, since this 
value would have to be updated in every old release. This has been replaced 
with a redirect from flink.apache.org/q/stable-docs.html.
    
    It would make sense to merge this PR into the release-1.2 branch, though it 
isn't strictly necessary.
    
    Also, release-1.1 will need to be updated when 1.2 is released.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/alpinegizmo/flink old-doc-warning

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3242.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3242
    
----
commit dcf9b96205c604cb2665d1e9bf6ed1d5897910ad
Author: David Anderson <[email protected]>
Date:   2017-01-31T14:15:15Z

    [FLINK-5575][docs] reworked the mechanism that warns users about newer docs 
so that only the most recent out-of-date release has to be updated when a new 
release is available

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to