This lazy vote thread passes with the following binding vote: - Gary Gregory (ggregory)
TY, Gary On Sat, Jul 26, 2025 at 7:52 AM Gary Gregory <garydgreg...@gmail.com> wrote: > My +1 > > Gary > > > On Wed, Jul 23, 2025 at 6:12 AM Gary Gregory <garydgreg...@gmail.com> > wrote: > >> We have fixed a few bugs since Apache Commons Release Plugin 1.9.0 was >> released, so I would like to release Apache Commons Release Plugin >> 1.9.1. >> >> Apache Commons Release Plugin 1.9.1 RC1 is available for review here: >> >> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.1-RC1 >> (svn revision 78322) >> >> The Git tag commons-release-plugin-1.9.1-RC1 commit for this RC is >> de9b6d4dc6a17f06e6f22f6443d7323a3ac4c164 which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=de9b6d4dc6a17f06e6f22f6443d7323a3ac4c164 >> You may checkout this tag using: >> git clone >> https://gitbox.apache.org/repos/asf/commons-release-plugin.git >> --branch >> <https://gitbox.apache.org/repos/asf/commons-release-plugin.git--branch> >> commons-release-plugin-1.9.1-RC1 >> commons-release-plugin-1.9.1-RC1 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1852/org/apache/commons/commons-release-plugin/1.9.1/ >> >> These are the artifacts and their hashes: >> >> #Release SHA-512s >> #Wed Jul 23 10:07:24 UTC 2025 >> >> commons-release-plugin-1.9.1-bin.tar.gz=37f8caf001b4b96e5e0655b6cea72977e7b1441defdd3e621365e8637624a7b0876e3c7dfd5fc5afa622226db212774e160523dd40f574051e5be70304de0306 >> >> commons-release-plugin-1.9.1-bin.zip=a08ba53a3e9c229fc0d22f262d59ad8d7274386d042e3e48a150b8c0b45d7362e028ade4353a41aece90cba9bb7397e28b099be9ba1d7e2650ffdf67e1445fac >> >> commons-release-plugin-1.9.1-bom.json=3bd31e99b53e8d306e74c72ff3dfb75c6c6dd2c49f0205b9c4dcefedd7410d2ab1ff0265b0e49fad07c85f6a2e897ae5b8476d2de458111d7b21c9285ca32046 >> >> commons-release-plugin-1.9.1-bom.xml=9ddd92d5838adf99b9b7960b09a256e53d6d21b7ecf1d974d5636f0243a24acda6c4428ad14a4279ac2cfec56a71c3c3533c0bc816f15e1d8b31c0481ef28dca >> >> commons-release-plugin-1.9.1-javadoc.jar=63196ab77a3d2a6483e65a57d7137b466a6166a0b42d38142e97512efdaf616b36c9fb3b469a85e164a55cb6d9cf98bf667729350e7a6d468e942a0fc0889e36 >> >> commons-release-plugin-1.9.1-sources.jar=5f9b4e089e84d1d4bb7d45956a037efd9abc3a94e5d9fac7f9056dec7bec994773a6673b8bd28295ab574af09bdb3ed0655fd002ccfc18d40db9ff22abd92b79 >> >> commons-release-plugin-1.9.1-src.tar.gz=216a12a7c8a3205a7a8707186a4b7db328be23131db2b57f7a3b1ebb221c55088cb43f6395a2c87f9ad39057f454e579077e004a8a3479b40d89bfebb360c8e1 >> >> commons-release-plugin-1.9.1-src.zip=3a4256c1c5bba6625fe5eff069a13d6d153b5654e9ee1fc5940903ddcfbdd433793a7851a195446372d0bce3b483dd49d6840ef2635b36d4aac383e4f313ac77 >> >> commons-release-plugin-1.9.1-test-sources.jar=00e5850d5421d5e914a54c75450739a367e793074168bda5e3467244688163e6e680b4237c045a2b1c356f5dbaab716ca7746993818696fe75b4052cdb89969a >> >> commons-release-plugin-1.9.1-tests.jar=ad60b93cb4298ce048e2e0a929e89638a8714bfdfe8cf47cf74608a3005b74b1cebfac2a488724d2a80fa27971dafa1386ecaecb3157157588d8917f7ed7230d >> >> org.apache.commons_commons-release-plugin-1.9.1.spdx.json=f5abacdbf168db249222205bcdbe27f3df5ed70838f65da40a0ad9f1188e6ca5cc221bc450cdc079f3f92742eed44e2a6c5f2e1f126cd36ff03638ef0d5d6738 >> >> >> I have tested this with 'mvn' and 'mvn clean install site' using: >> >> openjdk version "21.0.8" 2025-07-15 >> OpenJDK Runtime Environment Homebrew (build 21.0.8) >> OpenJDK 64-Bit Server VM Homebrew (build 21.0.8, mixed mode, sharing) >> >> Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) >> Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec >> Java version: 21.0.8, vendor: Homebrew, runtime: >> /opt/homebrew/Cellar/openjdk@21/21.0.8/libexec/openjdk.jdk/Contents/Home >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac" >> >> Darwin **** 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:53:27 >> PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64 >> >> Docker version 28.3.0, build 38b7060 >> >> >> Details of changes since 1.9.0 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.1-RC1/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.1-RC1/site/changes.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.1-RC1/site/index.html >> (note some *relative* links are broken and the 1.9.1 directories >> are not yet created - these will be OK once the site is deployed.) >> >> JApiCmp Report (compared to 1.9.0): >> >> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.1-RC1/site/japicmp.html >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.9.1-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, 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/release-plugin/1.9.1-RC1/source >> >> 1b) Check out the RC tag from git (optional) >> >> This is optional, as a reviewer must check source distributions as a >> minimum. >> >> git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git >> --branch >> <https://gitbox.apache.org/repos/asf/commons-release-plugin.git--branch> >> commons-release-plugin-1.9.1-RC1 >> commons-release-plugin-1.9.1-RC1 >> cd commons-release-plugin-1.9.1-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- >> >
