adoroszlai commented on PR #38:
URL: https://github.com/apache/ozone-site/pull/38#issuecomment-1551195326

   Thanks @krishnaasawa1 for working on this.
   
   [Downloads page](https://ozone.apache.org/downloads/) lists the 5 most 
recent release, linking to the announcement for each.  The announcement for old 
releases are still available 
([example](https://ozone.apache.org/release/0.5.0-beta/)), can be reached by 
e.g. editing the URL, having an old bookmark, or via search engines.
   
   Similarly, [Documentation page](https://ozone.apache.org/docs/) only lists 4 
most recent releases + "edge (master)".  Old docs are only accessible by same 
means (editing URL, search engines).
   
   I think the release page template should be updated to omit the 
"Documentation" link for outdated releases to avoid broken links.  For that, we 
also need to add a flag in release metadata to indicate being outdated.  Both 
of this must be done on the `master` branch, which gets generated into the 
`asf-site` branch.
   
   Template:
   
https://github.com/apache/ozone-site/blob/7292d848f044723623d58f0df1ebae9ca47adb42/layouts/release/single.html#L37
   
https://github.com/apache/ozone-site/blob/7292d848f044723623d58f0df1ebae9ca47adb42/layouts/release/single.html#L54
   
   Metadata:
   
https://github.com/apache/ozone-site/blob/7292d848f044723623d58f0df1ebae9ca47adb42/content/release/0.5.0-beta.md?plain=1#L1-L5
   
   If remove old docs completely, search engines might still list them but then 
result in 404.  Alternatively, instead of removing old docs, we might add a 
warning at the top of each old doc page and link to more recent versions.


-- 
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]


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

Reply via email to