My +1

Gary

On 2024/02/06 18:48:12 Rob Tompkins wrote:
> +1 all looks good.
> 
> Keep up the good work Gary!!!
> 
> Cheers,
> -Rob
> 
> > On Feb 4, 2024, at 10:40 AM, Gary Gregory <garydgreg...@gmail.com> wrote:
> > 
> > We have fixed a few bugs and added some enhancements since Apache
> > Commons Codec 1.16.0 was released, so I would like to release Apache
> > Commons Codec 1.16.1.
> > 
> > Apache Commons Codec 1.16.1 RC1 is available for review here:
> >    https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1
> > (svn revision 67174)
> > 
> > The Git tag commons-codec-1.16.1-RC1 commit for this RC is
> > e59fc76531141cb4a36f3031457b9d5f07e5e43f which you can browse here:
> >    
> > https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=commit;h=e59fc76531141cb4a36f3031457b9d5f07e5e43f
> > You may checkout this tag using:
> >    git clone https://gitbox.apache.org/repos/asf/commons-codec.git
> > --branch commons-codec-1.16.1-RC1 commons-codec-1.16.1-RC1
> > 
> > Maven artifacts are here:
> >    
> > https://repository.apache.org/content/repositories/orgapachecommons-1688/commons-codec/commons-codec/1.16.1/
> > 
> > These are the artifacts and their hashes:
> > 
> > #Release SHA-512s
> > #Sun Feb 04 15:31:03 UTC 2024
> > commons-codec-1.16.1-bin.tar.gz=b9088ca7bd63cfe56c06c855af809948cae730b2be5c4c02619cf9a5cea2fab5c2226a3bec60d4f638dcd9af13700bb4e9f27fa1fac74d9249fae45042cb2a2a
> > commons-codec-1.16.1-bin.zip=81e87157533219e0162e5a2218ed891dbe5310729c8fe0f7208da5f1dc8f058ddb46990b3d8cdace2984a37043d1d6a0648e8c2d04e78831e1beb8b1d58ae130
> > commons-codec-1.16.1-bom.json=ccd6aadad4bd4ec67651eddff31fbb0c9568701bcc6a952e32929dc24c393d0b84a2f45e229eaf6f7b996dedf30524aaed25a359be49e85dedd6430219b8a1c3
> > commons-codec-1.16.1-bom.xml=958dff0d9be2ac855bace9976903a5e289fe65b10a797006a962151c2f15516d5b0a3eb46f441f76ded49fea46581e7b07baa42912a9da583c385d6b9f5c849b
> > commons-codec-1.16.1-javadoc.jar=027e85f4fe8adb2914e0b6bb80139081985e64097155f5f58f7c4141defc43a51d22da398c1cde1ac2ec18c6014c760e12bcfc40f48209bcb937a08249bff487
> > commons-codec-1.16.1-sources.jar=434725ec624f3e60a0bb174f1d505e0aeb10d2255035d3ecc215248e3336fae0cee08374604a989c4c09458c772830342908ebcc269a232569b1d780f2dba04e
> > commons-codec-1.16.1-src.tar.gz=8e2d40ae625c04e61b0dd7473dea0b32fdd13a6d3aad47b8b052952ca46f57d3df4917133f523ea147305a1c7ed9267cce7c4fa34d901496e36e9d5de9856e61
> > commons-codec-1.16.1-src.zip=c2f5a26959c33c43c71df7eebfddf7c1a255a19faa8dd0324c19cfa902f9a4d3876689deffb99cf68456785b8960705b0a2b62e567c83b0ce674f26ef6db2eea
> > commons-codec-1.16.1-test-sources.jar=1619f6d6dec4c4c0a26cb278cf53dffac2fb137d0c1f684156f19ef5db3a64ce2554dab29dc19a44247bf56d9bd3685c8c6d30234d15bd8cada28a12d35b47c4
> > commons-codec-1.16.1-tests.jar=3e5496a79bc29558369cc356d3a2f8f0b2116fe8ae0c0ca2e3033988f47afd6b7ad1bbf8d3dabfda558b8912d4f77c40a67617237a8ddd70fe738e5c76e895e2
> > commons-codec_commons-codec-1.16.1.spdx.json=a306898741d0fc70d9d773bc6ca88236c6d03bbce239d409c697ee516c1ff258c617599852dfdaa0cc80125e97fd555d2c9e1457f1adb43f863af88c9cd11bda
> > 
> > 
> > I have tested this with:
> > 
> > mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site 
> > deploy
> > 
> > using:
> > 
> > openjdk version "17.0.9" 2023-10-17
> > OpenJDK Runtime Environment Homebrew (build 17.0.9+0)
> > OpenJDK 64-Bit Server VM Homebrew (build 17.0.9+0, mixed mode, sharing)
> > 
> > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> > Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> > Java version: 17.0.9, vendor: Homebrew, runtime:
> > /usr/local/Cellar/openjdk@17/17.0.9/libexec/openjdk.jdk/Contents/Home
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "mac os x", version: "14.3", arch: "x86_64", family: "mac"
> > 
> > Darwin **** 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> > PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> > 
> > Details of changes since 1.16.0 are in the release notes:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/RELEASE-NOTES.txt
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/site/changes-report.html
> > 
> > Site:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/site/index.html
> >    (note some *relative* links are broken and the 1.16.1 directories
> > are not yet created - these will be OK once the site is deployed.)
> > 
> > JApiCmp Report (compared to 1.16.0):
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/site/japicmp.html
> > 
> > RAT Report:
> >    
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.16.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)
> > 
> > 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-codec.git
> > --branch commons-codec-1.16.1-RC1 commons-codec-1.16.1-RC1
> > cd commons-codec-1.16.1-RC1
> > 
> > 1b) Download and unpack the source archive from:
> > 
> > https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-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

Reply via email to