The plan is to have javadocs/pydocs on a branch inside this repo. The implementation I have in progress creates a new `release-docs` branch with these docs moved up to the top of the directory structure. That work is staged here: https://github.com/swegner/beam-site/tree/release-docs
The exact branch we use, whether `asf-site` or `release-docs` doesn't really matter. We are currently publishing the website from `asf-site`, so the migration is trickier if we want to reuse this existing branch. We could flip back to `asf-site` after migration, although I sort of like having a different branch name to avoid confusion with the apache/beam `asf-site` branch. Thoughts? [ Full content available at: https://github.com/apache/beam-site/pull/567 ] This message was relayed via gitbox.apache.org for [email protected]
