We have fixed a few bugs and added enhancements since Apache Commons
Parent 75 was released, so I would like to release Apache Commons
Parent 76.
Apache Commons Parent 76 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/76-RC1 (svn
revision 71883)
The Git tag commons-parent-76-RC1 commit for this RC is
5c09ca8f175fcb1fbc41cac29109fbed6a5398f7 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=5c09ca8f175fcb1fbc41cac29109fbed6a5398f7
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-76-RC1 commons-parent-76-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1781/org/apache/commons/commons-parent/76/
These are the artifacts and their hashes:
#Release SHA-512s
#Wed Sep 25 19:40:35 UTC 2024
commons-parent-76-bom.json=a6757b2c02d65b1aa477a4b1e0ac3346009b4ef801339e2b69fc48926dd0a9dcc77242aff39b651915f9b5e6e4df089751db5308b73e69ae6d9c1568d3766bc7
commons-parent-76-bom.xml=107da41d82916ed431291ad49da88b1c5db8bf27d2df3b44873552af0944f16cdcea0ff7f183bf5324dc55ef2a60dc8fd90079f080ff69c62067d1fdd4495da8
commons-parent-76-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-76-src.tar.gz=5aa3f91670695e38f1cb157660829c9d2404106a78a065ce87c6f07b5e0ab11da2a82cd22aa2e50abcfc6614621487cedc9058655d0156d69d8ef553ec8bab7e
commons-parent-76-src.zip=6235c551574069c279e51f5cf50868f1be12c85f256cbd309111e3f8d943583b4ee963a3844f8bb42135c0dc4e35e4551a70b88f7cbb518c2510396020b5f064
org.apache.commons_commons-parent-76.spdx.json=86a8e6ee7785e0868ce69027b1c1d10b64874e04b1a8c5ec6516ca88f340a9ff240a9045866e0e4e03040ac9276ca6aad95ee7123ad78303cac09157d8774271
I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy
-P jacoco -P japicmp clean package site deploy' using:
openjdk version "21.0.4" 2024-07-16
OpenJDK Runtime Environment Homebrew (build 21.0.4)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.4, mixed mode, sharing)
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /usr/local/Cellar/maven/3.9.9/libexec
Java version: 21.0.4, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@21/21.0.4/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.0", arch: "x86_64", family: "mac"
Darwin ---- 24.0.0 Darwin Kernel Version 24.0.0: Mon Aug 12 20:54:30
PDT 2024; root:xnu-11215.1.10~2/RELEASE_X86_64 x86_64
Details of changes since 75 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/76-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/76-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/76-RC1/site/index.html
(note some *relative* links are broken and the 76 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/76-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-76-RC1 commons-parent-76-RC1
cd commons-parent-76-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/76-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
