Skip to content

Latest commit

 

History

History
24 lines (20 loc) · 1.54 KB

RELEASING.adoc

File metadata and controls

24 lines (20 loc) · 1.54 KB

How to release mvnd

  • Run the release script which will update the versions, the changelog, the native binaries and will tag the new git commit. This new tag will trigger the release workflow on this newly created tag.

./build/release-build.sh <released-version> <next-SNAPSHOT>

  • While the darwin-aarch64 is not supported by github, you need to perform a clean build on the tagged branch on a Apple M1 computer and upload the two binary distributions as additional assets to the draft release that has been generated at github.

  • Once the workflow completes, run the release-candidate script which will download the built assemblies, compute the checksums and signatures and commit them to the dev distribution repository releases.

./build/release-candidate.sh <released-version>

You can now call a vote on the dev mailing list pointing to that release candidate.

  • Once the vote passes, publish the release using the following command:

./build/release-publish.sh <released-version>
Warning
 TODO: document the publication process (move to the final svn area, homebrew, sdkman, choco updates…​)