kgyrtkirk commented on pull request #1410: URL: https://github.com/apache/hive/pull/1410#issuecomment-680111530
> One of the advantages of including the site in docs on the main branch is that it will automatically get packaged as part of the releases, so I'd rather not give that up I think when releases are made we should also produce a `javadoc` jar - which should contain the actual docs... however - I might have misunderstood your comment. Let's consider for a moment that we would be putting the javadocs into the main branch: in that case I think every commit *must* also update the generated javadocs - to keep them up-to-date ; which would increase commit sizes, burden on contributors - and could also make commits harder to be reviewed... > How about if we put the generated javadoc in a branch named "javadoc-3.1". We could point the site to reference that branch on github. Would that be acceptable? If that's possible - then that would be a great solution! ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
