We have fixed a few bugs and added enhancements since the release of
Apache Commons Parent 95, so I would like to release Apache Commons
Parent 96.
Apache Commons Parent 96 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/96-RC1 (svn
revision 81951)
The Git tag commons-parent-96-RC1 commit for this RC is
7c11bd5e202526f66b99c947a77de42035428ccb, which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=7c11bd5e202526f66b99c947a77de42035428ccb
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-96-RC1 commons-parent-96-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1909/org/apache/commons/commons-parent/96/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Jan 17 12:45:00 UTC 2026
commons-parent-96-bom.json=1ec9858f681fbe8b1ba912693fe7cbecc6d5a35abfe417b83da55bbaf3a60a1c8e84acd8cbcb091467190d93a7258b461390b989f55ef74d2541b85bc0c279d1
commons-parent-96-bom.xml=5d6a691f7ddb531bf12227b79baa9688f6eb61c87c7dfd7847263ccca3b698b3696cf80b5e811c92060f74943d61e2115fa6b72065a2b2c0b2d1bb53072764fd
commons-parent-96-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a
commons-parent-96-src.tar.gz=db46676fe2d817c27f5a12efc579bef43f72a828bd9dd9d0c7f5b12a684247e7688a23256140e8bf0fec8019892bb498e66abc21f3dedfc648cb18ff30d875ff
commons-parent-96-src.zip=c66dac29bc614282e61eee9ca846d8e30abacf0e2506232e40c7349b219fd88ae1588ed67cb97f3f20447ba055381700b8c29a5018739e98a1959611c7897136
org.apache.commons_commons-parent-96.spdx.json=435ac8723509804b88c5bf4c0f5ea7b0be36f9fbb28a15fd9620b7a6960b13525a5f6547644a678fa65198b95aacbc88772ac5e7cac279689d3366502f227375
I have tested this with 'mvn' and 'mvn clean install site' using:
***
Use the output from "mvn -version" for each combination you tested.
Windows: ver
Linux: uname -a
***
Details of changes since 95 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/96-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/96-RC1/site/changes.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/96-RC1/site/index.html
(Note some *relative* links are broken and the 96 directories are
not yet created - these will be OK once the site is deployed.)
*** JApiCmp Report (compared to 95):
https://dist.apache.org/repos/dist/dev/commons/parent/96-RC1/site/japicmp.html
***
Note that the above report notes several errors.
These are considered OK for the reasons stated below.
These exceptions are also noted in the Changes and Release Notes.
Errors reported:
- methods added to interface: OK because that does not affect
binary compatibility.
- etc.
***
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/parent/96-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 530AA5F25C25011F)
The following is intended as a helper and refresher for reviewers.
Validating a release candidate
==============================
These guidelines are NOT complete.
Requirements: Git, Java, and Maven.
You can validate a release from a release candidate (RC) tag as follows.
1a) Download and decompress the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/96-RC1/source
1b) Check out the RC tag from git (optional)
This is optional, as a reviewer must at least check source distributions.
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-96-RC1 commons-parent-96-RC1
cd commons-parent-96-RC1
2) Checking the build
All components should include a default Maven goal, such that you can
run 'mvn' from the command line by itself.
2) Check Apache licenses
This step is not required if the site includes a RAT report page,
which you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn apache-rat:check
3) Check binary compatibility
This step is not required if the site includes a JApiCmp report page,
which you then must check.
This check should be included in the default Maven build, but you can
check it with:
mvn verify -DskipTests -P japicmp japicmp:cmp
4) Build the package
This check should be included in the default Maven build, but you can
check it with:
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
4b) Check reproducibility
To check that a build is reproducible, run:
mvn clean verify artifact:compare -DskipTests
-Dreference.repo=https://repository.apache.org/content/repositories/staging/
'-Dbuildinfo.ignore=*/*.spdx.json'
Note that this excludes SPDX files from the check.
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: [email protected]
For additional commands, e-mail: [email protected]
