My +1 Gary
On Fri, Nov 22, 2024 at 10:58 AM Gary Gregory <garydgreg...@gmail.com> wrote: > > We have bumped the Log4j dependency and done some light housekeeping > since Apache Commons Logging 1.3.4 was released, so I would like to > release Apache Commons Logging 1.3.5. > > Apache Commons Logging 1.3.5 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC1 > (svn revision 73212) > > The Git tag commons-logging-1.3.5-RC1 commit for this RC is > 8cd10fae04eefc72496031e4eda3a8fbfb7cc565 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=8cd10fae04eefc72496031e4eda3a8fbfb7cc565 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-logging.git > --branch commons-logging-1.3.5-RC1 commons-logging-1.3.5-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1787/commons-logging/commons-logging/1.3.5/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri Nov 22 15:49:21 UTC 2024 > commons-logging-1.3.5-adapters.jar=5c7ffb800175962218be5efa7241d8142045ae5b9d52f88bbbd88e18bab2a2fca4a9228e8e73a89f54f7b68550d4d6a9432208d62b66b4f2677200ba3e51f3a1 > commons-logging-1.3.5-api.jar=58407266c1a0d0f17931684da25a6cba74ff8b90ab63ac8298be355d1765aecbfdaa0a756a3901b4941e8d51fafe722d53018309e9baba39435b8317ba8ddbbd > commons-logging-1.3.5-bin.tar.gz=827a25438599652bb7eeb9cabe837a002e6186579ef086e57a8f238ebf9b30ba61aec46c611e41146b21de2d70e906051036557d46c3304adec02c771deb9cc9 > commons-logging-1.3.5-bin.zip=189fa9895621dc7edbe55a7753427b2c044abb84a96c9682a59ddb1a5cc58df22a5d1246a8599d8362086c4a374dd5c7eac6ff6bd98c8f7ab4fd723806059ed4 > commons-logging-1.3.5-bom.json=0022a8795471ceaa8a4839137bbfbd547b82e94c092d40089304e1268fe21e0286f7eac28ea3d43a3db3c7a9372f2deeac587e91bc1c2b9f647e7e1034a56fd6 > commons-logging-1.3.5-bom.xml=c78a71568b16120940303823d83847082853621a2cdda7a12a2dfa108cad4953039433c68f6a35f88e57226f41b9a10c1b9f98b14c02771a4a3f92837953ca6c > commons-logging-1.3.5-javadoc.jar=b896011ab32e7944e92916deb8244be7ed5b0843d09e8b22aa4262bd605ae00b68516470307533107d8e82f4cfdc01d92dc5b87377c9589e17bca852e0a05afa > commons-logging-1.3.5-sources.jar=831e75c85979bdf9a433d0f5ad658a4cd5419d74a227596970248bb260af53c87567296c7f8b56ce3d16fe6482845e35b9b30c676da4836e4bf2c36799e8a39d > commons-logging-1.3.5-src.tar.gz=9813774c24b0a0c946e9d0c0137369f78f47a8052ae8b4d8ee946de5e91d31d839173acf14da48a2bc537b41980d3e05b65c38e0e661aeea842ef321c31e1b44 > commons-logging-1.3.5-src.zip=3173a56900fa976d5f3b1305ed0e2b46e8acfec11dc97feb69b8043430304fdeaa9295cfcc396cbbda88d336d157f184b91555f43e52051cc7eb85babf53ba90 > commons-logging-1.3.5-test-sources.jar=2d11793a81118ed21c754d3f4c0005ac38616cc6efb736e8297542bdb8786538a9231f07218bf3981abf656a02f5462e99c586f5e16a13a08d79f3d24bbfc3c2 > commons-logging-1.3.5-tests.jar=6cbc1b6a81c9e4887efa8f66e83b9e06916bb46505bf4822554c67b916a84b09e2b0ba8e1bc860e5050195297087c273c7c583c44d39f61543dd671a2a58b44a > commons-logging_commons-logging-1.3.5.spdx.json=1d84d60c05504afb69daa2e75cd98acdce8b8a356a68c96f38837b5002d918d69112901f24760701bf77c8cd143161e7cbd391a7fefcee53e382b91b5cefbd97 > > > 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.13" 2024-10-15 > OpenJDK Runtime Environment Homebrew (build 17.0.13+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.13+0, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /usr/local/Cellar/maven/3.9.9/libexec > Java version: 17.0.13, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.13/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 1.3.4 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC1/site/index.html > (note some *relative* links are broken and the 1.3.5 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.3.4): > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-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-logging.git > --branch commons-logging-1.3.5-RC1 commons-logging-1.3.5-RC1 > cd commons-logging-1.3.5-RC1 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/logging/1.3.5-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
