+1 Am 25.07.2019 um 16:59 schrieb Gary Gregory:
We have fixed quite a few bugs and added some significant enhancements since Apache Commons Pool 2.6.2 was released, so I would like to release Apache Commons Pool 2.7.0.Apache Commons Pool 2.7.0 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/commons/pool/2.7.0-RC1 (svn revision 35022) The Git tag commons-pool-2.7.0-RC1 commit for this RC is f4455dcb8afaf9ae7054589110f1082a7a8a282c which you can browse here: https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=f4455dcb8afaf9ae7054589110f1082a7a8a282c You may checkout this tag using: git clone https://gitbox.apache.org/repos/asf/commons-pool.git --branch commons-pool-2.7.0-RC1 commons-pool-2.7.0-RC1 Maven artifacts are here: https://repository.apache.org/content/repositories/orgapachecommons-1454/org/apache/commons/commons-pool2/2.7.0/ These are the artifacts and their hashes: #Release SHA-512s #Thu Jul 25 10:43:49 EDT 2019 commons-pool2-2.7.0-bin.tar.gz=5da53ee485b156fe428c18a1131ff762ca672e759ea84aa58d73155fba78ee3ce8421a1cfea6735e041b9770101e3889da4d51ffc30879fd583dc8f961bae1ed commons-pool2-2.7.0-bin.zip=f03f95b45b42e4fdc799974911cc8cba57feca74c3c8eda7ce710c2f8eaaef2329491746397db901c3c3a251b3a2cc524245128a61121c2d1443272baaa1c67e commons-pool2-2.7.0-javadoc.jar=a5a879e421d6063f721c20ccafba60550255b542b6d9cfc226a045a8fa2fb3a1758d61f8efd8f563d63d20ab9b29a966436e589a5f4beb1ea7d19665248fcdf1 commons-pool2-2.7.0-javadoc.jar.asc=003b0f60396671356c72f0203e17522b8ba035a45c7864efc3aa835c49809f73a6e5b7d8bd75c7125306d659a61e283af8e64f4f607920f5bf929ff052e3b2da commons-pool2-2.7.0-sources.jar=22fad51648d23e11d0a881faf1748b9633e8a5b8d0ccc1334554abd6330796254c174405b2fbf6d901ea729e50feb3e0b9d51fb12dc7ab1bce803b26faf1366d commons-pool2-2.7.0-src.tar.gz=2028df7c0306a01406b2f529f55898cc6db00a939731659eb86fc4d890f57bc55dbbf6cee777b406c9bc4c618218c0250b0dae236f8ddde58bcdcabf5afe6755 commons-pool2-2.7.0-src.zip=243ceba67abfcf621c6ceddbf30b52e2b84b453cb722294fb24a7db319f81a4668f9a3ebaf264e50becd50ea5822a82bb75c6303aec0ba57073cd628ea9938b2 commons-pool2-2.7.0-test-sources.jar=95605f34e415ad9c5de2bed7e54ed2b40bdfb2cabfccd23030b0a63362a258b082c798daa5f99ef35e149f8d733aa852449e73e0f91071272b79a52cf13629af commons-pool2-2.7.0-tests.jar=08818d2d106ea1c9b7bf2f6f67cae13c4eaf47fb25100c9285491647ea93cd30d7ed5c8a49907fa0e581d060f073ff5f63612f1b43af2829ee229d64ce2c7f23 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.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T15:00:29-04:00) Maven home: C:\Java\apache-maven-3.6.1\bin\.. Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_221\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" Details of changes since 2.6.2 are in the release notes: https://dist.apache.org/repos/dist/dev/commons/pool/2.7.0-RC1/RELEASE-NOTES.txt https://dist.apache.org/repos/dist/dev/commons/pool/2.7.0-RC1/site/changes-report.html Site: https://dist.apache.org/repos/dist/dev/commons/pool/2.7.0-RC1/site/index.html (note some *relative* links are broken and the 2.7.0 directories are not yet created - these will be OK once the site is deployed.) JApiCmp Report (compared to 2.6.2): https://dist.apache.org/repos/dist/dev/commons/pool/2.7.0-RC1/site/japicmp.html This release adds new default methods to the interface org.apache.commons.pool2.PooledObject which does not break binary compatibility. RAT Report: https://dist.apache.org/repos/dist/dev/commons/pool/2.7.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 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.7.0-RC1 commons-pool-2.7.0-RC1 cd commons-pool-2.7.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 This component uses 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 6) Build the site for a multi-module project mvn site mvn site:stage 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
