You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@commons.apache.org by er...@apache.org on 2022/12/22 10:10:18 UTC

[commons-math] 01/10: Update release howto.

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

erans pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-math.git

commit ab465fd22d4f8e0bc75df16f405ccac4815f9687
Author: Gilles Sadowski <gi...@gmail.com>
AuthorDate: Tue Dec 13 18:04:33 2022 +0100

    Update release howto.
---
 doc/release/release.howto.txt | 14 ++++++++++----
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/doc/release/release.howto.txt b/doc/release/release.howto.txt
index 1c3d31c23..f9716155a 100644
--- a/doc/release/release.howto.txt
+++ b/doc/release/release.howto.txt
@@ -148,12 +148,18 @@ In particular:
    about the API docs of the new release.
  * Estimate a release date (taking into account the release vote delay) and
    insert it in the "src/changes/changes.xml" file.
- * Update the "pom.xml" to contain the final version number and not a SNAPSHOT:
-   Assuming that the release version will be "4.0-beta1", modify the "<version>" tag to
-   read:
+ * Update all the "pom.xml" files to contain the final version number and not
+   a SNAPSHOT: Assuming that the release version will be "4.0-beta1", the
+   "<version>" should read:
 
     <version>4.0-beta1</version>
 
+   This can be done for all modules with command
+     $ mvn versions:set -DnewVersion=4.0-beta1 -DgenerateBackupPoms=false
+
+   Note: Perform a "grep" in order to ensure that all occurences have been
+   updated correctly.
+
    Modify the section of "<properties>" that also refers to version numbers.
    You should uncomment the "<commons.rc.version>" line and indicate the
    appropriate numbering of the release candidate: This refers to how many
@@ -275,7 +281,7 @@ in the settings.xml file.
 
 You can then run
 
-  $ mvn clean deploy -Prelease
+  $ mvn -Duser.name="__Your_Apache_id__" clean deploy -Prelease
 
 which will transfer the artifacts to the Nexus repository located at
   https://repository.apache.org/index.html#stagingRepositories