[VOTE] Release Apache Commons Pool 2.13.1 based on RC1

We have fixed a regression since the release of Apache Commons Pool
2.13.0, so I would like to release Apache Commons Pool 2.13.1.

Apache Commons Pool 2.13.1 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/pool/2.13.1-RC1
(svn revision 81557)

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

Maven artifacts are here:
    https://repository.apache.org/content/repositories/orgapachecommons-1893/org/apache/commons/commons-pool2/2.13.1/

These are the artifacts and their hashes:

#Release SHA-512s
#Mon Dec 29 21:37:18 UTC 2025
commons-pool2-2.13.1-bin.tar.gz=64cf81709e5b85814e657899f8e84d7886922c6b9b93ec74deda5379dfb3cda446a87bf30c5feecf06beb9c5f0390c9e74269dc40e1226072724c343a236e4b6
commons-pool2-2.13.1-bin.zip=f46281fe6c9339fda56c886f118684bb9b1059f02403dae4b857345bd3443bd7ee9e41475f66d08caab6f006c069207530a894e3930e6f9d590c740616196d82
commons-pool2-2.13.1-bom.json=f6ec8eb4c107dfd837327a7a49336d6c0ef9db88e84da91ab9f0a3bfde7f934712c891bf37a3b872af4e922a7a13b4e7abb1407f9f4a41ac69d9f332f9330ade
commons-pool2-2.13.1-bom.xml=fcc75c2cf0a167db8f3210ce4d0b7234131c891a181b25aaecac7becc572507c4e92a77fcc92ff780723729d000ce2e3d0dd8ce597d11abd9a000d0cf6fb3211
commons-pool2-2.13.1-javadoc.jar=67bb5985e0117758062ed64e2684d01a36bb8dbec6104b616823265753a0c15bdd1203e93eb713d0a5cd5c74c704ef263954ca4ffed36842488c996fc762e248
commons-pool2-2.13.1-sources.jar=8b8bfbfe78d21e03c68094daf5a287740039bdd804716799fb1cef1020489971a8e792f7dd651ca04e234dbd1dac90c17f6d5cefe5014cd7e4acc4247371a8d2
commons-pool2-2.13.1-src.tar.gz=3d36c62e9be701888330be389b58848a17d8fa576b3933716d4206187180babc7eb9fa6bf06947151f626a1df88f83ca8fc45f06e460d8925aeace59cd0e037a
commons-pool2-2.13.1-src.zip=d7d2e7556bf58d85228e8ec3f639d969d99abb0d7758d92d05a89a85710629d67136ea32483c5d71293aeb9cc97605ab998e83b777d39a2c802929e3b1953315
commons-pool2-2.13.1-test-sources.jar=4540d6d69e2fa213a6e99ef7b1f9e399ce21359bf17a36566a37cd9f546bfe8eb9aa9f9e5db7fbd8530791f80042c4f346b1cffea3c9cb90c57e59e6f62a38b1
commons-pool2-2.13.1-tests.jar=fae40cd2c96a949bbc8259f1a5c11ff5d5f16b7ccde66be0b7c4661ce40af96d523caa83680c58d4f40301031bff6891e0dede2ed1f43894fdb2d1137f5d68f0
org.apache.commons_commons-pool2-2.13.1.spdx.json=b9b1809b768b60fb3305029ea2edfbae4fe11bfe17bd674d96e06f550b49ac59afac6ce06692bff48f908030f7fef1235a04a4b8ed61b89ba858eb5ce3033aec


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

openjdk version "17.0.17" 2025-10-21
OpenJDK Runtime Environment Homebrew (build 17.0.17+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.17+0, mixed mode, sharing)

Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1)
Maven home: /opt/homebrew/Cellar/maven/3.9.12/libexec
Java version: 17.0.17, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@17/17.0.17/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 ****.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 2.13.0 are in the release notes:
    https://dist.apache.org/repos/dist/dev/commons/pool/2.13.1-RC1/RELEASE-NOTES.txt
    https://dist.apache.org/repos/dist/dev/commons/pool/2.13.1-RC1/site/changes.html

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

JApiCmp Report (compared to 2.13.0):
    https://dist.apache.org/repos/dist/dev/commons/pool/2.13.1-RC1/site/japicmp.html

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