[ 
https://issues.apache.org/jira/browse/HDDS-15124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Doroszlai resolved HDDS-15124.
-------------------------------------
    Fix Version/s: 2.2.0
       Resolution: Fixed

> [Docs] Fix broken in-repo doc links
> -----------------------------------
>
>                 Key: HDDS-15124
>                 URL: https://issues.apache.org/jira/browse/HDDS-15124
>             Project: Apache Ozone
>          Issue Type: Task
>          Components: documentation
>            Reporter: Chi-Hsuan Huang
>            Assignee: Chi-Hsuan Huang
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 2.2.0
>
>
> h2.  
> A grep across the repo finds 15 broken doc links pointing at 
> {{[https://ozone.apache.org/docs/]
> {current,edge}
> /...html}}. The website was migrated to Docusaurus and these legacy paths no 
> longer resolve.
> h2. Scope 
> Rewrite the 4 {{current/...html}} links to their current Docusaurus 
> equivalents:
>  * {{CONTRIBUTING.md:78}}
>  * {{hadoop-ozone/dist/README.md:33}}
>  * {{hadoop-ozone/dist/README.md:41}}
>  * {{hadoop-ozone/dist/README.md:42}}
> These sit in the two highest-traffic docs in the tree (top-level contributor 
> guide + the README shipped in every binary release) and have no server-side 
> backstop in flight.
> h2. Relationship to apache/ozone-site#351
> [ozone-site#351|https://github.com/apache/ozone-site/pull/351] restores 
> {{static/docs/edge/}} on the website side. When merged, it will transparently 
> fix the 11 remaining {{edge/...html}} links in 
> {{{}hadoop-hdds/docs/content/{*}{{*}}{*}{{*}}{{}}}}. That work is 
> complementary, not alternative\{*} — {{current/...html}} paths are out of 
> #351's scope, so this ticket is still needed regardless of #351's outcome.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to