[
https://issues.apache.org/jira/browse/FLINK-17551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17101511#comment-17101511
]
Xintong Song commented on FLINK-17551:
--------------------------------------
[~chesnay], thanks for the explanation.
I see your point. Indeed, maintaining documentation per each released version
is not trivial. The cherry-picks can be troublesome given that documentation
fixes are not always independent from production code changes.
I don't have any good idea to solve this, either. So I'll just close this
ticket.
> Documentation of stable releases are actually built on top of snapshot code
> bases.
> ----------------------------------------------------------------------------------
>
> Key: FLINK-17551
> URL: https://issues.apache.org/jira/browse/FLINK-17551
> Project: Flink
> Issue Type: Bug
> Components: Project Website
> Affects Versions: 1.10.0
> Reporter: Xintong Song
> Priority: Major
>
> When browsing Flink's documentation on the project website, we can choose
> from both the latest snapshot version and the stable release versions.
> However, it seems the documentation of stable release version is actually
> built on top of the snapshot version of the release branch.
> E.g., currently the latest stable release is 1.10.0, but the documentation
> described as "Flink 1.10 (Latest stable release)" is actually built with
> 1.10-SNAPSHOT. As a consequence, users might be confused when they use
> release 1.10.0 and some latest documentation changes meant for 1.10.1.
> [This
> comment|https://github.com/apache/flink/pull/11300#issuecomment-624776199]
> shows one of such confusions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
