Hi Alex,

  [x] +1 Release these artifacts

Built from tag, with `mvn clean test install site` using

Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
Maven home: /opt/apache-maven-3.8.5
Java version: 17.0.4, vendor: Private Build, runtime:
/usr/lib/jvm/java-17-openjdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "5.15.0-52-generic", arch: "amd64", family:
"unix"

Inspected dist area files (tar/zip, from binary/sources) and found no
issues. NOTICE files OK, Release Notes files OK, signatures look OK.

Found no issues looking at a few site reports from the link in this vote
email (too many modules to inspect everything, sorry!)

Thanks!

Bruno

On Sat, 29 Oct 2022 at 05:53, Alex Herbert <aherb...@apache.org> wrote:

> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Numbers 1.0 was released, so I would like to
> release Apache Commons Numbers 1.1.
>
> Apache Commons Numbers 1.1 RC1 is available for review here:
>     https://dist.apache.org/repos/dist/dev/commons/numbers/1.1-RC1
> (svn revision 57646)
>
> The Git tag for this RC is commons-numbers-1.1-RC1 which you can browse
> here:
>
> https://gitbox.apache.org/repos/asf?p=commons-numbers.git;a=commit;h=commons-numbers-1.1-RC1
>
> You may checkout this tag using:
>     git clone https://gitbox.apache.org/repos/asf/commons-numbers.git
> --branch <https://gitbox.apache.org/repos/asf/commons-numbers.git--branch>
> commons-numbers-1.1-RC1 commons-numbers-1.1-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1604/org/apache/commons/
>
> These are the artifacts and their hashes:
>
>
> commons-numbers-1.1-bin.tar.gz=e3827bf92a58bef6c1e1760a771c38a78ef74d452c030e7e0b0220ef439a93e7f9102bf871b1bcc6d2fd36e5cdd3f8cf457bf020d5c7b58b93675cade2937040
>
> commons-numbers-1.1-bin.zip=5d4f132253df294f30eea4893d94ad3c63788dee5c6b006f861ea502da3da34918b215b3d5cb2f534a59f864ba4c3ba1f536cb914c1de0388974e19e3e5f9b52
>
> commons-numbers-1.1-src.tar.gz=7398d725ac4fa7d8c3ef6f3578630ffd66c740c70120dfea1dd2dbe99dcbe75925bce7f3c98651613c13878997ccf669b4c66dd8c13e09b737988ce5c69419c6
>
> commons-numbers-1.1-src.zip=7b448154dc0f917004780e52e982fdbc852840bb5dc87fa14d20cf0fb7701d755fbcaf492a27058db4cfbb6e9e024e19929857b69289d2c77c89f605addc998a
>
> I have tested this with 'mvn clean install' using:
>
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: /usr/local/apache-maven-3
> Java version: 1.8.0_333, vendor: Oracle Corporation, runtime:
> /usr/lib/jvm/jdk1.8.0_333/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "4.15.0-194-generic", arch: "amd64", family:
> "unix"
>
> I have tested this with 'mvn package site site:stage
> -Pcommons-numbers-examples' using:
>
> Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
> Maven home: /usr/local/apache-maven-3
> Java version: 11.0.16, 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-194-generic", arch: "amd64", family:
> "unix"
>
> Note: The examples included by the profile require Java 9+.
>
> Details of changes since 1.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/numbers/1.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/numbers/1.1-RC1/site/changes-report.html
>
> Site:
>     https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/
>     (note some *relative* links are broken and the 1.1 directories are
> not yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 1.0):
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-angle/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-arrays/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-combinatorics/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-complex/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-core/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-field/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-fraction/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-gamma/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-primes/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-quaternion/japicmp.html
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-site/commons-numbers-rootfinder/japicmp.html
>
> RAT Report:
>
> https://home.apache.org/~aherbert/commons-numbers-1.1-RC1-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) Clone and checkout the RC tag
>
> git clone https://gitbox.apache.org/repos/asf/commons-numbers.git
> --branch <https://gitbox.apache.org/repos/asf/commons-numbers.git--branch>
> commons-numbers-1.1-RC1 commons-numbers-1.1-RC1
> cd commons-numbers-1.1-RC1
>
> OR
>
> Extract the source from a source distribution archive at
> https://dist.apache.org/repos/dist/dev/commons/numbers/1.1-RC1
>
> 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
>
> Newer components use JApiCmp with the japicmp Maven Profile:
>
> This step is not required if the site includes a JApiCmp report page
> which you then must check.
>
> mvn install -DskipTests -P japicmp japicmp:cmp
>
> 4) Build the package
>
> 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
>
> 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
>
> -the end-
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Reply via email to