My +1 Gary
On Sat, Nov 23, 2024, 5:47 PM Gary Gregory <garydgreg...@gmail.com> wrote: > We have fixed a few bugs and added enhancements since Apache Commons > DBCP 2.12.0 was released, so I would like to release Apache Commons > DBCP 2.13.0. > > Apache Commons DBCP 2.13.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/dbcp/2.13.0-RC1 > (svn revision 73223) > > The Git tag commons-dbcp-2.13.0-RC1 commit for this RC is > 3cccba8e127cf55a4a30c5056e0bb9ec09446fd7 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-dbcp.git;a=commit;h=3cccba8e127cf55a4a30c5056e0bb9ec09446fd7 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-dbcp.git > --branch <https://gitbox.apache.org/repos/asf/commons-dbcp.git--branch> > commons-dbcp-2.13.0-RC1 commons-dbcp-2.13.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1788/org/apache/commons/commons-dbcp2/2.13.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sat Nov 23 22:41:23 UTC 2024 > Apache\ Commons\ > > DBCP-2.13.0.spdx.rdf.xml=99f6d4c9c26601360a094ff5f3f8774536762cc2173de8d8f0af762031d752a8621e84e52c2719b390ec3c033ca02d2c216cf5928632c603cbb767b226d40b18 > > commons-dbcp2-2.13.0-bin.tar.gz=992fa1fe1e562bba4417a8236d8c638ce11655323f860012174c5a095eb4adde159f8c576225077a6ac23e56a7ec168492b8324e9ff98f4f5679d49e48ded0f9 > > commons-dbcp2-2.13.0-bin.zip=b6c4769b10c02207b44bd31b5c5b84dd296325a7c650aa88f7ab708a735b02deaf8f3ee2317ab4fe25d8eb88731a3059ad99a368d1f1fde9ea18e7551feb83a5 > > commons-dbcp2-2.13.0-bom.json=371677872ed8620cf20ecfaad80563cc5a0385704b850ca8f9a5f309435cf37fc841466d3a13d16733985c2e8407c0f872cc700d8084adb1c6181a8dec4d3144 > > commons-dbcp2-2.13.0-bom.xml=7965771f69e3dcbac1b07e1d1f0f7e0375933cdde09d60863f983ac9350c1af14a5162a178c036052d2ccae7b2353e5f05b11c42dbf264a9ccdd124cddf02ec7 > > commons-dbcp2-2.13.0-javadoc.jar=224b2b2fbe0459982f718a22b22b32f446eed77d69f1478aee93698927caaafff77512464773625170b641a09fdac4dc5b40079939c585c6cadb868f407803c2 > > commons-dbcp2-2.13.0-sources.jar=3e06e23113d1f99f4534d25fa64c6f8a04e91f90ba1e36a8ae783b710b1ef5590c68401dab4216aa6e7412158366982d65d04897ac2532c226d8401067b20ab2 > > commons-dbcp2-2.13.0-src.tar.gz=acbc212e38a9b19bc749ab9245f5231a5212304d003320b0f883c4a31f27535da694cd3b9e82d837c63c7c4811b4f001aee08c97fa553bb7160671e797260918 > > commons-dbcp2-2.13.0-src.zip=afc92227115b5309cd8a5fbc7e0745acaa6cbb29230996cc6ef1464429ec0fc492ad975d3ee1f035ec4f45082d1661a738852100435fba4cf46f1fd801d765a5 > > commons-dbcp2-2.13.0-test-sources.jar=5fb371ca16c3b123e8338b2a3781ee60e20943e29048e209884ee01b0e576f4e03d64667d12349b11f1e1e4e408725473a928348091e8e023ac5d058f2653d6a > > commons-dbcp2-2.13.0-tests.jar=7a5c72f4bbbfca7e4fb810b9f6665f33417ab9be40f1fad78af2feec21ccde5d1f7a20b6d2ad3a159880722d59092b31ea3e6901f7e8ef24e5417a243b00a05d > > > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy > -P jacoco -P japicmp clean package site deploy' 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: /usr/local/Cellar/maven/3.9.9/libexec > Java version: 21.0.5, vendor: Homebrew, runtime: > /usr/local/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.1.1", arch: "x86_64", family: "mac" > > Darwin **** 24.1.0 Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:27 > PDT 2024; root:xnu-11215.41.3~2/RELEASE_X86_64 x86_64 > > > Details of changes since 2.12.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/dbcp/2.13.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/dbcp/2.13.0-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/dbcp/2.13.0-RC1/site/index.html > (note some *relative* links are broken and the 2.13.0 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/dbcp/2.13.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/dbcp/2.13.0-RC1/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, Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1a) Clone and checkout the RC tag > > git clone https://gitbox.apache.org/repos/asf/commons-dbcp.git > --branch commons-dbcp-2.13.0-RC1 commons-dbcp-2.13.0-RC1 > cd commons-dbcp-2.13.0-RC1 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/dbcp/2.13.0-RC1/source > > 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 > > Note that the project reports are created for each module. > Modules can be accessed using the 'Project Modules' link under > the 'Project Information' menu (see <path-to-site>/modules.html). > > -the end- >
