+1 - all site, signatures, reports, and builds check out. Thank you!
> On Apr 13, 2024, at 1:20 PM, Bruno Kinoshita <brunodepau...@gmail.com> wrote: > > +1 > > Building OK from tag on > > Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0) > Maven home: /opt/apache-maven-3.8.5 > Java version: 17.0.10, vendor: Private Build, runtime: > /usr/lib/jvm/java-17-openjdk-amd64 > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux", version: "5.15.0-102-generic", arch: "amd64", family: > "unix" > > Thanks > > On Sat, 13 Apr 2024 at 15:44, Gary Gregory <ggreg...@apache.org > <mailto:ggreg...@apache.org>> wrote: > >> We have fixed a few bugs and added enhancements since Apache Commons >> Text 1.11.0 was released, so I would like to release Apache Commons >> Text 1.12.0. >> >> Apache Commons Text 1.12.0 RC1 is available for review here: >> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1 >> (svn revision 68475) >> >> The Git tag commons-text-1.12.0-RC1 commit for this RC is >> 2c2d0818b0540c59f055f5174db51d0574af46da which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=2c2d0818b0540c59f055f5174db51d0574af46da >> You may checkout this tag using: >> git clone https://gitbox.apache.org/repos/asf/commons-text.git >> --branch <https://gitbox.apache.org/repos/asf/commons-text.git--branch> >> commons-text-1.12.0-RC1 commons-text-1.12.0-RC1 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1719/org/apache/commons/commons-text/1.12.0/ >> >> These are the artifacts and their hashes: >> >> #Release SHA-512s >> #Sat Apr 13 13:34:53 UTC 2024 >> >> commons-text-1.12.0-bom.xml=43b65ff31fc8fbc65cb87b3dd4ccfc819ca3f22986d7b494184d6039dcef27f87879d86bc2b0b8aa11b1076fa08b940e211cbf0c717039cbb166d47ebc052244 >> >> commons-text-1.12.0-bom.json=5f3d52977598686724506ff0daf329cea26d1bb9d069b62f1f24e2ed483360fbd56ba3a7687590695a7a23dbffd90b03f9b59d73779eb6c057ce7aba40bda464 >> >> org.apache.commons_commons-text-1.12.0.spdx.json=32401c4d64fc0edc6aba525462309b86aa758ffe2201b89732f2c75845403c835b398fd783b3b670cd5c22875bdefe13dade05d3394d0642a45912de82e9ae59 >> >> commons-text-1.12.0-src.tar.gz=6f995d6b120109466c1af4aba7ba7678b1c7461628d78d0ae3139720c099411bc106a7d492727bb54b7714fb0c443a4844913b3d6f0f18befa9e3bc6e8171af0 >> >> commons-text-1.12.0-src.zip=f98f9fde5221914c133d6c1cb685d50ba6652991090cde27e3c3310eec4ed24229d0741107f671821bef216f4a5b2efa0488555a57e0d3c226d53c6497e2e502 >> >> commons-text-1.12.0-javadoc.jar=6e4d9493cef82660663b6af99f6c32f7fefdca2cb98c1ec8bbd4a01fb123b3348fdab7c32593b5cf3ddd69107ebf58124dc19b6679182d8568a43454e2a7602a >> >> commons-text-1.12.0-bin.tar.gz=c2f5cedf0a2f31fc0657241c9efb3113e221d8a4d53654448745f0ba853b4fa31ffa061810c53114ba16adee34d8c8dcc0e465e827dfeae03e9f91a2618f5bac >> >> commons-text-1.12.0-tests.jar=33381e48a5239a43458beb597cbd9c65c3d8ce8687a974dd1d21fe9d7bdb7acb6fc534ba3d9bd18c00cd5bf3e44b33b99a8c0bf2a7dc85613f789767bdf57605 >> >> commons-text-1.12.0-test-sources.jar=d9c9d7fc9473536ea6c92df58f3d33d489f26b0f44b6363d8fcc7a366e1a8ecda3ec366eac26ea61f5722c3438f602385ff9b777c30e895a6bfaeeb83524ace5 >> >> commons-text-1.12.0-sources.jar=eed680391a6181d44b5c6e6b0e99b7c36ed5d4d34e496f4299b7d77e9f0c0851966a6ccf4037a2ebc729c3dbdff67dd644a0534df651766f47ea8d16a7e18dc7 >> >> commons-text-1.12.0-bin.zip=fe50ac094fed72a8de3f92a275ee6d8be2a1ae6e94dc0b53df69444064574e7319b9fa6a265437ba6faf260f11a1f8c220ee3ed37ccde791f1488aea8f29a9d9 >> >> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P >> jacoco -P japicmp clean package site deploy' using: >> >> openjdk version "17.0.10" 2024-01-16 >> OpenJDK Runtime Environment Homebrew (build 17.0.10+0) >> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing) >> >> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) >> Maven home: /usr/local/Cellar/maven/3.9.6/libexec >> Java version: 17.0.10, vendor: Homebrew, runtime: >> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac" >> >> Darwin **** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05 >> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64 >> >> Details of changes since 1.11.0 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/site/changes-report.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/site/index.html >> (note some *relative* links are broken and the 1.12.0 directories >> are not yet created - these will be OK once the site is deployed.) >> >> JApiCmp Report (compared to 1.11.0): >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/site/japicmp.html >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.12.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) >> >> 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-text.git >> --branch commons-text-1.12.0-RC1 commons-text-1.12.0-RC1 >> cd commons-text-1.12.0-RC1 >> >> 1b) Download and unpack the source archive from: >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-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 >> <mailto:dev-unsubscr...@commons.apache.org> >> For additional commands, e-mail: dev-h...@commons.apache.org >> <mailto:dev-h...@commons.apache.org>
