We have added enhancements since Apache Commons Parent 71 was
released, so I would like to release Apache Commons Parent 72.
Apache Commons Parent 72 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/72-RC1 (svn
revision 70453)
The Git tag commons-parent-72-RC1 commit for this RC is
5eb7ad71ec5db46c9e08527969c00bb3bfced5e3 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=5eb7ad71ec5db46c9e08527969c00bb3bfced5e3
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-72-RC1 commons-parent-72-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1761/org/apache/commons/commons-parent/72/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Jul 21 18:25:27 UTC 2024
commons-parent-72-bom.json=7d0abc1bf1aacd58aae935d3f89bb87fc2e5d257470da5033fdd055a5ed11a6422e0db2cbac5103e81099853667c17ac7fc79bc8c5d1103257bc0ae46b6dfb56
commons-parent-72-bom.xml=c51f4b9619b5502fc895ca7b2998dd868115ac16c6547e0a67355160858990f40f4399fd6ef5182cbb6e6d14e65bf91d48da83068a79d1f2808834ce2d89ff22
commons-parent-72-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-72-src.tar.gz=5c6e0bd4090906fe0dfef5bc204e0de37f2f6177e30a25f1a292734a41954f992e8ee617bfb25c284e96ca0f0d85285f8138721346a6084b023adf99f3b0d752
commons-parent-72-src.zip=2e9811baf549e88a94573fd4239e56180a62971af4bbf3d64f47ba37ea4dddf8d36e9074fd8ed9595172acdb35c0cc107ed5e9474756c6675b1d6bdecc49b558
org.apache.commons_commons-parent-72.spdx.json=6607c088dee95917cf5d06dc51731a6463a6deb66a069f52870d12f3c733b063b142376240829d9afc3356f430d17ba6b8f81bf0a20f418f56365aa2065fea29
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.5", arch: "x86_64", family: "mac"
Darwin **** 23.5.0 Darwin Kernel Version 23.5.0: Wed May 1 20:09:52
PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64
Details of changes since 71 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/72-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/72-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/72-RC1/site/index.html
(note some *relative* links are broken and the 72 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/72-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-72-RC1 commons-parent-72-RC1
cd commons-parent-72-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/72-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
