Does this mean that we will need to check in the generated javadocs here (in the asf-site branch)? If so: * We'll need to update the [release manager scripts](https://github.com/apache/beam/blob/master/release/src/main/scripts/build_release_candidate.sh). Maybe create a JIRA to track that? * Won't this explode the size of the repo? I know this has been discussed by others, and we can leave it for later, but how feasible is to avoid checking in generated files? (now or in the future)
[ Full content available at: https://github.com/apache/beam/pull/6282 ] This message was relayed via gitbox.apache.org for [email protected]
