This release vote passes with the following +1 binding votes: - Henri Biestro (henrib) - Gary Gregory (ggregory) - Rob Tompkins (chtompki)
Gary On Wed, Aug 14, 2024 at 2:45 PM Rob Tompkins <chtom...@gmail.com> wrote: > > +1 > > > On Aug 10, 2024, at 9:14 AM, Gary Gregory <ggreg...@apache.org> wrote: > > > > We have fixed a few bugs and added enhancements since Apache Commons > > CLI 1.8.0 was released, so I would like to release Apache Commons CLI > > 1.9.0. > > > > Apache Commons CLI 1.9.0 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/cli/1.9.0-RC1 (svn > > revision 70780) > > > > The Git tag commons-cli-1.9.0-RC1 commit for this RC is > > 698b238276c0e22e97e4aec703a0b00201d29666 which you can browse here: > > > > https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=698b238276c0e22e97e4aec703a0b00201d29666 > > You may checkout this tag using: > > git clone https://gitbox.apache.org/repos/asf/commons-cli.git > > --branch commons-cli-1.9.0-RC1 commons-cli-1.9.0-RC1 > > > > Maven artifacts are here: > > > > https://repository.apache.org/content/repositories/orgapachecommons-1768/commons-cli/commons-cli/1.9.0/ > > > > These are the artifacts and their hashes: > > > > #Release SHA-512s > > #Sat Aug 10 13:08:27 UTC 2024 > > commons-cli-1.9.0-bin.tar.gz=f3ed06d0269c38eaf0505751468e137807003741772bfc3b88aa6547f974f43bf6daa2c649d745a3eedae5e01ede1c730df0a63ee5ce7abc504ed5858d9ba7df > > commons-cli-1.9.0-bin.zip=6df718dae338caeb8905db0bcd9e1c147c60796a11c30a3c9eaaff5035492e2db21cdb496a4e47769339c1da7930ad8742d4976b9688d37f30ab2e40caf7dcec > > commons-cli-1.9.0-bom.json=0bdb44676d6bd310b614ade5c5728f79ecf7dbb3c5982ae9758a38361dc56838258a24f19b2d9560ebe0741df476c3a58c6226f60be2d2182577c2d003625441 > > commons-cli-1.9.0-bom.xml=c0aae3650e695986369e37a8690031d14d3db28b511840ff872b6eeb4ba4ff792add198fa22d1e09581904542012fd539c2df632599b09edae3c0ea4f5edc94a > > commons-cli-1.9.0-javadoc.jar=b581820ab885fc1c7326537d5135cce4c25e40b16234441015b77edb4e2dbe70e0bcda198783761ccf56983161b84d95a835a1dfe4316afb70240b4947522ef7 > > commons-cli-1.9.0-sources.jar=ff4268d93d10cb9a5373c4a2c9a71bf2b9ce9abfc2cdc9d7c2f2fcfe10462929b10025e7e68cc118bf825b26c3bfc5bf7fa83ef20542e8f15a9036386d9597d5 > > commons-cli-1.9.0-src.tar.gz=d20df809e8e0ebed79c57af9c9b447b0068347ba0edfcdec3652cb00bd9575b24fc77093d735e827d9d02a6fe2681bf239fd01df5f7c682ae34ade0781c53e35 > > commons-cli-1.9.0-src.zip=604b0329afd92b13a662549b02f68d11a71828a8745a74e2b08f912ae2d35814bd4f6278f3f74c9a24b55e6854a1af420848ed1f6182a29f6d30bb3568ad6e55 > > commons-cli-1.9.0-test-sources.jar=ef6d16ecb4cf01e3901df9451afb35bf2a122e6ff4af4d4b99560f9cb48933620a8f33cc810f4bcc5f9bff7ee6189e22b9300bd4619240d1b7aea55bd30aed31 > > commons-cli-1.9.0-tests.jar=ae995be6121589a321df596825d17d9379df88c9d6a23ada05879ef3a7a9c77865857b4b84c981c4b79a6da710a1d4837c2830cdc312690568ab83882225f94b > > commons-cli_commons-cli-1.9.0.spdx.json=444a59cece554fd97441de8cc411575ea715348cf5803e07ca1c28351cfba78c9849ea40ea4d11b0e73d5c72755d7041f8373596382a4b77062d2cb1a6335824 > > > > > > > > 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.12" 2024-07-16 > > OpenJDK Runtime Environment Homebrew (build 17.0.12+0) > > OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing) > > > > Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) > > Maven home: /usr/local/Cellar/maven/3.9.8/libexec > > Java version: 17.0.12, vendor: Homebrew, runtime: > > /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home > > Default locale: en_US, platform encoding: UTF-8 > > OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac" > > > > Darwin gdg-mac-mini.local 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul > > 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64 > > > > Details of changes since 1.8.0 are in the release notes: > > > > https://dist.apache.org/repos/dist/dev/commons/cli/1.9.0-RC1/RELEASE-NOTES.txt > > > > https://dist.apache.org/repos/dist/dev/commons/cli/1.9.0-RC1/site/changes-report.html > > > > Site: > > > > https://dist.apache.org/repos/dist/dev/commons/cli/1.9.0-RC1/site/index.html > > (note some *relative* links are broken and the 1.9.0 directories > > are not yet created - these will be OK once the site is deployed.) > > > > JApiCmp Report (compared to 1.8.0): > > > > https://dist.apache.org/repos/dist/dev/commons/cli/1.9.0-RC1/site/japicmp.html > > > > RAT Report: > > > > https://dist.apache.org/repos/dist/dev/commons/cli/1.9.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 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-cli.git --branch > > commons-cli-1.9.0-RC1 commons-cli-1.9.0-RC1 > > cd commons-cli-1.9.0-RC1 > > > > 1b) Download and unpack the source archive from: > > > > https://dist.apache.org/repos/dist/dev/commons/cli/1.9.0-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 > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
