My +1 Gary
On Thu, Jun 11, 2026 at 8:42 PM Gary Gregory <[email protected]> wrote: > > We have fixed a few bugs and added one enhancement since the release > of Apache Commons Logging 1.3.6, so I would like to release Apache > Commons Logging 1.4.0. > > Apache Commons Logging 1.4.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/logging/1.4.0-RC1 > (svn revision 85184) > > The Git tag commons-logging-1.4.0-RC1 commit for this RC is > ff5ff39e05cd39b5c807b6bf91973524201b3c3e, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=ff5ff39e05cd39b5c807b6bf91973524201b3c3e > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-logging.git > --branch commons-logging-1.4.0-RC1 commons-logging-1.4.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1948/commons-logging/commons-logging/1.4.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Thu Jun 11 20:49:24 UTC 2026 > commons-logging-1.4.0-adapters.jar=31f0095be5b09a62d50141cc602cc9dccfe56709dd7baf969965aa0a08fbd584597327d161f1d843d0f63cc28b6c8de1b6f869a456977355b00d7aa033197f1d > commons-logging-1.4.0-api.jar=6db098619f5681f75cb5c0c386f19902e67630c2db267913f22f5a4c9955f9d173ba888f737628a9d34c6447b32f50c96cc2d786aa5ac7c933a28c94d32f8cc8 > commons-logging-1.4.0-bin.tar.gz=c3de9cf4381cb38e1cf6d753f8326fe8a40307f79a41a982b5225658947c919598baaa5582f1060023c7fbb90714bdd02db4e298b72fb20c47b9c3d452405cee > commons-logging-1.4.0-bin.zip=4db84a9f6c151816c784aa1ed51280257488b2630e35ceaa5d0cb1de0a95ff42460d4cba2336a0c971ef8b02576218a5f2c254282a7f8b23903b1299584ead0b > commons-logging-1.4.0-bom.json=ea275c83b97ac31864be54fc01be19daeedab6dd27015cb87e68a914d0aba2ffec870298f7c2fd0b2105435297a56e3255d575d5a480a0554642461d7fa06605 > commons-logging-1.4.0-bom.xml=df4439fb1104de3ec4699f12eb8967d93b2ef9bb2a29deee3c5ee6415ad3751f0295d78a8207400a56aefb1d8bd19a1fdd7844cab2e8bc1b94c3becd4191c427 > commons-logging-1.4.0-javadoc.jar=acc3e1d0039ec32edc91350071d5e6ec4c34e19178fe7cb012fe4ff3a1500c078106df3180e252ac8f8048fc8b16157dfeea91969022aae030737b8ce4e1b6c3 > commons-logging-1.4.0-sources.jar=62d616de7c392553eb7ff6e9b34bc7738638b0d5a42bf7e7afb37bbdc1696a3917b3e829aefa7682dce656e117bb59d24164e944b1b2f85e3da20ddd1c2355ed > commons-logging-1.4.0-src.tar.gz=92d698301b601b1af76739e445f90f338ceeafe59c5fe6a247e9d4684a967a659d1908e7a211d2616344ddbf3f53433e512e0b160cf6ac9a40ac9b29431dc2a2 > commons-logging-1.4.0-src.zip=f8bf1f19cbeecae1796831ee7417d9561dc60e56dab65554875433eee3d6cceb4c1a458eb88f1f3a604adda932835ff0ce5ab03734fb061b9dd7a97e7c9004e0 > commons-logging-1.4.0-test-sources.jar=f99cac7fb121c7d67df135a3612f2a4bc31c35fdafcdfa212a950e9d89da0b75be39c22ef2e55d9c837aeaa8557746c131b8fb8517781eddbd591932e25de3cf > commons-logging-1.4.0-tests.jar=92275ccb50b53b71100f14be55176246c92b6a1f55ba420683f541419a5312fcf2f23fcd7391b45f5fcdae7a03beafd167378f0e6164f42ee4c78351db9adb3a > commons-logging_commons-logging-1.4.0.spdx.json=ac92c459a4a905b10a3ea97321a45d848c1bfe0c7242d00641d1d22d63152a4a9d9d6f100ac9a5d0a31390de2cdb473d4b9034927d0c3c206e9bad0f31bc4caf > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.11" 2026-04-21 > OpenJDK Runtime Environment Homebrew (build 21.0.11) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.11, mixed mode, sharing) > > Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5) > Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec > Java version: 21.0.11, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.11/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.5.1", arch: "aarch64", family: "mac" > > Darwin ****.local 25.5.0 Darwin Kernel Version 25.5.0: Mon Apr 27 > 20:41:15 PDT 2026; root:xnu-12377.121.6~2/RELEASE_ARM64_T6041 arm64 > > Docker version 29.4.3, build 055a478 > > > Details of changes since 1.3.6 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.4.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/logging/1.4.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.4.0-RC1/site/index.html > (Note some *relative* links are broken and the 1.4.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.3.6): > > https://dist.apache.org/repos/dist/dev/commons/logging/1.4.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.4.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 530AA5F25C25011F) > > The following is intended as a helper and refresher for reviewers. > > Validating a release candidate > ============================== > > These guidelines are NOT complete. > > Requirements: Git, Java, and Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1a) Download and decompress the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.4.0-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must at least check source distributions. > > git clone https://gitbox.apache.org/repos/asf/commons-logging.git > --branch commons-logging-1.4.0-RC1 commons-logging-1.4.0-RC1 > cd commons-logging-1.4.0-RC1 > > 2) Checking the build > > All components should include a default Maven goal, such that you can > run 'mvn' from the command line by itself. > > 2) Check Apache licenses > > This step is not required if the site includes a RAT report page, > which you then must check. > This check should be included in the default Maven build, but you can > check it with: > > mvn apache-rat:check > > 3) Check binary compatibility > > This step is not required if the site includes a JApiCmp report page, > which you then must check. > This check should be included in the default Maven build, but you can > check it with: > > mvn verify -DskipTests -P japicmp japicmp:cmp > > 4) Build the package > > This check should be included in the default Maven build, but you can > check it with: > > 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 > > 4b) Check reproducibility > > To check that a build is reproducible, run: > > mvn clean verify artifact:compare -DskipTests > -Dreference.repo=https://repository.apache.org/content/repositories/staging/ > '-Dbuildinfo.ignore=*/*.spdx.json' > > Note that this excludes SPDX files from the check. > > 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: [email protected] For additional commands, e-mail: [email protected]
