+1 looks good. Thanks a ton
> On May 12, 2024, at 8:33 AM, Gary Gregory <ggreg...@apache.org> wrote: > > [The only difference with RC2 is the release notes text file] > > We have fixed a few bugs and added enhancements since Apache Commons > Logging 1.3.1 was released, so I would like to release Apache Commons > Logging 1.3.2. > > Apache Commons Logging 1.3.2 RC3 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3 > (svn revision 69111) > > The Git tag commons-logging-1.3.2-RC3 commit for this RC is > 51ee80926c25ad32cb50700996edf56ef9bb901b which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=51ee80926c25ad32cb50700996edf56ef9bb901b > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-logging.git > --branch commons-logging-1.3.2-RC3 commons-logging-1.3.2-RC3 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1728/commons-logging/commons-logging/1.3.2/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun May 12 12:28:47 UTC 2024 > commons-logging-1.3.2-adapters.jar=ca7783d5658395a34a1cfdaac0717563d4211cbe331f56a639527edf40824ef47b14bc5b194f329f0119d0ce582bd527f32fa0dd5971fbe6947bc35cdf292de0 > commons-logging-1.3.2-api.jar=c973a826ad20c0c890ed405632320b3fed1d969079205f69a49327cec282d1cc1223fa0b5646a5de84e31a209c060a5ad6614f38c558482c9bbe2ab0a99d54e0 > commons-logging-1.3.2-bin.tar.gz=13fa96d0e119c4e671e17cd391fbbe869642e0c769b6a91ebc29b918c3cd1c173d9e0ac18400d41848b611adbaee2386932121dcef3ab0937a78ecf73dbab4fc > commons-logging-1.3.2-bin.zip=46479bbcdb6c204e97bd006072ce610ac2b0200cb8657b78dfbfa027a293a7746c32ef74bf118eafe0919e81e78ff15354d2124a87a959300e56452a33d0d5b3 > commons-logging-1.3.2-bom.json=140a60c1bc7960ffd0e4eb733efc8733778a0228adeaff2dd4d9ee6ffd7bc4f5eb7f6152b18f3d5c662e4041c56cfcd1d4f103c628a9177d5cb475db463c1aea > commons-logging-1.3.2-bom.xml=0f2e5b2b45ed7d22ea5d03b6641b1518e98cf1ff4b641b475ececfe91ca5ea65877d18a4c647116944e71a55ce68a20dc93c3b1b98faa50d2d5b0d1c22a4ac56 > commons-logging-1.3.2-javadoc.jar=d8635955b27887aecb7ad3956b4a51c3e543ea85f1dd65eb7bdc7bcac2db417d48321a0a09faf6f8a369b818c4a55810c8ae6f298895aa49571291bd49c448f8 > commons-logging-1.3.2-sources.jar=8f83cb0fbdbed75eb0cbac0d53c91bc484e19034640536d376f26706d02427c9db8f64048bf76deaba14f1b4494611755b4cd89830a630f67b43890048a87650 > commons-logging-1.3.2-src.tar.gz=9c3a43d0507c16e08d35052e84326206d3cfbfa7c1cb6e6a9d739e7eada92febe3c332185c42220ce12b68b7b95e0ba8bfdcaa233571eca7ec395663f7a262ea > commons-logging-1.3.2-src.zip=933d741489788ba8287e189f4d4b7840623866ba0d7e689d3e2ddf8038926e8bfd7bfbf327542edf1468cd1cf3307a27dc71c971b423902b53c15bc9c8546ec2 > commons-logging-1.3.2-test-sources.jar=4264e97c1f0fba85280daa9ca62d233c16e0f626c79606a9dd4db6276fc5da2e5dfc7810af7bbb35308a62f707480f25cc89e9f6c25ef935b3c0e6d8569272c7 > commons-logging-1.3.2-tests.jar=fc8a0217379e71e4aee34cfb19eeebf5fab93fb3566eda798ce211adbe46b13e829f89f16665dd613ba31984ef9d78802a9f0b7b1a0a3706b33c7ce3696fc4da > commons-logging_commons-logging-1.3.2.spdx.json=b43a2bcf3b232ba7bbf9c0173e2c1beb4f229dcb6345430d7b67bc4400faf6eb4055b150bed96b44ddb486cbcd68a2f1a7a9a894d416d10c1a37ec3b089a07cb > > I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P > jacoco -P japicmp clean package site deploy' using: > > openjdk version "21.0.3" 2024-04-16 > OpenJDK Runtime Environment Homebrew (build 21.0.3) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.3, mixed mode, sharing) > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /usr/local/Cellar/maven/3.9.6/libexec > Java version: 21.0.3, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk/21.0.3/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac" > > Darwin **** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05 > PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64 > > Details of changes since 1.3.1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/site/index.html > (note some *relative* links are broken and the 1.3.2 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.3.1): > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/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) > > 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. > > 1a) Clone and checkout the RC tag > > git clone https://gitbox.apache.org/repos/asf/commons-logging.git > --branch commons-logging-1.3.2-RC3 commons-logging-1.3.2-RC3 > cd commons-logging-1.3.2-RC3 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.2-RC3/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 > > -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
