+1 to release sigs, hashes, reports all look good. Tested on maven 3.8.7, Ubuntu 24.04.3 LTS openjdk version "11.0.29" openjdk version "17.0.17" openjdk version "21.0.9" openjdk version "25.0.1" openjdk version "1.8.0_472"
Thanks for the RM Phil On Tue, Dec 30, 2025 at 2:28 PM Gary Gregory <[email protected]> wrote: > We have fixed a regression bug 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 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/pool/2.13.1-RC2 > (svn revision 81576) > > The Git tag commons-pool-2.13.1-RC2 commit for this RC is > 33078499af82dc1bdef3680916fd0a5b9322bab3, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=33078499af82dc1bdef3680916fd0a5b9322bab3 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-pool.git > --branch <https://gitbox.apache.org/repos/asf/commons-pool.git--branch> > commons-pool-2.13.1-RC2 commons-pool-2.13.1-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1896/org/apache/commons/commons-pool2/2.13.1/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Tue Dec 30 19:02:57 UTC 2025 > > commons-pool2-2.13.1-bin.tar.gz=98afb2f67245b65039fb2cbe58dd0e1b1afbc55164dc010948a2a5d72a814e71fbf1c52e88859f812baa758fd12b17c90e86c266204a0d1a0e6e772d19624c5f > > commons-pool2-2.13.1-bin.zip=5929738cba8655891c5ed6afb15d61543ba362f61dbd6fcfe44a1fa7d3b93a8c90ff1e5fa4652e63c02b41febe60122ea8e5ead9ccec12bf3342669384a123c3 > > commons-pool2-2.13.1-bom.json=f6ec8eb4c107dfd837327a7a49336d6c0ef9db88e84da91ab9f0a3bfde7f934712c891bf37a3b872af4e922a7a13b4e7abb1407f9f4a41ac69d9f332f9330ade > > commons-pool2-2.13.1-bom.xml=fcc75c2cf0a167db8f3210ce4d0b7234131c891a181b25aaecac7becc572507c4e92a77fcc92ff780723729d000ce2e3d0dd8ce597d11abd9a000d0cf6fb3211 > > commons-pool2-2.13.1-javadoc.jar=44f8faba4c7ae6c714aa219af1aa25aee19d010ceab93a3841ddd021c93755d2c096a23ef265ad49e258b9baa610976d3a8add36c15ec3e285a8cef6d0d5b842 > > commons-pool2-2.13.1-sources.jar=9e385aec9d11e038ada304d011bbe68717409a56cd62384c226fa61ae66cf2ebdea7213a0c387f6b2f7231118be9cf6b1aee92a4c62c7e286e27f1c9c1fcdf4d > > commons-pool2-2.13.1-src.tar.gz=c4b35cc4e042a17d608b853d717ec920cefd91a30edb4b0ff3c776b67b8222dc24d88cd349e891ca349256551947f2248766554bdc6ca5df8567e49a95232277 > > commons-pool2-2.13.1-src.zip=9fbf313dd472a690be36a4418f024a942ea48bbe1a5c83593b4659362c1b6cce7750a37ba77c3615e85110bf46d3afc3aed11df9a2e8462376529468683611c7 > > commons-pool2-2.13.1-test-sources.jar=e0a594cee8ea3c273d9ae7a7a06b92204d7e479f3f45ec9558f4f1c2ba89389d0eb16c560da80b9e32c84e61fdf19f7a046c3849a2dcd749e7fd2bab2cc37586 > > commons-pool2-2.13.1-tests.jar=a85561ec57997187d1e4f5755289cfb355cdf616869b29794a3c2ae15bf1c8b03affdef3728878aa5e63bcc6021591aea0d69d21c764c87721d6182d9e2d2060 > > org.apache.commons_commons-pool2-2.13.1.spdx.json=4b8af29c05fd1ba9a395ff86cff027cba26046f55689d381bca267c6800fd36164815a7fe991d3221dece6f22d3595ee0b621c0c9a0e263b49e583810c322a12 > > > 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-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/pool/2.13.1-RC2/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/pool/2.13.1-RC2/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-RC2/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/pool/2.13.1-RC2/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-RC2/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-RC2 commons-pool-2.13.1-RC2 > cd commons-pool-2.13.1-RC2 > > 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] > >
