Apache
/
commons-math
mirror of https://github.com/apache/commons-math.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update release howto.

This commit is contained in:
Gilles Sadowski 2022-12-13 18:04:33 +01:00
parent 11237fb40f
commit ab465fd22d
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/release/release.howto.txt
View File

@ -148,12 +148,18 @@ In particular:
about the API docs of the new release. about the API docs of the new release.
* Estimate a release date (taking into account the release vote delay) and * Estimate a release date (taking into account the release vote delay) and
insert it in the "src/changes/changes.xml" file. insert it in the "src/changes/changes.xml" file.
* Update the "pom.xml" to contain the final version number and not a SNAPSHOT: * Update all the "pom.xml" files to contain the final version number and not
Assuming that the release version will be "4.0-beta1", modify the "<version>" tag to a SNAPSHOT: Assuming that the release version will be "4.0-beta1", the
read: "<version>" should read:
<version>4.0-beta1</version> <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. Modify the section of "<properties>" that also refers to version numbers.
You should uncomment the "<commons.rc.version>" line and indicate the You should uncomment the "<commons.rc.version>" line and indicate the
appropriate numbering of the release candidate: This refers to how many appropriate numbering of the release candidate: This refers to how many
@ -275,7 +281,7 @@ in the settings.xml file.
You can then run 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 which will transfer the artifacts to the Nexus repository located at
https://repository.apache.org/index.html#stagingRepositories https://repository.apache.org/index.html#stagingRepositories