+1 builds all good, signatures and site good. Cheers, -Rob
> On Jun 30, 2024, at 2:57 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed a few bugs since Apache Commons Logging 1.3.2 was > released, so I would like to release Apache Commons Logging 1.3.3. > > Apache Commons Logging 1.3.3 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.3-RC1 > (svn revision 70063) > > The Git tag commons-logging-1.3.3-RC1 commit for this RC is > 894cdbd50c560e2022cccd16fa766607c79b0f07 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=894cdbd50c560e2022cccd16fa766607c79b0f07 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-logging.git > --branch commons-logging-1.3.3-RC1 commons-logging-1.3.3-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1752/commons-logging/commons-logging/1.3.3/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Jun 30 18:51:30 UTC 2024 > commons-logging-1.3.3-adapters.jar=20a571986f628c89d0ee3c0967a64ccc823dc5e1384ca5c1fc5678c97a8a56694559d7636fc8849faa6ad5f980b8ca1051f4ffdeeb8ae4abd344d2085a4dd6f3 > commons-logging-1.3.3-api.jar=ab3ea420570f2e976586b9d0fa7531e9b39d13d5fd61b2c73fd84012adbe4ff9ba97fac7e65dc4ff0f75d01488306ce2ffc23899f8f7cdebcb9b76e38d4ae878 > commons-logging-1.3.3-bin.tar.gz=df0817ebc2ffbeb49d3aca74621184972957930b8399c44ac5bbfe2e7ccdd8e851abcf98039ff4507bb92bd1d555a66f51827b9be05c1942baeef40586c1ec75 > commons-logging-1.3.3-bin.zip=fe346324ffadd429f629af29dea93bd0259cff23bdcee7fb870f1802faebef0161caf3d0b7052f628d42deaf3b9b4cb7d9a5566dca3e76ca8df8ec325bf46933 > commons-logging-1.3.3-bom.json=abf83105c45eac77a7a123173296ba8ecd791a911555279b2c5c6295acd27f5c51b0998fd738df2ac42bc8050ff07329ef336a2bc900d0a0fe07f22bc2973f3b > commons-logging-1.3.3-bom.xml=a8ffc934c7a0a8c7f8b0d07e49a24ce6f4d378d2d3035053c90ac9ad67b965e700a5544a1d0a5d758015da80434f7ca3b1adcc09aebeee6a55f95fab7dc425c0 > commons-logging-1.3.3-javadoc.jar=adb36fee51cd7996a91e89205a3fcca36a98d16439f154b39ee9f20195b69b2916416beea6d43027737a10e0ad47e5e9862460212ca1955eeaf9c20c616d6e60 > commons-logging-1.3.3-sources.jar=2bf1bf6d0906abf49ba632fd88396c5e48f3c6bcd6a80abe0c8644714001f33e302a0a5de913e19faf91fde6be856193f759e45b5917a4f6dc1ecef1a793b88f > commons-logging-1.3.3-src.tar.gz=d7fc6a07026218f87e95046d756638e690087c5ad186f84b0846c5339178f301f71d18a36d8a17321b637c0660af66377eccd0ff4e34876c53b451488e89faed > commons-logging-1.3.3-src.zip=df3dab9d077c9ae8fbde21d6893163e2cafc7ac1dc8905ef503fe7068b9a02a52e2f9586ae4ffcda10f4e64c76ae8aa7dd5f1208e4850d03ae609487633e9d79 > commons-logging-1.3.3-test-sources.jar=3907ab46c4dc04df12c0169f20ae67e06233a6c714389d36df4a0ab40ea9bfe098029518e586623a43f4a0601b793dd168bfcc605781117a71dc86cc06f2b875 > commons-logging-1.3.3-tests.jar=7cc9d2f3f312b708fbfaffc7de5f1ce17e69b4f1ff21eaaa79e1468c475fe834f54ce2570f39c16ddd1df3f2a23fe5c44f8258ef4c294d94fcd4fa6d54b81d18 > commons-logging_commons-logging-1.3.3.spdx.json=360eee382740de020389e2f63d5c21294a74beee9445b40e2c0acbf9ec5db7d17a58ec6a3e2944d5b1a4440e13c46ebfbd885e38e5bb27bb1e8ca5b2bf18c325 > > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy > -P jacoco -P japicmp clean package site deploy' using: > > openjdk version "17.0.11" 2024-04-16 > OpenJDK Runtime Environment Homebrew (build 17.0.11+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing) > > Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) > Maven home: /usr/local/Cellar/maven/3.9.8/libexec > Java version: 17.0.11, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac" > > Darwin **** 23.5.0 Darwin Kernel Version 23.5.0: Wed May 1 20:09:52 > PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64 > > Details of changes since 1.3.2 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.3-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.3-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.3-RC1/site/index.html > (note some *relative* links are broken and the 1.3.3 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.3.2): > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.3-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.3-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) > > 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.3-RC1 commons-logging-1.3.3-RC1 > cd commons-logging-1.3.3-RC1 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.3-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 > > -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
