build release documentation and build_release_candidate.sh conflict on how to generate pydoc and javadoc
Open
bug
build
P3
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 4.7k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 196
Description
build_release_candidate.sh generates a handy PR (modulo bug: https://issues.apache.org/jira/browse/BEAM-9091),
but step 6 (https://beam.apache.org/contribute/release-guide/#6-prepare-documents) in the instructions tells us to run tox, unpack maven artifacts, etc.
Which is it?
Imported from Jira [BEAM-9092](https://issues.apache.org/jira/browse/BEAM-9092). Original Jira may contain additional context.
Reported by: udim.
Contributor guide
Assessment
This issue has not been assessed yet.