[jackrabbit-filevault] branch master updated: releng: clarify release:prepare

[kw...@apache.org]

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

kwin pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/jackrabbit-filevault.git


The following commit(s) were added to refs/heads/master by this push:
     new 7104f863 releng: clarify release:prepare
7104f863 is described below

commit 7104f8633b85e604c905a7dd4e2f3c6c03048ef5
Author: Konrad Windszus <kw...@apache.org>
AuthorDate: Fri Sep 16 11:24:55 2022 +0200

    releng: clarify release:prepare
---
 src/site/markdown/howto_release.md | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/src/site/markdown/howto_release.md b/src/site/markdown/howto_release.md
index 652f339c..b8b5ed4a 100644
--- a/src/site/markdown/howto_release.md
+++ b/src/site/markdown/howto_release.md
@@ -49,8 +49,7 @@ Release management tasks
     
     1. (optional, prepare your environment. e.g.: `$ export version=3.1.36`)
     2. Execute `mvn clean deploy -Papache-release -Dmaven.deploy.skip=true`. This tests if the release would work.
-    3. Execute `mvn release:prepare`. This will update the POM files and tag the release in Git (btw: specifying the
-        release version on the commandline doesn't update the module poms anymore lately).
+    3. Execute `mvn release:prepare`. This will update the POM files and tag the release in Git after asking for the release version number.
     4. Execute `mvn release:perform`. This will build the tagged release and deploy the artifacts to
         a new staging repository on _repository.apache.org_. 
         After the build, login to [https://repository.apache.org/][2] and you should see it there.