+1 All looks good, builds, signatures, site, reports, Nit - release-notes have apache source header at the top.
As always, thank you Gary for your work!! Cheers, -Rob > On Jul 20, 2025, at 10:16 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > Text 1.13.1 was released, so I would like to release Apache Commons > Text 1.14.0. > > Apache Commons Text 1.14.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/text/1.14.0-RC1 > (svn revision 78270) > > The Git tag commons-text-1.14.0-RC1 commit for this RC is > 2c9212adb960b4b6180438745e8fcae3eae084f4 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=2c9212adb960b4b6180438745e8fcae3eae084f4 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-text.git > --branch commons-text-1.14.0-RC1 commons-text-1.14.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1850/org/apache/commons/commons-text/1.14.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Jul 20 14:11:44 UTC 2025 > commons-text-1.14.0-bin.tar.gz=8963bdd8a0dd88ac7382837e12a5678dc199263e7001d2df51b473ab5709dddfa301761b846c9f0d7e4a0c573d7e80a05a46480df0277f9741cade00fe36e9ab > commons-text-1.14.0-bin.zip=9934a1a66d9142e0d01902f58178ad7952b15a9236445064d10ac962273dbc2cb698638c162209c600fcfb670bc4419fa3753020084ab2334f7b585d3bed2e6b > commons-text-1.14.0-bom.json=b96998b4836b62fd847047716e878ad349b429e265d5addfd740f229acb9ace33c2026c312b52d0aee7ab054571d56357328ad747eef38a24e87a14249c1afd2 > commons-text-1.14.0-bom.xml=20104071062651663e6acfb7cfc1aa2ef239328278eb41af1cd3ba13601fb4367ac3dfd48822abe5edc42b9ea46687a651fd184da1e36cdf0cd427436bffd71e > commons-text-1.14.0-javadoc.jar=5a1ea4a4cdb4866583da8ecf59950d434897188912e43ad74927d0deb59a19a58f83f012d31663f3dedb683dd5853927429587e5a2d4d5ec6ca38868eddc1c11 > commons-text-1.14.0-sources.jar=2e732ff5029da4ffbce029869738bb46e9679d38fb4deb9060ddc7a5ce079c1cbbf88db639fbb8d8eaa4da52ac4155b6ef536c19c9d86844ce82d541d9d09af4 > commons-text-1.14.0-src.tar.gz=db9369ca5249e447f871b03f826782ff34d55f7f375c6fe9a6e6ffb740124ad38ced4487ea0bd9fafe1603b5dade9ce6fdd7d595af63b6d3a66560de936aa46a > commons-text-1.14.0-src.zip=9d099dac2df22aa3119e6112d72a0fc15f0d0f8aea61f1fc1ec49c72384247bfabac9f14582d058a2ee98a92f1744c3d76a0620f0a97487e1762c7c87a637e8b > commons-text-1.14.0-test-sources.jar=58da64543b6133303a39cea68918d7e52b15b75deb15816d793b1c05e60930f093149a5639aab53e8ff29fbbca2fb8d8d30334e83b4c69b531fab088eeb50849 > commons-text-1.14.0-tests.jar=df8ecbc8d0e0078396281dac245ec47c8233f028b1f61e34032caf27b66587825c64b82f34fe95b8c187bfe39b56ff42f6f1ebac952c975b09bd2479881c20a0 > org.apache.commons_commons-text-1.14.0.spdx.json=f27422d6a3e7310aa2249774a4b990645deb7b18bc0eae8078a801a0c5192829e224be4046f264be95fe53a94a71cdc204414d1ec8223464810131dee3ebf9a4 > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.8" 2025-07-15 > OpenJDK Runtime Environment Homebrew (build 21.0.8) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.8, mixed mode, sharing) > > Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) > Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec > Java version: 21.0.8, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.8/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac" > > Darwin ****.local 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 > 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64 > > Docker version 28.3.0, build 38b7060 > > Details of changes since 1.13.1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/text/1.14.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/text/1.14.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/text/1.14.0-RC1/site/index.html > (note some *relative* links are broken and the 1.14.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.13.1): > > https://dist.apache.org/repos/dist/dev/commons/text/1.14.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/text/1.14.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) > > 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/text/1.14.0-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must check source distributions as a minimum. > > git clone https://gitbox.apache.org/repos/asf/commons-text.git > --branch commons-text-1.14.0-RC1 commons-text-1.14.0-RC1 > cd commons-text-1.14.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 > > -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
