We have fixed a few bugs and added enhancements since Apache Commons
Parent 72 was released, so I would like to release Apache Commons
Parent 73.
Apache Commons Parent 73 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/73-RC1 (svn
revision 70876)
The Git tag commons-parent-73-RC1 commit for this RC is
260485b70e9ba65631fa870fe123dda030dea3e7 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=260485b70e9ba65631fa870fe123dda030dea3e7
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-73-RC1 commons-parent-73-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1770/org/apache/commons/commons-parent/73/
These are the artifacts and their hashes:
#Release SHA-512s
#Thu Aug 15 01:27:08 UTC 2024
commons-parent-73-bom.json=fe0a05bde1db1c5206676df02568ad1209ca75311d48faa32f2ce8174a0909f0d9c0b726d036449709f05e70b10e38d661329b87b84601a8ff72b1a9b03e682f
commons-parent-73-bom.xml=0ecefc06f07167d0bb7bee75ee8bb8bc0af0245155b28e8c16f938e428ffb7eefd058de21354c6fe089c5ace250159ed018d0e5305f2692181b0e135f7c3083f
commons-parent-73-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-73-src.tar.gz=a76212a755e6c35b17a1f3abce2de538e5c04b96384259e15526ef56ca0e2158e8b2c52e4e3b0f4d49fb85b15cdfbc8abb2d188cc0323ed202106d82640c8823
commons-parent-73-src.zip=a1ad546ea2f35c04067b4ebce859cc0a6754ed9738824a1de6a32c15ac778f2cae04e927420a853be6c9886aa6643026506ac3acac4cbdd578bfe7902cf4e23f
org.apache.commons_commons-parent-73.spdx.json=ffc02d8362d15b2a1fa4f2771d4e6e51e0dcf7d82ec570d2133f405e26836bef437bd86c73ba2f576f9566db641f1c8462eb495d63aa6bf84bfa6afef697c1b0
I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy
-P jacoco -P japicmp clean package site deploy' using:
openjdk version "17.0.12" 2024-07-16
OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256)
Maven home: /usr/local/Cellar/maven/3.9.8/libexec
Java version: 17.0.12, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
Darwin **** 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00
PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
Details of changes since 72 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/73-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/73-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/73-RC1/site/index.html
(note some *relative* links are broken and the 73 directories are
not yet created - these will be OK once the site is deployed.)
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/parent/73-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,
Gary Gregory,
Release Manager (using key 86fdc7e2a11262cb)
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.
1a) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-73-RC1 commons-parent-73-RC1
cd commons-parent-73-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/73-RC1/source
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
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
