MINOR: Add a command to make site-docs and Javadocs updates easier on version release #20478
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clolov
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The Kafka website is hosted in a separate repository than the Kafka
code. The files versioned in the kafka-site repository are generated as
part of the version release process and then copied over. Today, this is
a manual process detailed in
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=34840886#ReleaseProcess-Websiteupdateprocess
This PR aims to simplify the manual steps by adding a sub-command to the
release.py script. The command uses the javadocs and *-site-docs.tgz in
the .release_work_dir and copies them over to the kafka-site repository.
There is a rudimentary dry-run sub-sub-command which can be used for
path-checking.
The addition to the script makes the assumption that the kafka-site
repository is on the same level as the kafka repository on a user's
machine. In the suggestion for subsequent commands it makes the further
assumption that the branch used in the kafka-site repository is
asf-site.
There are many things which we can improve about the overall script and
this addition in particular, but it is a start 😊.
I have tested this manually as part of the 4.0.1 release process and
cross-checked with the manual changes I did in
apache/kafka-site#718 and
apache/kafka-site#719