Kontinuation opened a new pull request, #864:
URL: https://github.com/apache/sedona/pull/864

   ## Did you read the Contributor Guide?
   
   - Yes, I have read [Contributor 
Rules](https://sedona.apache.org/latest-snapshot/community/rule/) and 
[Contributor Development 
Guide](https://sedona.apache.org/latest-snapshot/community/develop/)
   
   ## Is this PR related to a JIRA ticket?
   
   - Yes, the URL of the associated JIRA ticket is 
https://issues.apache.org/jira/browse/SEDONA-306. The PR name follows the 
format `[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:
   
   1. Added an `enable-all-submodules` profile for `release:prepare` to 
substitute versions of all submodules.
   2. Don't generate and publish scala docs when building `sedona-core`, 
`sedona-viz` and `sedona-flink`. We'll publish java docs for these modules. 
This also gets rid of conflicts caused by deploying javadocs.jar twice.
   3. Don't run gpg-sign in the deploy phase. Now the signatures generated by 
gpg-sign in verify phase are all correct, and there's no need to fix signature 
issues manually.
   
   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 setup 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 differ.
   
   ## Did this PR include necessary documentation updates?
   
   - Yes, I have updated the documentation update.
   
   


-- 
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...@sedona.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to