Had a quick look at some of the files in the Maven repository, and found no
issues.
Checked signatures and found nothing out of ordinary.
[x] +1 Release these artifacts
Thanks!
Bruno
On Saturday, 4 April 2020, 2:19:04 pm NZDT, Matt Juntunen
<matt.juntu...@hotmail.com> wrote:
> @Matt, is the Maven repository link working for you?
It is not. I'm not sure what's going on with that. I can log into Nexus and
view the artifacts under staging repo 1497, though. I can also browse the
contents if I go to
https://repository.apache.org/content/repositories/orgapachecommons-1497/org/apache/commons/.
Perhaps this is an issue with single module vs multi-module projects?
-Matt
________________________________
From: Bruno P. Kinoshita <ki...@apache.org>
Sent: Friday, April 3, 2020 8:49 PM
To: Commons Developers List <dev@commons.apache.org>
Subject: Re: [VOTE] Release Apache Commons Numbers (full distribution)
1.0-beta1 based on RC1
Build passed locally from tag, with `mvn clean test install site` after 21mins
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_242, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-91-generic", arch: "amd64", family: "unix"
In the changelog (report & RELEASE-NOTES.txt) I could see the warning about it
being a beta release, great.
The code coverage is really good, well done. Found no RAT issues. Other reports
look good too.
LICENSE, NOTICE, RELEASE-NOTES look OK too in the archives in the dist area. No
issues with files signatures.
@Matt, is the Maven repository link working for you?
>Maven artifacts are here:
>
>https://repository.apache.org/content/repositories/orgapachecommons-1497/org/apache/commons/commons-numbers/1.0-beta1/
Cheers
Bruno
On Saturday, 4 April 2020, 4:25:26 am NZDT, Matt Juntunen
<matt.juntu...@hotmail.com> wrote:
We have been working hard to prepare Apache Commons Numbers for an initial
release, so I would like to release Apache Commons Numbers (full distribution)
1.0-beta1.
Apache Commons Numbers (full distribution) 1.0-beta1 RC1 is available for
review here:
https://dist.apache.org/repos/dist/dev/commons/numbers/1.0-beta1-RC1 (svn
revision 38800)
The Git tag commons-numbers-1.0-beta1-rc1 commit for this RC is
3406c0980b4bc1071314bbb081dad2ef49cd68d3 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-numbers.git;a=commit;h=3406c0980b4bc1071314bbb081dad2ef49cd68d3
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-numbers.git --branch
commons-numbers-1.0-beta1-rc1 commons-numbers-1.0-beta1-rc1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1497/org/apache/commons/commons-numbers/1.0-beta1/
These are the artifacts and their hashes:
#Release SHA-512s
#Fri Apr 03 08:03:05 EDT 2020
commons-numbers-1.0-beta1-bin.tar.gz=0a18312d62e53937ac82e17c971db028054da45d9ee3937aec80f296ab73fa49f5dc42c9e381ae9693240284993e4426e70a27b412c409c1c5f1b2f3ad78b551
commons-numbers-1.0-beta1-bin.zip=36ffbb850f0f6a51dd96236ddf27566e82ab6b68344ee9ff29a680e78ebdd4e136675856576f03ca4af63362fd115282e2b2289715db4587933a00b7d0a58f62
commons-numbers-1.0-beta1-src.tar.gz=963dd030406a35d7abf180e87ea0d07e4d663da222403ac9cab13ed2d64076422a924fb3e3732c0168de8224396737df87aaeb06971dab9582e599a0edd8ba1c
commons-numbers-1.0-beta1-src.zip=db931f1b9c7383ffeb87db2dc8629fc19f2044ff6b2e4a96d1284512106d59db81428eed7cbdd1e5e99dfebc3d68738dc87197bf67659d53d1b7c8db3545478c
I have tested this with ***'mvn clean install site'*** using:
***
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T14:49:05-05:00)
Maven home: /home/matt/tools/maven/apache-maven-3.5.3
Java version: 1.8.0_242, vendor: Private Build
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-91-generic", arch: "amd64", family: "unix"
***
Details of changes are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/numbers/1.0-beta1-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/numbers/1.0-beta1-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/numbers/1.0-beta1-RC1/site/index.html
(note some *relative* links are broken and the 1.0-beta1 directories are
not yet created - these will be OK once the site is deployed.)
CLIRR Report:
N/A
JApiCmp Report:
N/A
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/numbers/1.0-beta1-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 that 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,
Matt Juntunen,
Release Manager (using key 7DD53AEFEDF1C3D392B51EBE346F4FCECFB70B1A)
For 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
commons-numbers-1.0-beta1-rc1 commons-numbers-1.0-beta1-rc1
cd commons-numbers-1.0-beta1-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
Older components still use Apache Clirr:
This step is not required if the site includes a Clirr report page which you
then must check.
mvn clirr:check
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 single module project
Note: Some plugins require the components to be installed instead of packaged.
mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html
6) 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
