michaeljmarshall commented on PR #133: URL: https://github.com/apache/pulsar-site/pull/133#issuecomment-1175722892
> I see you've generated API docs for major and minor versions, so for future releases, we need to generate API docs for each version (align with the Pulsar release), correct? Yes, that is correct. We currently expect the release manager to generate the swagger docs and the python client docs. I think we could make it so the release manager only has to run a single command to generate all docs for the release. Alternatively, we could probably make some github action that runs when tags are released, but it's probably not worth the effort, and it might lead to minor errors. > ## Release owner > > Currently, API docs are automatically generated. > > In this PR, you've changed the automatic workflow to manual work, so who will be responsible for generating API docs? Release managers? If so, would you like to add this required step to the [Pulsar release process - wiki](https://github.com/apache/pulsar/wiki/Release-process)? The current automated process only updates the latest docs based on the `apache/pulsar` repo's `master` branch. The docs have `-SNAPSHOT` on the end because they are not generated based on the correct tag of the Pulsar code base. While it'd be nice to have a completely automated solution, I think it'll be easier to add a manual solution that relies on running a single script. Once we have the script completely implemented, it might be easier to automate the process. Additionally, I will update the release process wiki once we have a new process. For now, I think my primary question is if we can get rid of the broker's Javadocs. -- 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: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
