[LAZY][VOTE] Release Apache Commons Release Plugin 1.9.2 based on RC1

We have fixed a few bugs and added enhancements since the release of
Apache Commons Release Plugin 1.9.1, so I would like to release Apache
Commons Release Plugin 1.9.2.

Apache Commons Release Plugin 1.9.2 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.2-RC1
(svn revision 82090)

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

Maven artifacts are here:
    https://repository.apache.org/content/repositories/orgapachecommons-1914/org/apache/commons/commons-release-plugin/1.9.2/

These are the artifacts and their hashes:

#Release SHA-512s
#Sun Jan 25 15:09:25 UTC 2026
commons-release-plugin-1.9.2-bin.tar.gz=81b5171ad8699005ddcceb245ca8bb153fb332596feebfd68c3d5007229d1f96e9313aabfea2faf9c0e86cca9398d668d2de6374eff18c46c74ac06895e02b03
commons-release-plugin-1.9.2-bin.zip=c70561bfd66f3fd3fd003fca95f1f68b304cd9f11a4a7c2255426a8427e753df16496bab0aa481a76618c16a2484faf0fa241e9e466535ba589e5d8d1de63fee
commons-release-plugin-1.9.2-bom.json=eecbe957cce0672478f0427adca339300b4014d4b69a5bbb3744269fb61f11f863a68b3f32ee6f32cac56bfb96050891c3b806bf99d872621b5a586550710261
commons-release-plugin-1.9.2-bom.xml=615b2ad88454d044925ae04791ddf7524e21fb6228a92946fa891f06cef097576fce2b6e1f6992ac149764e66271584e2318cc40ac733fe7a947d206cbb3213e
commons-release-plugin-1.9.2-javadoc.jar=a8b80152be291eaeddd44aaa44124ed1eb7d6ad9b1f4d59fed2075c07f0d8b20e1efbba14631c7787692283df038e4ae85c4050d3da3e727897a2fce73cd9e11
commons-release-plugin-1.9.2-sources.jar=fc930225695694b7600f62bf0c2fa9e4bf5622433b7d6d1ddd9bf6b5dd72ce7e4310589dd3a969c748132101ec6e96b822eb4bb8ea65882f5d0508309e91edbf
commons-release-plugin-1.9.2-src.tar.gz=6a933a8d319c96d3a9eef17de753bbcb7b66a7b6536a530454e13252f699fd3cacf01bdcee14d8d9a10448ee85b37a23883d7fa29aa40c646e83f6b88ffa3c80
commons-release-plugin-1.9.2-src.zip=9626dd4cba700cafa56bc6f9addf0fba70a49dc875a3457c15df3007c319c9600123788d4896537a7c8b53271427c7a1dd7468c1dfb64345d015998b6f97e745
commons-release-plugin-1.9.2-test-sources.jar=e7eff2ce867d8df32f5526e9c8aa88ba03990cf44d6036efbc7ffc51f1564cd27030b69ecbe57f105c3a440c313a5854dcf11157d20224faafac1a9814b1dc36
commons-release-plugin-1.9.2-tests.jar=2e347e39e2f05d27aba568040c3c998d22c20d9136f148bc9467510bd8d33e05b31195526df3a4c7d0311a1c7e00b37050033f3b80f365be9d72d3480f9c8efe
org.apache.commons_commons-release-plugin-1.9.2.spdx.json=c6743f4198f7bc170a2be138017f6ffaa225a104f24b934d1fd2128c196a36b0181627604d3d08533d1b6a69548109b7ddf9bd76638b6f8e7b756a9d85c1e333


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.2", arch: "aarch64", family: "mac"

Darwin Garys-MacBook-Pro.local 25.2.0 Darwin Kernel Version 25.2.0:
Tue Nov 18 21:09:56 PST 2025;
root:xnu-12377.61.12~1/RELEASE_ARM64_T6041 arm64

Docker version 29.1.3, build f52814d


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

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

JApiCmp Report (compared to 1.9.1):
    No report for this internal component.

RAT Report:
    https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.2-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/release-plugin/1.9.2-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-release-plugin.git
--branch commons-release-plugin-1.9.2-RC1
commons-release-plugin-1.9.2-RC1
cd commons-release-plugin-1.9.2-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-