We have added two enhancements since Apache Commons Pool 2.9.0 was
released, so I would like to release Apache Commons Pool 2.10.0.
Apache Commons Pool 2.10.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/pool/2.10.0-RC1 (svn
revision 47956)
The Git tag commons-pool-2.10.0-RC1 commit for this RC is
48c289d95c2374ee11e3276a8bcb93b7f99015be which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=48c289d95c2374ee11e3276a8bcb93b7f99015be
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-pool.git --branch
commons-pool-2.10.0-RC1 commons-pool-2.10.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1549/org/apache/commons/commons-pool2/2.10.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Fri May 28 16:51:08 EDT 2021
commons-pool2-2.10.0-bin.tar.gz=850ea4765b913aab37fbafff938568f9c0415ad0add4f4894873a2caeb3286ed6293ee6cd477f39c5b22c52514abca799504cad3b74ed78d7de9550af48fb6e4
commons-pool2-2.10.0-bin.zip=fd411668de81ab686e35901cddd849f6517bdabb7b449d736aee174263184ff2b9da551d4940ecf4ff58168eb86f69b4ce98c4ccc9e5efead9b0bf9a13cb3c0e
commons-pool2-2.10.0-javadoc.jar=4804de4692de627ba3129f01937c4c9ceb85676ec807d12ce99670e341b43a170d2ba7f508389f31b877215d118acdb38a5342d984d981704503fb70501ab8d8
commons-pool2-2.10.0-sources.jar=ab3a8e93d39899be06805f72411dc36da98f1195a5468bae76e14509975dd482287ed41af6469487745b62d4280f50f4890bcaca2e990ae69957ecf66ae81eac
commons-pool2-2.10.0-src.tar.gz=dcfdd6ebfcd40a712cc765d4aa7888674dc7c9c0635ee716471c1c833b8704d182b632c700881cd903a7c58b9d0adfddfde9f9b40acdf143668c18f3fde61ac7
commons-pool2-2.10.0-src.zip=fe4dec5d15b5a8d2ba979548ab0650097789ed3b9009b24aaa6ee7b68deda0cc16b517379b493767ebfcc7a970843b7adc9de02c796401451f30260b46435331
commons-pool2-2.10.0-test-sources.jar=f7d1c5f7bad1b853cd755402bcc1c4c0fcf153897bdac3427e0918f351984bf33a045b813653240ff66d06885b4e933b2154b2bdf0c709b37380bf8998c9a9d0
commons-pool2-2.10.0-tests.jar=37f6dcef0ac12d4bad10e571c43f96129f573678d48b94174fef1f8c745c4c58ae73118f2f60e5a83c70c3580cf6b3185e2d7dc363cdf636482b3cd0c67b4602
I have tested this with 'mvn -V -Prelease -Ptest-deploy -P jacoco -P
japicmp clean package site deploy' using:
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /usr/local/Cellar/maven/3.8.1/libexec
Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
Details of changes since 2.9.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/pool/2.10.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/pool/2.10.0-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/pool/2.10.0-RC1/site/index.html
(note some *relative* links are broken and the 2.10.0 directories are
not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 2.9.0):
https://dist.apache.org/repos/dist/dev/commons/pool/2.10.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/pool/2.10.0-RC1/site/rat-report.html
KEYS:
https://www.apache.org/dist/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 86fdc7e2a11262cb)
For following is intended as a helper and refresher for reviewers.
Validating a release candidate
==============================
These guidelines are NOT complete.
Requirements: Git, Java, Maven.
You can validate a release from a release candidate (RC) tag as follows.
1) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-pool.git --branch
commons-pool-2.10.0-RC1 commons-pool-2.10.0-RC1
cd commons-pool-2.10.0-RC1
2) Check Apache licenses
This step is not required if the site includes a RAT report page which you
then must check.
mvn apache-rat:check
3) Check binary compatibility
Older components still use Apache Clirr:
This step is not required if the site includes a Clirr report page which
you then must check.
mvn clirr:check
Newer components use JApiCmp with the japicmp Maven Profile:
This step is not required if the site includes a JApiCmp report page which
you then must check.
mvn install -DskipTests -P japicmp japicmp:cmp
4) Build the package
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
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-
