[SEDONA-306] Prepare release 1.4.1 #864
Merged
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.
Did you read the Contributor Guide?
Is this PR related to a JIRA ticket?
[SEDONA-XXX] my subject
.What changes were proposed in this PR?
Due to the changes made to the project structure since Sedona 1.4.0, the release process of Sedona 1.4.1 changed a lot. We'll update the docs and address all the issues introduced to the release process. Notable changes are:
enable-all-submodules
profile forrelease:prepare
to substitute versions of all submodules.sedona-core
,sedona-viz
andsedona-flink
. We'll publish java docs for these modules. This also gets rid of conflicts caused by deploying javadocs.jar twice.We'll also submit release notes for 1.4.1 in the same pull request, as well as other trivial version changes. Experienced contributors can help check if these changes were made correctly.
How was this patch tested?
We've set up a local nexus repository and tested the release process. The release process to actually publish artifacts to repository.apache.org may be a little bit different.
Did this PR include necessary documentation updates?