[LAZY][VOTE] Release Apache Commons Parent 97 based on RC1

Gary Gregory <[email protected]>
Newsgroups gmane.comp.jakarta.commons.devel
Message-ID <CACZkXPw+W=kW2o5KzjCvaGx7wtp3sEtNEBDphjxEmfzycuWUaQ@mail.gmail.com>
We have fixed a few bugs and added enhancements since the release of
Apache Commons Parent 96, so I would like to release Apache Commons
Parent 97.

Apache Commons Parent 97 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/parent/97-RC1 (svn
revision 82645)

The Git tag commons-parent-97-RC1 commit for this RC is
e47e665a43a8d864bd18d387f75c5a72d2170628, which you can browse here:
    https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=e47e665a43a8d864bd18d387f75c5a72d2170628
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-97-RC1 commons-parent-97-RC1

Maven artifacts are here:
    https://repository.apache.org/content/repositories/orgapachecommons-1922/org/apache/commons/commons-parent/97/

These are the artifacts and their hashes:

#Release SHA-512s
#Sat Feb 21 12:00:59 UTC 2026
commons-parent-97-bom.json=3e5cdec718a4114c15c6d00c0298ade57f82aeb6a192641c5d5732f5ae0a7760813755aa943ab61a9e40d10c595fb50500f78c769b2bfe131d67c6693a45cb08
commons-parent-97-bom.xml=3384a22f23b00560d9a64cdbac14a6ed24be3aa63d7cf88b0892d179ee33c7746f8152957de097a9f1b7a7ef8f4977a457898da46e38abeb6f08e677475d552e
commons-parent-97-site.xml=78fbbc6f0f79a0b7c86f7b298675fba49f01f44f08b2211e41a727835c38c4e32e33fb20cf39284ad33afb427116e6a667888f50f87b5f98d64c23788bb7fd3a
commons-parent-97-src.tar.gz=fbc2839982c233914749bfe5b6984c96c6e3d2abcb31e9f679b1966953944b0c3b3b7ee0007174910d98ee820549e1b461ecea1f3ae80eadb098869d0a2bd84d
commons-parent-97-src.zip=771e990bae32bd6f3c07aef89a6c18b58aca6142d81b212af73f036c022ae46f402f6ebfcedef755e61bd542add5cf468e4551494d5539315854e443d7d1120e
org.apache.commons_commons-parent-97.spdx.json=acaafa8de9c120ae7e311eaf190c4cd3e0f9829981abaef76b508477a9bc07e55e080990da3cc45dd4ba019e2246508d9c1c42f62dc03e8e9fa25c28d770f0ac


I have tested this with 'mvn' and 'mvn clean install site' using:

openjdk version "21.0.10" 2026-01-20
OpenJDK Runtime Environment Homebrew (build 21.0.10)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.10, mixed mode, sharing)

Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1)
Maven home: /opt/homebrew/Cellar/maven/3.9.12/libexec
Java version: 21.0.10, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.10/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "26.3", arch: "aarch64", family: "mac"

Darwin Garys-MacBook-Pro.local 25.3.0 Darwin Kernel Version 25.3.0:
Wed Jan 28 20:48:41 PST 2026;
root:xnu-12377.81.4~5/RELEASE_ARM64_T6041 arm64

Docker version 29.2.0, build 0b9d198


Details of changes since 96 are in the release notes:
    https://dist.apache.org/repos/dist/dev/commons/parent/97-RC1/RELEASE-NOTES.txt
    https://dist.apache.org/repos/dist/dev/commons/parent/97-RC1/site/changes.html

Site:
    https://dist.apache.org/repos/dist/dev/commons/parent/97-RC1/site/index.html
    (Note some *relative* links are broken and the 97 directories are
not yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 96):
    https://dist.apache.org/repos/dist/dev/commons/parent/97-RC1/site/japicmp.html
    This report is empty, there is no Java code in this component.

RAT Report:
    https://dist.apache.org/repos/dist/dev/commons/parent/97-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/97-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-97-RC1 commons-parent-97-RC1
cd commons-parent-97-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-
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.