Arg,m the site's download link is wrong, fixing... Gary On Wed, Jan 22, 2025 at 8:10 AM Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > Pool 2.12.0 was released, so I would like to release Apache Commons > Pool 2.12.1. > > *The difference from RC1 to RC2 is that the source zip and tar files > include the whole 'src' folder.* > > Apache Commons Pool 2.12.1 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/pool/2.12.1-RC2 > (svn revision 74363) > > The Git tag commons-pool-2.12.1-RC2 commit for this RC is > dfd934fa8c0e9a04446c0430ac522fab9e13efad which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=dfd934fa8c0e9a04446c0430ac522fab9e13efad > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-pool.git > --branch commons-pool-2.12.1-RC2 commons-pool-2.12.1-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1805/org/apache/commons/commons-pool2/2.12.1/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Wed Jan 22 13:03:51 UTC 2025 > commons-pool2-2.12.1-bin.tar.gz=efe5779422c8c3fe3c587569cdd8406c127339c6ee08896738dd16283b6696612616863d235a735316ba15bb46e68a8ef4a3b2afcda8dcb73e9cff429338c39f > commons-pool2-2.12.1-bin.zip=ac1afb5aecac0b14210cec4bc7c35ebb3180e173419b8e2856bb00800891624f71442a1da9a087f553a85fe33612aeecd0ce1da4e81fa5d07f41244c733feb43 > commons-pool2-2.12.1-bom.json=365460af3c2bf33eec17604e5b41bb98333eed8a9699f5335546f66938b3fefe8262e6c74cfbac4ab99b22643e9077addd070da79ee8728e99f5bea226621431 > commons-pool2-2.12.1-bom.xml=97fb9114ba6c507f094fa8bc96f34a314ff68320d7113634e21e2687be8b13ee053bbf3b8da83de3f6ba5f1366398ce8f8b18b5e253e329f0a9174bd54da3f96 > commons-pool2-2.12.1-javadoc.jar=19ef73fca7d45c52d6360de022fadcfec063cb0f7844d46cedca91d54c979e8efbb828c12289f5c5274addcd460f85d882794b174efd4e1e5e559e3aae4f00a6 > commons-pool2-2.12.1-sources.jar=fc448f0d5c1e61efd472b8a7f286cd0897a765a968577bc1fa9baa41a34e630aaa34b615dd3f5d73b40432a13322bb5cf284ed50404294457bc59a7f73322458 > commons-pool2-2.12.1-src.tar.gz=64f492b1105f553e27693c22498713f22fad222b4f18c4fa87f210d5d328b76dd38fbf3124ee44891caf9bfcbe9c380c42126fac2c98d9b7153594febcb19996 > commons-pool2-2.12.1-src.zip=fd02bfd00fef115ab2499cbb06e4d0f384d7bfe35287c5ecabb7e8b4c03db22b74f1927247f340d6b50eda490230f4fb2ec8743e307db0306571fb9bd7457bfb > commons-pool2-2.12.1-test-sources.jar=6bb0541fcdc9fe997605d87779461a0f639542ee8eb1e75b730decadf84a4046b5b4b0fd1e0275cc2866fa31458b528ec701a3ab24b69959fa093e0a430ba5d9 > commons-pool2-2.12.1-tests.jar=3b2ad4d0558a6d7d405b146a9cf623469a9e80deb83b7998165e52f5e967fc1aa9b5228fe7f19960f0752e4a509726d328a31127989da9567b13dc4d334f745c > org.apache.commons_commons-pool2-2.12.1.spdx.json=4e63a1cd7709b2b2e3f55232f60cb1a68fa72d697e13f2ef93bc4c5e9dfcf6cadcb48dac79b9d31d686e8d517a457d9322d3f77d583256b26a48dfcd7cfb4d49 > > > > I have tested this with > - mvn > - mvn -e -V -P release -P test-deploy -P jacoco -P japicmp clean > package site deploy > - mvn clean verify artifact:compare -DskipTests > -Dreference.repo=https://repository.apache.org/content/repositories/staging/ > '-Dbuildinfo.ignore=*/*.spdx.json'\ > > Using: > > openjdk version "21.0.5" 2024-10-15 > OpenJDK Runtime Environment Homebrew (build 21.0.5) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.5, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec > Java version: 21.0.5, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.5/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.2", arch: "aarch64", family: "mac" > > Darwin ****.local 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec 6 > 19:03:40 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 arm64 > Docker version 27.3.1, build ce12230 > > > Details of changes since 2.12.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/pool/2.12.1-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/pool/2.12.1-RC2/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/pool/2.12.1-RC2/site/index.html > (note some *relative* links are broken and the 2.12.1 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.12.0): > > https://dist.apache.org/repos/dist/dev/commons/pool/2.12.1-RC2/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/pool/2.12.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 86fdc7e2a11262cb) > > 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.12.1-RC2/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must check source distributions as a minimum. > > git clone https://gitbox.apache.org/repos/asf/commons-pool.git > --branch commons-pool-2.12.1-RC2 commons-pool-2.12.1-RC2 > cd commons-pool-2.12.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: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
