Note: The release notes detail bug fix NUMBERS-207 but the site Jira report for the fraction module [1] does not include the Jira link to NUMBERS-207 [2].
I could not set the ticket to resolved as Jira is currently (as of Apr 15, 2026 - 09:13 UTC) not allowing login using apache LDAP [3]. However the bug has been fixed. The site Jira report can be updated when Jira service is resumed. [1] https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-fraction/jira-changes.html [2] https://issues.apache.org/jira/browse/NUMBERS-207 [3] https://status.apache.org/ On Wed, 15 Apr 2026 at 16:01, Alex Herbert <[email protected]> wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Numbers 1.2 was released, > so I would like to release Apache Commons Numbers 1.3. > > Apache Commons Numbers 1.3 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1 (svn > revision 83807) > > The Git tag commons-numbers-1.3-RC1 commit for this RC is > commons-numbers-1.3-RC1, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-numbers.git;a=commit;h=commons-numbers-1.3-RC1 > > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-numbers.git > --branch commons-numbers-1.3-RC1 commons-numbers-1.3-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1927/org/apache/commons/ > > These are the artifacts and their hashes: > > > commons-numbers-1.3-bin.tar.gz=94ab95fce6c7729d07a58c02c3cca384fd74a2d8bb9cdad7c8943c673f2afefc92a67abfbce81437e17428f04863f9b0b32d46f9987346ac3e71ab3116927306 > > commons-numbers-1.3-bin.zip=5abb52b46658b220caa58ddbce86d6b4ef1db1c96d854a8d25312f54f1d7fdea2f099d5a62e88247782643e7f337d42b651caf4eebeec2c6a464766b21f35c93 > > commons-numbers-1.3-src.tar.gz=aab91d736c2336883fe4a29f8819723fb94cf75a281c092bdb8cdd53bb59b008f2f081f8c0d8f6904f8375329d593373f4a5e8c95e9601edfbdda07583e0412e > > commons-numbers-1.3-src.zip=6ea0a1eda07a31252a3effebca73f8a12a0f7f3a9649df1291cc2c90f12b826c363a1e713810b448c231c1df3ad14189cb0b0b97a35decd669f6c6d6b8cbb18c > > I have tested this with 'mvn clean install' using: > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /Users/ah403/software/apache-maven-3 > Java version: 11.0.29, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@11/11.0.29/libexec/openjdk.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "15.7.5", arch: "aarch64", family: "mac" > > I have tested this with 'mvn clean install site site:stage -Pexamples' > using: > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /Users/ah403/software/apache-maven-3 > Java version: 21.0.9, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.9/libexec/openjdk.jdk/Contents/Home > Default locale: en_GB, platform encoding: UTF-8 > OS name: "mac os x", version: "15.7.5", arch: "aarch64", family: "mac" > > Note: The examples require Java 9+. > > Details of changes since 1.2 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/RELEASE-NOTES.txt > > Site: > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/index.html > (Note some *relative* links are broken and the 1.3 directories are not > yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.2): > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-angle/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-arrays/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-combinatorics/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-complex/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-core/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-field/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-fraction/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-gamma/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-primes/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-quaternion/japicmp.html > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/commons-numbers-rootfinder/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/site/rat-report.html > > KEYS: > https://downloads.apache.org/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, and Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1a) Download and decompress the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/numbers/1.3-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must at least check source distributions. > > git clone https://gitbox.apache.org/repos/asf/commons-numbers.git > --branch commons-numbers-1.3-RC1 commons-numbers-1.3-RC1 > cd commons-numbers-1.3-RC1 > > 2) Checking the build > > All components should include a default Maven goal, such that you can run > 'mvn' from the command line by itself. > > 2) Check Apache licenses > > This step is not required if the site includes a RAT report page, which > you then must check. > This check should be included in the default Maven build, but you can > check it with: > > 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. > This check should be included in the default Maven build, but you can > check it with: > > mvn verify -DskipTests -P japicmp japicmp:cmp > > 4) Build the package > > This check should be included in the default Maven build, but you can > check it with: > > mvn -V clean package > > You can record the Maven and Java version produced by -V in your VOTE > reply. > To gather OS information from a command line: > Windows: ver > Linux: uname -a > > 4b) Check reproducibility > > To check that a build is reproducible, run: > > mvn clean verify artifact:compare -DskipTests -Dreference.repo= > https://repository.apache.org/content/repositories/staging/ > '-Dbuildinfo.ignore=*/*.spdx.json' > > Note that this excludes SPDX files from the check. > > 5) Build the site for a multi-module project > > mvn site > mvn site:stage > Check the site reports in: > - Windows: target\site\index.html > - Linux: target/site/index.html > > Note that the project reports are created for each module. > Modules can be accessed using the 'Project Modules' link under > the 'Project Information' menu (see <path-to-site>/modules.html). > > -the end- > >
