We have fixed a few bugs and added enhancements since the release of
Apache Commons Pool 2.12.1, so I would like to release Apache Commons
Pool 2.13.0.

[Note: I removed my local Maven repo before deploying]

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

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

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

These are the artifacts and their hashes:

#Release SHA-512s
#Sat Dec 06 12:50:59 UTC 2025
commons-pool2-2.13.0-bin.tar.gz=fd532eb542bd0ae3bae707d6583cb16b2c052917cd564cd91d6c3c3fd9bf511d48f1fe6e6ea7de43e1af54064ce34ec31355ab1176814b1e864c230c7702d443
commons-pool2-2.13.0-bin.zip=cbae1865c51f9a696fec517aede7b01c622e277f28381a8fe675695010838cc471a00a072613fc61f22daebd1d8bc84b81d79638a146bba576680490678d76f8
commons-pool2-2.13.0-bom.json=b43e9cf3966d558006526c927aed2781e8cb5971aa2e70be62dd8880cd1bd8fb6129281941d8d022e65adcef5aa75ad90f530b2e59018d5e23ba067fc020ec95
commons-pool2-2.13.0-bom.xml=af72731a8723b5bbe543a34a308da5805f36c5c2cb0493a59f3051ad63636457899c52d162e5db6c92202370883160bcdb7bcedc83cae082a85aca4e5b456b44
commons-pool2-2.13.0-javadoc.jar=728bc0ad3e71244b9cc3c2dc48c35073291dda672dcb0fc60127bc54b0670488706a260e34c6db6ebb7cf5de3732d6dfdc56d336aca297d6ed7e41753f614b66
commons-pool2-2.13.0-sources.jar=33e685460ef7a024a5eaef942d470f5666aa557669a76f916d6d0277bc544f56fa22697ec57a1925e30a3c9c968e695383266adb9ef57a5931efe9c3f4948685
commons-pool2-2.13.0-src.tar.gz=9a94411795c1f4a26037062d3bf05f120f1b6552aa3c937836949a34787c70f93ef4461ec57182cea2db77a1cad9c495d756f38cca02fb09e8a2a90740068de1
commons-pool2-2.13.0-src.zip=3011c104748d53b556dd2e1651fa9cfdd62add70ee84fc53c0830e19e187ff53d5e8a21e6db8af040d3ee1d1c8ed3a851cc6ff5e84eb7ea56de040822a377ad1
commons-pool2-2.13.0-test-sources.jar=51ae7523b811998fb011ff9d35296618818c1c12a62469267d98f1241bfd65bcd627424cce0eb3492a502c9f2401852711e2a647d293431337a831d254caffb8
commons-pool2-2.13.0-tests.jar=1b848069b3fe2349bfcd92414665798bf9fba18f94890bee0e2e7478518cff632dabd1b1bf35f749af0fd6361b77f59b11be97b69bcb6d5ac806679573259949
org.apache.commons_commons-pool2-2.13.0.spdx.json=6b0de238403f36bb608e3309196a10ba43ccc382f117ba31c282f861e0ff2c8fbb1686dc7fdf0b8a08cb19b15b666fe8a22c3c78a02e62f6113843ec8d57ddb1


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

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

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

Darwin Garys-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0:
Wed Oct 15 21:12:15 PDT 2025;
root:xnu-11417.140.69.703.14~1/RELEASE_ARM64_T6041 arm64

Docker version 28.4.0, build d8eb465


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

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

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

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/pool/2.13.0-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.0-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.0-RC1 commons-pool-2.13.0-RC1
cd commons-pool-2.13.0-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]

Reply via email to