+1 (non-binding) I checked: * hash and signatures for src and bin zips * no unexpected binary files (just some expected image files under site) * I tested the staged artifacts against the Groovy groovy-cli-commons test suite (all tests pass) * There appears to be an empty "src/test/java/org/apache/commons/cli/converters/" folder in the src zip that isn't in the github source tree AFAIK, but it's not doing any harm
Cheers, Paul. On Mon, May 20, 2024 at 12:55 AM Gary Gregory <ggreg...@apache.org> wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > CLI 1.7.0 was released, so I would like to release Apache Commons CLI > 1.8.0. > > Apache Commons CLI 1.8.0 RC2 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/cli/1.8.0-RC2 (svn > revision 69280) > > The Git tag commons-cli-1.8.0-RC2 commit for this RC is > 91369572408eff424ff5cec2d46dd9667ceba1b3 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=91369572408eff424ff5cec2d46dd9667ceba1b3 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-cli.git > --branch commons-cli-1.8.0-RC2 commons-cli-1.8.0-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1732/commons-cli/commons-cli/1.8.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun May 19 14:50:37 UTC 2024 > commons-cli-1.8.0-bin.tar.gz=9e8072c9d1efc8f8d5ecb65d82a02a8e573837ebf6e699b9675db7769c21fadc7157e7691e2a8dfb91267ccdac2671f64403631a394dc094a8481b8d5ffd190f > commons-cli-1.8.0-bin.zip=281019ef7dbb94702f5b7e5bcd0ed8947bcc55a62f87c4a93c97e34d95751352ccb191a368d8ff59ba389f342b2a7335effee0cf60fa4bbf2428f90ec648e530 > commons-cli-1.8.0-bom.json=2d9b8cb5333bf31a48fdb1037dec84c48434c619a4fe421529df7386f2ede67b76c61d2c490bbb5b6af301f92262a95fb3dff30b91468bb4b6ce555f2f1e1026 > commons-cli-1.8.0-bom.xml=00f5c34db21083b3f2677a931d9b2e10de60c40fa3f58fc2a01ea34e4b5227b800d58231df9194f2a39d2c40e062b859bce5399f93d2188ca230be81bfb93106 > commons-cli-1.8.0-javadoc.jar=ec49e3a71f26ac91b5ce16b6390d82d605cc78843fb93f6bef56484a306bcb2230d173569adfb0b28b3b222396313ecec4b852fd33745000d8712b55b8ad6dbf > commons-cli-1.8.0-sources.jar=f2740e9695d43cf56f111d47a7fb53ec99044eb69b259921096be0b57c963a19f4282579acf58052d5724cb6273028fe0457309b0b21c59f4039a0960f09c985 > commons-cli-1.8.0-src.tar.gz=588d89d86deb60ac0e182bd4b574e30aac4000dde9da13ee1080844a4982d45f4a4d29fc3ee54c904c74ed6bf14dbb3bffdcbad0eab86ddde8418811f2efb5c2 > commons-cli-1.8.0-src.zip=48513dc3fdf7deae5bfc94c4ef1975659a851a12432f3158ff764fd30ce03bdefeba0e255829e1c4d84f5a6185dbaabec1570917cf73360f395ab6b5b54f9613 > commons-cli-1.8.0-test-sources.jar=a59ae8590b6ebf4a25fe01e18fa55d6b5769b425d6363943671ae32271a17bd3ed226e3e35f0bcc3fafe0aca06a726f2211049cbad1fbb39d3cda008b894c689 > commons-cli-1.8.0-tests.jar=3a85ff142f3ea9ebf5d6d9c5efe407754803424e29f07e18ac8429f3a7c1dd706f518fee669f2108414d7120f8e5fdd2ee464d2096766beca7ec9ce3b80074b4 > commons-cli_commons-cli-1.8.0.spdx.json=1df478ac114f20e50fa7717a12d8838c03bd104f66b277a59b0e640a992e0c25894fc67ee7fde5927b3c5dc1ce6170bcc2010ef55abaec6484a6eae82c60d652 > > I have tested this with 'mvn' and 'mvn -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.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /usr/local/Cellar/maven/3.9.6/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.7.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/cli/1.8.0-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/cli/1.8.0-RC2/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/cli/1.8.0-RC2/site/index.html > (note some *relative* links are broken and the 1.8.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.7.0): > > https://dist.apache.org/repos/dist/dev/commons/cli/1.8.0-RC2/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/cli/1.8.0-RC2/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-cli.git --branch > commons-cli-1.8.0-RC2 commons-cli-1.8.0-RC2 > cd commons-cli-1.8.0-RC2 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/cli/1.8.0-RC2/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
