+1 to release!

> On Apr 15, 2024, at 12:53 PM, Rob Tompkins <chtom...@gmail.com> wrote:
> 
> +1 site, release-notes, signatures, and builds all check out
> 
> Thanks!!
> 
> -Rob
> 
>> On Apr 13, 2024, at 7:29 AM, Gary Gregory <ggreg...@apache.org> wrote:
>> 
>> We have fixed a few bugs and added enhancements since Apache Commons
>> CLI 1.6.0 was released, so I would like to release Apache Commons CLI
>> 1.7.0.
>> 
>> Apache Commons CLI 1.7.0 RC1 is available for review here:
>>   https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1 (svn
>> revision 68470)
>> 
>> The Git tag commons-cli-1.7.0-RC1 commit for this RC is
>> caed6714a73ce366aebccebf4a21e287d6d34ae0 which you can browse here:
>>   
>> https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=caed6714a73ce366aebccebf4a21e287d6d34ae0
>> You may checkout this tag using:
>>   git clone https://gitbox.apache.org/repos/asf/commons-cli.git
>> --branch commons-cli-1.7.0-RC1 commons-cli-1.7.0-RC1
>> 
>> Maven artifacts are here:
>>   
>> https://repository.apache.org/content/repositories/orgapachecommons-1718/commons-cli/commons-cli/1.7.0/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sat Apr 13 02:26:30 UTC 2024
>> commons-cli-1.7.0-bom.json=fd710316564b50a1af147751c01f25c473c8ccee4af117e3ebd12f7e1eda9524b10389e8ae8705922cc82c0164bc1c5a2977327eb22eac449ce4b149b15d3d90
>> commons-cli-1.7.0-test-sources.jar=7b1e4940a6d0b2c84939146122849db1086730d93b8c540047a6fd2b6112eba9c420008302300557c8187821316cddbb7b0599664f04fa21e325e04bd4bb06f0
>> commons-cli-1.7.0-src.zip=e0f684163327c6180098c61d89705ff49041239b04dcd0235dd0b7b3b9ac590c23da85236ae4458135b1d804824d639db2f4a85ee9cfa281c2cc49ec2f5775f1
>> commons-cli-1.7.0-javadoc.jar=fea0659ba7c7f23940547f2aa6ae15d85817a7ecf9d537083b7c5873012e85b39aa9dbf1054f69f49a86b30b3ea06e037dc5b972c1bc553caa2c6004be409613
>> commons-cli_commons-cli-1.7.0.spdx.json=1527955bcb67fdbefac08bd6905290f01c3397e6921eb5980e4b96145cf68a4a6745f28b29435fb4e181f051cd1c9d43017d53db5df6a12e76244bd642c5213a
>> commons-cli-1.7.0-bin.zip=07a2a6698ba1010c5952ec26ad2e4ce73a87476f0fd97dd34cb5280f0563c0a0bdeb65e3cc9afbe9bca50c149f2570fa716f0a617c9f277b1ffdd9baa75081d0
>> commons-cli-1.7.0-tests.jar=08338e5488c6d12e28a65b2d5ea2da172a087832c0c58915f47e1078038b10873bf5594237dc2275a6079027487745d5a76722424c5482c5f786ba95f5c34acb
>> commons-cli-1.7.0-src.tar.gz=d97be4df213e0df72a3866b8271e34064e984e98debb2ae8bdd1bef94ea1fd358655dbc730866cb62b4232bad7888d69b4d964a101139f2cf36cd0fcfb39d28b
>> commons-cli-1.7.0-sources.jar=9bc86da3391d3fc87806384fda1272b8e0a0313eb529ae4e9eaf7d5fc63708a90449f6fe72b4d29da730c21c4fc497f395c01812b625803479884e08f0593090
>> commons-cli-1.7.0-bom.xml=40623202b108d74635fee720a826e730ed63b838596db45a887f4718be949db9ca01f9661be3c03067b2d1d9246d7fde1524c83c7718db1cb2202e0d3ed748d2
>> commons-cli-1.7.0-bin.tar.gz=c429f22021bbb80f11e9b27bc768ec28b797d9d6fc18b3af369bfc7278641f2585c62cd6d6736b7f1813e3f9690390f8fd304743f123ae9fff496edd1942cac6
>> 
>> 
>> I have tested this with 'mvn' and 'mvn -V -Duser.name=$my_apache_id
>> -Dcommons.release-plugin.version=$commons_release_plugin_version
>> -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
>> deploy' using:
>> 
>> openjdk version "17.0.10" 2024-01-16
>> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
>> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
>> 
>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
>> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
>> Java version: 17.0.10, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
>> 
>> Darwin ***** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
>> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 1.6.0 are in the release notes:
>>   
>> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/RELEASE-NOTES.txt
>>   
>> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/site/changes-report.html
>> 
>> Site:
>>   
>> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/site/index.html
>>   (note some *relative* links are broken and the 1.7.0 directories
>> are not yet created - these will be OK once the site is deployed.)
>> 
>> JApiCmp Report (compared to 1.6.0):
>>   
>> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/site/japicmp.html
>> 
>> RAT Report:
>>   
>> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.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)
>> 
>> 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.7.0-RC1 commons-cli-1.7.0-RC1
>> cd commons-cli-1.7.0-RC1
>> 
>> 1b) Download and unpack the source archive from:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.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
> 

_______________________
Eric Pugh | Founder | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com <http://www.opensourceconnections.com/> | 
My Free/Busy <http://tinyurl.com/eric-cal>  
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 
<https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw>
    
This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.

Reply via email to