errose28 commented on PR #10829: URL: https://github.com/apache/ozone/pull/10829#issuecomment-5047754908
Yeah we can leave this open for a week or two, there's no rush. The only open issues I'm aware of are: - New releases ship with outdated docs embedded in them - Confusing for devs where to update documentation > Originally, the idea was to have the docs shipped with the binary so admin can reference even without internet access. But that was a long time ago. In any case, that wouldn't work now given our doc has migrated to the website repo. Yes this was a concern when we started the new website. At the time it was deemed a minor issue, because even though the cluster may be airgapped, the developer working on it almost certainly isn't and can go to `ozone.apache.org` in their regular browser. As mentioned in the description, I'm also fine with removing the docs links from the WebUI all together, but I think they are useful in the common case. I previously advocated for putting the site in a separate repo but to this day I'm not sure it was the right choice. For a myriad of reasons it seems like a mono repo would have been easier. -- 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]
