[x] +1 Release these artifacts
Build passing on JDK 8, Ubuntu LTS. Site reports look good. The changes report is showing the date as 2020-MM-DD. But I think that can be fixed later in the site. Checked signatures from Maven repo and from the dist area src and bin files. Found no issues. Inspected a couple files from the dist area, NOTICE, LICENSE, general structure, all looking OK too. Cheers Bruno On Tuesday, 28 July 2020, 1:18:21 pm NZST, Gary Gregory <ggreg...@apache.org> wrote: We have fixed one bug and added a few enhancements since Apache Commons Pool 2.8.0 was released, so I would like to release Apache Commons Pool 2.8.1. Apache Commons Pool 2.8.1 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1 (svn revision 40727) The Git tag commons-pool-2.8.1-RC1 commit for this RC is 3fb7df661d521d57297d6aafa2d2d57356ae4adf which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=3fb7df661d521d57297d6aafa2d2d57356ae4adf You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-pool.git --branch commons-pool-2.8.1-RC1 commons-pool-2.8.1-RC1 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1509/org/apache/commons/commons-pool2/2.8.1/ These are the artifacts and their hashes: #Release SHA-512s #Mon Jul 27 21:09:02 EDT 2020 commons-pool2-2.8.1-bin.tar.gz=a2887c27af17691c06c23b6b44f63f71414f460f6bf8788ce15013c8dbd68989df5ca75fd87975c806b4e93d976bdd6d9af2ff824a8127416c2cc303f38a02a9 commons-pool2-2.8.1-bin.zip=3e8b7522572db4234c6ba7879d8920e7590f5c176eceb3bc1cf1dfddf84e1eeee3f0ee12e7e839831b54ecb1ed367d4c67936335adbc13460a8bfe6469765550 commons-pool2-2.8.1-javadoc.jar=7cfdc4f238fdd298dd690823c1d8a2e43629d75851152d369383a7007ebf559e0f231a1d05a027f9476d3dcd16502ee39c818f18176e8fd398d4300948098195 commons-pool2-2.8.1-sources.jar=1d679ec95dcd105eb8b619cbe0755693d15495a19b64609e9ccba7137a5307b2dc7b18276aa26d5af28d90465e925984257d26e7f40870456de26a6c6a84cb95 commons-pool2-2.8.1-src.tar.gz=4cece944ac8b4b1f76bcf78355b3262b043f1a00699da0334fff622a7e5042c5b51defc625c292f1fb228af43fd0608a4c6bdbd083c32d944d7d2c8e89dd106c commons-pool2-2.8.1-src.zip=7351bb17f2144742f145cd936ab10c0e90ef1e568d88637e96a1dc03e60dfca2f9902036b0e58a8790600c03b03da2a62779d1cab5d50bec7f4a1621de2313de commons-pool2-2.8.1-test-sources.jar=0c4c4d7d57bbc1bfa7b6bf6eacf2cbf980e0f88972af6c2fdbdf7f91afdf681c14bb5c58844490562214e898a66da3e022ada29a3fe52556f780c4b08e8ff42c commons-pool2-2.8.1-tests.jar=84a939f018f1a9f0dc28f822144566883d685bfc75f05d072aeef3504cec51f4f92d92fd37fa41c5608505b5001fd04da15b1b81143abf4202d8922ff678ca0f I have tested this with mvn -V -Duser.name=%my_apache_id% -Dcommons.release-plugin.version=%commons.release-plugin.version% -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy using: Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: C:\Java\apache-maven-3.6.3\bin\.. Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_251\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Details of changes since 2.8.0 are in the release notes: https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/site/changes-report.html Site: https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/site/index.html (note some *relative* links are broken and the 2.8.1 directories are not yet created - these will be OK once the site is deployed.) JApiCmp Report (compared to 2.8.0): https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/site/japicmp.html RAT Report: https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-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 that 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.8.1-RC1 commons-pool-2.8.1-RC1 cd commons-pool-2.8.1-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- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
