On Mon, Nov 9, 2026, 23:17 Rob Tompkins <[email protected]> wrote:

>
>
> > On Nov 8, 2026, at 10:56 AM, Henri Biestro via dev <
> [email protected]> wrote:
> >
> > [+1]
> >
> > - SHA-512 checksums OK for all dist archives and match the vote email.
> > - GPG signatures OK (key 530AA5F25C25011F, in KEYS) for dist archives
> >  and all Nexus staging artifacts (orgapachecommons-1973).
> > - Source archive matches tag commons-lang-3.22.0-RC1 (562de6e4).
> > - Nexus jars are identical to the jars in the binary archives.
> > - LICENSE/NOTICE OK; RAT clean (0 unapproved); no bundled third-party
> code.
> > - japicmp vs 3.21.0: no binary incompatibilities.
> > - Default 'mvn' build from the source archive passes (tests, RAT,
> >  japicmp, checkstyle, PMD, SpotBugs, javadoc) on:
> >    Java 1.8.0_345, 17.0.20, 21.0.8, 25.0.5.0.3 (Azul Zulu),
> >    Maven 3.9.16, Darwin 27.0.0 arm64
> > - 'mvn clean verify site' OK on Java 27.0.1.0.3; reports clean
> >  (Checkstyle 0, SpotBugs 0, PMD 0, RAT 0 unapproved, 110,799 tests
> >  0 failures).
> > - Reproducible: built with JDK 27 (TZ=UTC), all jars, the pom and both
> >  CycloneDX SBOMs on Nexus rebuild byte-for-byte.
> > - Smoke-tested the staged jar on Java 8, 17, 21, 25 and 27, including
> >  the new fair TimedSemaphore and the RandomStringUtils '~' fix.
> >
> > Notes:
> > - RELEASE-NOTES.txt is ISO-8859-1; "Ivan Šarić" comes out as
> >  "Ivan ?ari?" (3 entries). Same in 3.21.0, so not a regression.
> > - Minor: the SHA-512 list in the vote email omits
> >  commons-lang3-3.22.0.jar and commons-lang3-3.22.0.pom.
>
> How so, they just aren’t there?
>
> If thats the case I need to write a fix for the release plugin. That is,
> if the complete boss Gary hasn’t already beaten me to it.


Good find. I fixed this in
https://github.com/apache/commons-release-plugin/commit/10449165df30415458850f4cbd8deb9c91309b5f
and it's available in 1.10.0-SNAPSHOT builds. I also create an RC.

Gary

>
>
> Cheers,
> -Rob
>
> >
> > Henri
> >
> > ---------------------------------------------------------------------
> > 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