You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sedona.apache.org by "Kristin Cowalcijk (Jira)" <ji...@apache.org> on 2023/06/20 07:12:00 UTC

[jira] [Created] (SEDONA-306) Prepare for releasing Sedona 1.4.1

Kristin Cowalcijk created SEDONA-306:
----------------------------------------

             Summary: Prepare for releasing Sedona 1.4.1
                 Key: SEDONA-306
                 URL: https://issues.apache.org/jira/browse/SEDONA-306
             Project: Apache Sedona
          Issue Type: Task
            Reporter: Kristin Cowalcijk


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:

# Added an {{enable-all-submodules}} profile for `release:prepare` to substitute versions of all submodules.
# Don't generate and publish scala docs when building {{sedona-core}}, {{sedona-vis}} and {{sedona-flink}}. We'll publish java docs for these modules and this also get rid of conflicts caused by deploying javadocs.jar twice.
# Don't run gpg-sign in deploy phase. Now the signatures generated by gpg-sign in verify phase are all correct, and there's no need to manually fix signature issues.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)