MartijnVisser opened a new pull request, #27412:
URL: https://github.com/apache/flink/pull/27412

   ## What is the purpose of the change
   
   * The "stable version" link in the warning banner for unreleased/out-of-date 
docs now redirects to the equivalent page in the stable docs instead of always 
redirecting to the homepage.
   * To make sure that search engines point to the right version of the docs, 
the generated HTML contains a [canonical 
tag](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls)
 to indicate that the docs that are on "stable" are the most trustworthy ones.
   
   Note: this change needs to be backported to all the previous docs, and it 
also appears that some versions are not yet marked as "outdated". That's for 
follow-up PRs into those release branches
   
   ## Brief change log
   
   * Use regex in Hugo partial to redirect the user to the right deeplink on 
the stable docs
   * Includes an auto-generated canonical tag
   
   ## Verifying this change
   
   * Verified this by running the Hugo Docker image locally, and testing out 
the deeplinks and generated canonical tags by inspecting the source code
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): (yes / **no**)
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: (yes / **no**)
     - The serializers: (yes / **no** / don't know)
     - The runtime per-record code paths (performance sensitive): (yes / **no** 
/ don't know)
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / **no** / don't 
know)
     - The S3 file system connector: (yes / **no** / don't know)
   
   ## Documentation
   
     - Does this pull request introduce a new feature? (yes / **no**)
     - If yes, how is the feature documented? (**not applicable** / docs / 
JavaDocs / not documented)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to