GitHub user uce opened a pull request:
https://github.com/apache/flink/pull/4553
[FLINK-7642] [docs] Add very obvious warning about outdated docs
## What is the purpose of the change
This pull requests make the warning about outdated docs more obvious.
Please compare the screenshot to our current state:
https://ci.apache.org/projects/flink/flink-docs-release-1.1/
If you like this, I would back/forward port this to all versions >= 1.0 and
update the releasing Wiki page to add a note about updating the configuration
of the docs.
## Brief change log
- Change the color of the outdated warning footer to red
- Rename the config key from `is_latest` to `show_outdated_warning`
- Add an outdated warning to every page before the actual content
## Verifying this change
- We don't have any tests for the docs
- You can manually check out my branch and build the docs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/uce/flink 7462-outdated_docs_warning
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/4553.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 #4553
----
commit e140634687a56fb5fdd0e32a1dce3d5ac41fd123
Author: Ufuk Celebi <[email protected]>
Date: 2017-08-16T16:21:49Z
[FLINK-7462] [docs] Make outdated docs footer background light red
commit 15fe71e0402d2e2d931485497338973e12cce9db
Author: Ufuk Celebi <[email protected]>
Date: 2017-08-16T16:34:51Z
[FLINK-7462] [docs] Rename is_latest flag to show_outdated_warning
commit 9bdeeae0cb88b59f0dfaee547fbf9b54d125645e
Author: Ufuk Celebi <[email protected]>
Date: 2017-08-16T16:35:03Z
[FLINK-7462] [docs] Add outdated warning to content
----
---
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.
---
