Signatures good, site looks good, all the reports looks good, release notes look good. Send it
+1 > On Apr 7, 2025, at 3:49 PM, Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed a few bugs since Apache Commons Text 1.13.0 was > released, so I would like to release Apache Commons Text 1.13.1. > > Apache Commons Text 1.13.1 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/text/1.13.1-RC1 > (svn revision 76119) > > The Git tag commons-text-1.13.1-RC1 commit for this RC is > a70c34e028ab279bb89565606e1ab09011a41bc2 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=a70c34e028ab279bb89565606e1ab09011a41bc2 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-text.git > --branch commons-text-1.13.1-RC1 commons-text-1.13.1-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1816/org/apache/commons/commons-text/1.13.1/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Mon Apr 07 19:43:05 UTC 2025 > commons-text-1.13.1-bin.tar.gz=fadaf8331604bce151c04c5391a44301052745a106f06a2b3fcb171435908302b115cb861346cfae93f3711c45f9818b6afda2ddc73252664abcd8191c914786 > commons-text-1.13.1-bin.zip=3ace0384ef918784f9a363a8f815d9a286745acff45d117aeb279b7e952f5159d0e9ee2a46c59a7c76341d469ddb4167f1ef12cca8da74dc9a7be68c4db37fe7 > commons-text-1.13.1-bom.json=d10dc69f3474de3057adaae84b40dc612c0c090f3e7bd3f129dc76c3d9c17ad3b048075842240d2f81684a6d93cc3e00bc1dc570e7cbfbad958fe438b1341bf8 > commons-text-1.13.1-bom.xml=1a01aa46920a9770c6599110d68cdba03b5199d3a0984f590c4c0927c81a116addeef625590445d970d82b26d3cfd4facbbf3c2e90de0667d0e3d2ecbdda23a9 > commons-text-1.13.1-javadoc.jar=85ec06d73f93c80994196c284742d3fb73956e08dd6371e82aaae30cf80f2236aac7215cc225d6d3db5c8d0f889d86f8c031c3ec179130c11bfc7440cb4212b5 > commons-text-1.13.1-sources.jar=b0e598918c2f3ad86f7f9fa0e2ab2c1e0842361120031ce0f35b7aa982f964794570542a3fa5fae512a579ac25e4d2355d75d9106158eeb215ad5bd51ec902e7 > commons-text-1.13.1-src.tar.gz=4884c9cf5117065fc92a29d05b5e148e72eec51d01c9744fd72f20566a8a28657d4dbfd33971f7d8aeb320329e49bba18a8cbf0c075207fe215a7e2f363b5169 > commons-text-1.13.1-src.zip=8fb4c7f14f1ac9816f0f4ea4d09a1742f9c5ba31a3e6107ed6260be58637adda64a13b8fd963c095fa18be822b7f24e0bb1f0d2d75ee542766926d64984380a8 > commons-text-1.13.1-test-sources.jar=eca2a84df1a8f461767c46c306cefed6d18aa6e820cc9fb50137507fde08a3bc301f204f1f757204c66134cdc6153261ebade42a7d2b9a433256bebd2ab7a910 > commons-text-1.13.1-tests.jar=e5301303c70ff17abd29be4fb1de034fdc13e76d9734a15b85ba230edd7cd1b8a07a57e54da8c1bab4b45c5e4a910423c54d8478d4f236fafdc04a59b0e4bf7f > org.apache.commons_commons-text-1.13.1.spdx.json=160e57f99760f35216f8f639d6c8c9b0b36274e590944fdec74e77f9261f7a5874f93055b73abc49ecf1ec09613a87a22089bbb1c4e12b7d733253cb137d80e7 > > > I have tested this with 'mvn' and 'mvn -e -V -P release -P test-deploy > -P jacoco -P japicmp clean package site deploy' using: > > openjdk version "21.0.6" 2025-01-21 > OpenJDK Runtime Environment Homebrew (build 21.0.6) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.6, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec > Java version: 21.0.6, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.6/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.4", arch: "aarch64", family: "mac" > > Darwin Garys-MacBook-Pro.local 24.4.0 Darwin Kernel Version 24.4.0: > Wed Mar 19 21:17:35 PDT 2025; > root:xnu-11417.101.15~1/RELEASE_ARM64_T6041 arm64 > > Docker version 28.0.1, build 068a01e > > > Details of changes since 1.13.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/text/1.13.1-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/text/1.13.1-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/text/1.13.1-RC1/site/index.html > (note some *relative* links are broken and the 1.13.1 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 1.13.0): > > https://dist.apache.org/repos/dist/dev/commons/text/1.13.1-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/text/1.13.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) > > 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.13.1-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.13.1-RC1 commons-text-1.13.1-RC1 > cd commons-text-1.13.1-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
