This vote thread passes with the following +1 votes cast: - Arturo Bernal (non-binding) - Bruno P. Kinoshita (binding) - Rob Tompkins (binding) - Gary Gregory (binding)
Thank you all for taking the time to review this release candidate, Gary On Wed, Aug 11, 2021 at 8:26 PM Gary Gregory <garydgreg...@gmail.com> wrote: > > My +1 > > Gary > > On Wed, Aug 11, 2021 at 5:53 PM Rob Tompkins <chtom...@gmail.com> wrote: > > > > +1 signatures good, builds on 8 and 11, rat good reports good. > > > > send it :-) > > > > > On Aug 11, 2021, at 5:45 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > > May I get at least one more PMC review please? > > > > > > Gary > > > > > > On Sun, Aug 8, 2021, 18:12 Gary Gregory <garydgreg...@gmail.com> wrote: > > > > > >> We have fixed a few bugs and added some enhancements since Apache > > >> Commons Pool 2.10.0 was released, so I would like to release Apache > > >> Commons Pool 2.11.0. > > >> > > >> Apache Commons Pool 2.11.0 RC1 is available for review here: > > >> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1 > > >> (svn revision 49387) > > >> > > >> The Git tag commons-pool-2.11.0-RC1 commit for this RC is > > >> b94e8bec1a056e2784799cba51c79bc3b801d4cd which you can browse here: > > >> > > >> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=b94e8bec1a056e2784799cba51c79bc3b801d4cd > > >> 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.11.0-RC1 commons-pool-2.11.0-RC1 > > >> > > >> Maven artifacts are here: > > >> > > >> https://repository.apache.org/content/repositories/orgapachecommons-1560/org/apache/commons/commons-pool2/2.11.0/ > > >> > > >> These are the artifacts and their hashes: > > >> > > >> #Release SHA-512s > > >> #Sun Aug 08 17:25:31 EDT 2021 > > >> > > >> commons-pool2-2.11.0-bin.tar.gz=e3fd5e2841ea5d357b875c2bf669b7f903e0c8914e45bd40ffbfe28ea9fe48a995b0c80a1d4a9e859b8bc9f69c0544701c302bfed6903e5a647a5ae388b17bac > > >> > > >> commons-pool2-2.11.0-bin.zip=a9c500bff6d014e0ee0ab49c410e66c3777c55ae94c4490c3125bd7e0bb92ee55fc8067e7d8ecaecd1ac467c201ef1aae3dc73751bfb9bc94ec620dab7f48862 > > >> > > >> commons-pool2-2.11.0-javadoc.jar=e1c253021b5980bafb4ff11fd2f0dc46752c24d37b6b4b363ddd5ef1c8bd6e70c4b27b0ad95759d2102efb4d3f42128ec248809e11a977a39ebc55f8fd032619 > > >> > > >> commons-pool2-2.11.0-sources.jar=336ae1927ed517c8168ae3c85dd8b84eb45d46288fba3e64b324accbe07f1b8fd44eded3a5f62c36e0280f444a91a6659722e47149c926a8a4ecdf3bb7a6c53e > > >> > > >> commons-pool2-2.11.0-src.tar.gz=1316ed17d3bb11f8fa15733dd79a09c9d117ed2410b2854ce72067fd5ea1ccde5612a2f3246d857d55913ddf81db6c03e94a0d17a05e8bfd11b045c982e3d40a > > >> > > >> commons-pool2-2.11.0-src.zip=30686059d9932f75d413cdb93c6333ccbf432dd7864f3075981d1721ee87642c7b481fe84fd1fd3d075acf469f939ad4a753384177cafcd5bd90af722b0c34bb > > >> > > >> commons-pool2-2.11.0-test-sources.jar=d983d4a97362cc74bdca1987697e482431e2f84ecc8943b8e1c1cc20a82e889b4d2b5aac57708fbafdcaa00a1fb6f135bd94072c7c956f0275d7a925a27396fc > > >> > > >> commons-pool2-2.11.0-tests.jar=62a9b7d5a2f67933d72479efe59974578ed8eaf58a4be449aea6014fe9c0063cb1a7aca974eb45f9e69b4b0b495a01396aedd622a053f8c2d504b6efe64ef61c > > >> > > >> 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.10.0 are in the release notes: > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/RELEASE-NOTES.txt > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/site/changes-report.html > > >> > > >> Site: > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/site/index.html > > >> (note some *relative* links are broken and the 2.11.0 directories > > >> are not yet created - these will be OK once the site is deployed.) > > >> > > >> JApiCmp Report (compared to 2.10.0): > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/site/japicmp.html > > >> > > >> RAT Report: > > >> > > >> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.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.11.0-RC1 commons-pool-2.11.0-RC1 > > >> cd commons-pool-2.11.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- > > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
