This is an automated email from the ASF dual-hosted git repository.

gnodet pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git


The following commit(s) were added to refs/heads/master by this push:
     new d377916  Fix release guide and publish script
d377916 is described below

commit d37791600d193d3ed6b55d846c53ddbbeaf99fc7
Author: Guillaume Nodet <gno...@gmail.com>
AuthorDate: Fri Apr 29 19:28:05 2022 +0200

    Fix release guide and publish script
---
 RELEASING.adoc   | 13 +++++++++----
 build/publish.sh |  1 +
 2 files changed, 10 insertions(+), 4 deletions(-)

diff --git a/RELEASING.adoc b/RELEASING.adoc
index af0a8fe..4e93c5d 100644
--- a/RELEASING.adoc
+++ b/RELEASING.adoc
@@ -1,11 +1,16 @@
 = How to release `mnvd`
 
+* Run the 
https://raw.githubusercontent.com/apache/maven-mvnd/master/build/release.sh[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 
https://raw.githubusercontent.com/apache/maven-mvnd/master/.github/workflows/release.yaml[release
 workflow] on this newly created tag.
 [source,shell]
 ----
 ./build/release.sh <released-version> <next-SNAPSHOT>
 ----
 
-* Re-run the 
https://github.com/apache/maven-mvnd/actions?query=workflow%3A%22Mvnd+Changelog%22[Changelog
 update] manually.
-* When it terminates, find the section about the current release
-  in the 
https://raw.githubusercontent.com/mvndaemon/mvnd/master/CHANGELOG.md[Changelog] 
and copy its MarkDown source
-  to the respective release page. The release page will appear once the 
release build is finished.
+
+* Once the workflow completes, run the 
https://raw.githubusercontent.com/apache/maven-mvnd/master/build/publish.sh[publish
 script] which will download the built assemblies, compute the checksums and 
signatures and commit them to the 
https://dist.apache.org/repos/dist/dev/maven/mvnd/[dev distribution repository]
+https://github.com/apache/maven-mvnd/releases[releases].
+You can now call a vote on the mailto:d...@maven.apache.org[dev mailing list] 
pointing to that release candidate.
+
+* Once the vote passes, publish the release.
+
+WARNING: *TODO*: document the publication process (move to the final svn area, 
homebrew, sdkman, choco updates...)
diff --git a/build/publish.sh b/build/publish.sh
index 92ae19a..b6cdcd1 100755
--- a/build/publish.sh
+++ b/build/publish.sh
@@ -58,6 +58,7 @@ do
   gpg --detach-sign --armor ${FILE}
 done
 
+cd ..
 svn co https://dist.apache.org/repos/dist/dev/maven/mvnd
 mv ${VERSION} mvnd
 cd mvnd

Reply via email to