Update release guidelines.
Project: http://git-wip-us.apache.org/repos/asf/commons-rng/repo Commit: http://git-wip-us.apache.org/repos/asf/commons-rng/commit/c8962e09 Tree: http://git-wip-us.apache.org/repos/asf/commons-rng/tree/c8962e09 Diff: http://git-wip-us.apache.org/repos/asf/commons-rng/diff/c8962e09 Branch: refs/heads/master Commit: c8962e092c46c6bdccc87eb7a1695df9fa821d22 Parents: 193e543 Author: Gilles <er...@apache.org> Authored: Mon Nov 28 23:24:26 2016 +0100 Committer: Gilles <er...@apache.org> Committed: Mon Nov 28 23:24:26 2016 +0100 ---------------------------------------------------------------------- doc/release/release.howto.txt | 34 ++++++++++++++++++++++++---------- 1 file changed, 24 insertions(+), 10 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/commons-rng/blob/c8962e09/doc/release/release.howto.txt ---------------------------------------------------------------------- diff --git a/doc/release/release.howto.txt b/doc/release/release.howto.txt index 875c8c9..1b7fda5 100644 --- a/doc/release/release.howto.txt +++ b/doc/release/release.howto.txt @@ -79,17 +79,31 @@ Preliminary checks: (1) -As a first optional step, you can test that everything works locally, i.e. +As an optional step, you can test that everything works locally, i.e. that the build process can create all the necessary artifacts. -The command - $ mvn clean deploy -Prelease -Ptest-deploy + (1a) + The command -should create the artifacts in the "target/deploy" directory. + $ mvn clean deploy -Prelease -Ptest-deploy -Pcommons-rng-examples -At some point when processing the above command, the GPG passphrase will be -requested; to avoid problems, the "gpg2" executable should be specified in -the "settings.xml" file (see below). + should create the artifacts in the "target/deploy" directory. + + At some point when processing the above command, the GPG passphrase will be + requested; to avoid problems, the "gpg2" executable should be specified in + the "settings.xml" file (see below). + + (1b) + When the above works, you can test the creation of the full distribution + files with the following commands: + + $ ( cd dist-archive && mvn assembly:single ) + + The "dist-archive/target" directory will then contain those files: + commons-rng-1.0-SNAPSHOT-bin.tar.gz + commons-rng-1.0-SNAPSHOT-bin.zip + commons-rng-1.0-SNAPSHOT-src.tar.gz + commons-rng-1.0-SNAPSHOT-src.zip (2) @@ -172,7 +186,7 @@ The "release notes" file will be created by gathering all the changes collected during development in the file "src/changes/changes.xml". Create it by running: - $ mvn -Prelease-notes changes:announcement-generate + $ mvn -Prelease-notes -Pcommons-rng-examples changes:announcement-generate Check the file for weird line breaks, and commit the updated files to git: @@ -272,7 +286,7 @@ in the settings.xml file. You can then run - $ mvn clean deploy -Prelease + $ mvn clean deploy -Prelease -Pcommons-rng-examples which will transfer the artifacts to the Nexus repository located at https://repository.apache.org/index.html#stagingRepositories @@ -359,7 +373,7 @@ login and copy the contents of your file to "SSH Key (authorized_keys line)". Then run these commands: - $ mvn site site:stage + $ mvn -Pcommons-rng-examples site site:stage $ cd target $ mv site commons-rng-1.0-RC1-site $ lftp sftp://__your_apache_logi...@home.apache.org
