jackye1995 commented on pull request #3378: URL: https://github.com/apache/iceberg/pull/3378#issuecomment-952361358
And I think #2719 is trying to tackle this same versioning issue only for javadoc. We can solve both of them in the same way. If we enable versioning for the entire website, then it does not make sense for each version of the website to have all the previous javadoc versions. We can have a 1:1 mapping between website and javadoc. Btw, this also raises the question about how we deal with the python doc releases. Maybe website release version should be different from the java release version, e.g. using release date as the website version number, and there is a table describing the java and python versions of the specific release date. But maybe that is too much for now? -- 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]
