We have fixed quite a few bugs and added some significant enhancements
since Apache Commons RNG 1.3 was released, so I would like to release
Apache Commons RNG 1.4.

Apache Commons RNG 1.4 RC3 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/rng/1.4-RC3 (svn
revision 49824)
    https://home.apache.org/~aherbert/commons-rng-1.4-RC3-site/

The Git tag commit for this RC is RNG_1_4_RC3 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-rng.git;a=commit;h=RNG_1_4_RC3

You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-rng.git --branch
RNG_1_4_RC3 commons-rng-1.4-RC3
(signature can be checked from git using 'git tag -v RNG_1_4_RC3')

Commit ID the tag points at:
    9909be95e178b2f73831fe7330c143f13af176bb

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1572/org/apache/commons/

These are the artifacts and their hashes:

#Release SHA-512s
#Wed Sep 08 10:36:58 BST 2021
commons-rng-1.4-src.tar.gz=e3227362314cbff30d96c24430eb72d50637e2f54d26ff2bb6372d2a8f4165debd0d4915d656642a23009c5e2a960c8eb9a98fb283eef60b253e88a270a1056e
commons-rng-1.4-src.zip=bc2f1cdc52ed99d765c5dc8b60a3c093fd975107829aea532bf9f12c77596fc9abccf656d80f97e0dce33f99dd8833961c507edb99304612c49c75e4e0bb5463
commons-rng-1.4-bin.tar.gz=6b64112d627249b8c209be9f2ae57a14ceac63b635ec8048e8e695b0c2fa30c26d91c5cecc32f2b46758f20b6397be8783129e0d9a21efa446855df58c4a42c2
commons-rng-1.4-bin.zip=7aa8f4c0fe6784b94233e097f4ccc8dcbfcd95ae11eb0b7ec3a8af2f8d5336e6c20bfdaf52edf3b9aeabd69da01c0c99181015b687e22fc8cf969a6bf17b4372

The source code contains examples that are not part of the public API.
These examples contain Java 11 modules and are enabled using a profile (see
below).

Note: Testing randomness using statistical thresholds results in failures
at a given probability. The 'maven-surefire-plugin' is configured to re-run
tests that fail, and pass the build if they succeed within the allotted
number of reruns (the test will be marked as 'flaky' in the report).

I have tested this with 'mvn clean install' using:

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /usr/local/apache-maven-3.6.3
Java version: 1.8.0_241, vendor: Oracle Corporation, runtime:
/usr/lib/jvm/jdk1.8.0_241/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-153-generic", arch: "amd64", family:
"unix"

I have tested this with 'mvn clean package site site:stage
-Pcommons-rng-examples' using:

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: /usr/local/apache-maven-3.6.3
Java version: 11.0.11, vendor: Ubuntu, runtime:
/usr/lib/jvm/java-11-openjdk-amd64
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-153-generic", arch: "amd64", family:
"unix"

Details of changes since 1.3 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/rng/1.4-RC3/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/rng/1.4-RC3/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/rng/1.4-RC3/site/index.html
    (note some *relative* links are broken and the 1.4 directories are not
yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 1.3):

https://home.apache.org/~aherbert/commons-rng-1.4-RC3-site/commons-rng-client-api/japicmp.html

https://home.apache.org/~aherbert/commons-rng-1.4-RC3-site/commons-rng-core/japicmp.html

https://home.apache.org/~aherbert/commons-rng-1.4-RC3-site/commons-rng-simple/japicmp.html

https://home.apache.org/~aherbert/commons-rng-1.4-RC3-site/commons-rng-sampling/japicmp.html


RAT Report:

https://home.apache.org/~aherbert/commons-rng-1.4-RC3-site/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now.

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thank you,

Alex Herbert,
Release Manager (using key BC87A3FD0A54480F0BADBEBD21939FF0CA2A6567)

The following is intended as a helper and refresher for reviewers.

Validating a release candidate
==============================

These guidelines are NOT complete.

Requirements: Git, Java, Maven.

You can validate a release from a release candidate (RC) tag as follows.

1) Extract the .tar.gz or .zip source archive from the release artifacts.

unzip commons-rng-1.4-src.zip
cd commons-rng-1.4-src

Alternatively clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-rng.git --branch
RNG_1_4_RC3 commons-rng-1.4-RC3
cd commons-rng-1.4-RC3

2) Check Apache licenses

This step is not required if the site includes a RAT report page which you
then must check.

mvn apache-rat:check

3) Check binary compatibility

This step is not required if the site includes a JApiCmp report page which
you then must check.

mvn package -DskipTests -P japicmp japicmp:cmp

4) Build the package

mvn -V clean verify

You can record the Maven and Java version produced by 'mvn -v' in your VOTE
reply.

To gather OS information from a command line:
Windows: ver
Linux: uname -a

5) Build the site for a multi-module project

mvn package site site:stage

Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

-the end-

Reply via email to