+1, but I didn’t test with 1.8. Everything else is good to go signatures, site, 
builds, release-notes. All good. My +1 is predicated is if we don’t need a 1.8 
test.

Thank you Gary!!!!!


Cheers,
-Rob

> On Nov 8, 2026, at 9:22 AM, Gary Gregory <[email protected]> wrote:
> 
> We have fixed a few bugs and added enhancements since the release of
> Apache Commons Lang 3.21.0, so I would like to release Apache Commons
> Lang 3.22.0.
> 
> Apache Commons Lang 3.22.0 RC1 is available for review here:
>    https://dist.apache.org/repos/dist/dev/commons/lang/3.22.0-RC1
> (svn revision 89139)
> 
> The Git tag commons-lang-3.22.0-RC1 commit for this RC is
> 562de6e40e0742f471adefcf05bd4b273d995028, which you can browse here:
>    
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=562de6e40e0742f471adefcf05bd4b273d995028
> You may checkout this tag using:
>    git clone https://gitbox.apache.org/repos/asf/commons-lang.git
> --branch commons-lang-3.22.0-RC1 commons-lang-3.22.0-RC1
> 
> Maven artifacts are here:
>    
> https://repository.apache.org/content/repositories/orgapachecommons-1973/org/apache/commons/commons-lang3/3.22.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Nov 08 14:10:56 UTC 2026
> commons-lang3-3.22.0-bin.tar.gz=259e9e67813a16d9131f7265c130280ae2d8d51bd16442a02ef3876c67cecf3c83bc2a275719e052c357fee7381a84779d3e47e9cf132951c9a0d3d872677b6b
> commons-lang3-3.22.0-bin.zip=c23c3337b56a5a7acd3ca2eca2c3c85348fa98bf307206a893916d8328ecd9eff63026f9f2ace33f5900f51d158968a312de510e07345035dbb39bd9901fabde
> commons-lang3-3.22.0-bom.json=6959d38fc12648778494c576b1e5f002065f4856098bcdb13e9c3cb5259d49aa2e752fbc9fd907481628d37da1593401b5fa33084d1cc58837090cd2fb94629f
> commons-lang3-3.22.0-bom.xml=ad7461e48080f39087c94bc15fe9e436a9b65ba7665cd4bc2e6206e619b7659b42a13d7f08cb0b1c172e47af36d221d953fe492a907f48b5b33bd8f669a77c0e
> commons-lang3-3.22.0-javadoc.jar=3dbd4be5a64d51fbbecc623721a88cdfd6c7d298407b5c3005e16d06b999e6aed3d0f7c3183130749288dd1f43b90a099144ce23704c47fa64cefe9fe3fabb34
> commons-lang3-3.22.0-sources.jar=f8fb79716b577ab8e0a286cbdacd6d0a233ad29fa294840fe4aac6b5adbc75efa85ecd80b262f5b415f5bbc87a57fce8f603396a13cc5db6ab77b6af751ba9e5
> commons-lang3-3.22.0-src.tar.gz=8f3dea22cacb43085cf5637162520a95a78175e56ef6e5b7fd84203e876164333108345e5e4fa387d5b9c07b9c3a758f484c69725e2255478936f33994abbf53
> commons-lang3-3.22.0-src.zip=87277e2ed27ea09505c30b8ec9757991b6dde76d4aa0a34c862ce5e8fe69ccc62c106f638e6c5974233343868534f7a4896ee8f4c39a17ac1a22e1221698c896
> commons-lang3-3.22.0-test-sources.jar=ae3d96d2c6ca1141e194323a58e2de96afc4159b354be6ee0c53c53ba6e44bb786b63c011760dd0388958df3a3948ef7a245808c699fb3e034d8278f20959fb2
> commons-lang3-3.22.0-tests.jar=669588def763d9a8eea901b3302f267dbb86db8ac1b0efb59825cdf4e90d218d88dc4b27e983fa5ad562ddb86d7fe340d1d370425c05b2354e7bd633685eaeb8
> org.apache.commons_commons-lang3-3.22.0.spdx.json=65b444655a6e7b5f8acb147954a01eb7aed8287772ff3ef9850d0c7993876f8d01ac6dd7b9d21a3b54a6b8cfec026e1538185a07570a0d2a0c4845daeb5603b7
> 
> 
> I have tested this with 'mvn' and 'mvn clean install site' using:
> 
> openjdk version "27.0.1.0.3" 2026-10-24
> OpenJDK Runtime Environment Homebrew (build 27.0.1.0.3)
> OpenJDK 64-Bit Server VM Homebrew (build 27.0.1.0.3, mixed mode, sharing)
> 
> Apache Maven 3.10.0 (c43a36b8d67be7e0805a411bc0898af1a51f5472)
> Maven home: /opt/homebrew/Cellar/maven/3.10.0/libexec
> Java version: 27.0.1.0.3, vendor: Homebrew, runtime:
> /opt/homebrew/Cellar/openjdk/27.0.1.0.3/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8, time zone: UTC
> OS name: "mac os x", version: "26.7.2", arch: "aarch64", family: "mac"
> 
> Darwin ****.local 25.6.0 Darwin Kernel Version 25.6.0: Mon Oct 12
> 00:39:48 PDT 2026; root:xnu-12377.161.15.701.48~2/RELEASE_ARM64_T6041
> arm64
> 
> Docker version 29.9.2, build a82e528
> 
> 
> Details of changes since 3.21.0 are in the release notes:
>    
> https://dist.apache.org/repos/dist/dev/commons/lang/3.22.0-RC1/RELEASE-NOTES.txt
>    
> https://dist.apache.org/repos/dist/dev/commons/lang/3.22.0-RC1/site/changes.html
> 
> Site:
>    
> https://dist.apache.org/repos/dist/dev/commons/lang/3.22.0-RC1/site/index.html
>    (Note some *relative* links are broken and the 3.22.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.21.0):
>    
> https://dist.apache.org/repos/dist/dev/commons/lang/3.22.0-RC1/site/japicmp.html
> 
> RAT Report:
>    
> https://dist.apache.org/repos/dist/dev/commons/lang/3.22.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 530AA5F25C25011F)
> 
> 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/lang/3.22.0-RC1/source
> 
> 1b) Check out the RC tag from git (optional)
> 
> This is optional,  as a reviewer must at least check source distributions.
> 
> git clone https://gitbox.apache.org/repos/asf/commons-lang.git
> --branch commons-lang-3.22.0-RC1 commons-lang-3.22.0-RC1
> cd commons-lang-3.22.0-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
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to