Files
maven-mvnd/RELEASING.adoc
Tamas Cservenak 446c292709 Port all the mvnd-1.x fixes for release to master (#1027)
Changes:
* Drop CHANGELOG.md and tool, it is confused by two branches (1.x and master).
* Update GH workflows, they now provide all 4 needed binaries
* Release scripts: do NOT push, user will (but remind user)
* native: Makefile and built binaries updated (cross checked with @gnodet )
2024-06-17 20:42:29 +02:00

25 lines
1.5 KiB
Plaintext

= How to release `mvnd`
* Run the https://raw.githubusercontent.com/apache/maven-mvnd/master/build/release-build.sh[release script] which will update the versions, the native binaries and will tag the new git commit. This new tag will trigger the https://raw.githubusercontent.com/apache/maven-mvnd/master/.github/workflows/release.yaml[release workflow] on this newly created tag.
[source,shell]
----
./build/release-build.sh <released-version> <next-SNAPSHOT>
----
Warning for Fedora users: The RedHat `podman` is usually preinstalled and happily coexisting with `Docker`. Make sure Docker is being used, usually by setting `OCI_EXE=docker` env variable.
* Once the workflow completes, run the https://raw.githubusercontent.com/apache/maven-mvnd/master/build/release-candidate.sh[release-candidate script] which will download the built assemblies, compute the checksums and signatures, commit them to the https://dist.apache.org/repos/dist/dev/maven/mvnd/[dev distribution repository]
https://github.com/apache/maven-mvnd/releases[releases] and also upload them as assets to the staging area for the github draft release.
[source,shell]
----
./build/release-candidate.sh <released-version>
----
You can now call a vote on the mailto:dev@maven.apache.org[dev mailing list] pointing to that release candidate.
* Once the vote passes, publish the release using the following command:
[source,shell]
----
./build/release-publish.sh <released-version>
----
WARNING: *TODO*: document the publication process (move to the final svn area, homebrew, sdkman, choco updates...)