My +1 Gary
On Sat, Aug 24, 2024 at 3:21 PM Gary Gregory <[email protected]> wrote: > We have fixed a few bugs and added enhancements since Apache Commons Lang > 3.16.0 was released, so I would like to release Apache Commons Lang 3.17.0. > > Apache Commons Lang 3.17.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/lang/3.17.0-RC1 (svn > revision 71083) > > The Git tag commons-lang-3.17.0-RC1 commit for this RC is > 29ccc7665f3bc5d84155a3092ab2209a053324e6 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=29ccc7665f3bc5d84155a3092ab2209a053324e6 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-lang.git > --branch commons-lang-3.17.0-RC1 commons-lang-3.17.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1777/org/apache/commons/commons-lang3/3.17.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sat Aug 24 19:06:25 UTC 2024 > > commons-lang3-3.17.0-bin.tar.gz=8927a406a1bd084b548f89cf15fe4bc7567dcaa50ae8abae54e9c883c1574c648fcc8ad6c3abaa381dfbdf1801727ac5e6c4572063203a1dfac293d122282f05 > > commons-lang3-3.17.0-bin.zip=00ea810d00b0f8a5bf898edfed1fa022e9bd2bf31c9c00859de2ac6c4bc971d6833f3c2e0b24cecad6bb979de2078be8b1cc7eb42ca63c9ec35f70b1490e8c3d > > commons-lang3-3.17.0-bom.json=b39ff96546bccdcf8fd2547ba3c130988541a99557e08de4b99bae09c43be569bf1939cec9fdba65d54df890c80fe58ba72e5194f9adb26c00b3f497f7f04230 > > commons-lang3-3.17.0-bom.xml=973b469f1395cfd709f281878faaed610cde2a778e66609ccd76408a17718c5291e538f1fe1b09052b7042d0aa7bed1f38f39249b3e2c0ff374d3165d63b443b > > commons-lang3-3.17.0-javadoc.jar=64a1feec66688bb06486871a6a0bf3075d57efddad8fd36a1d540c88ac8e7c562cf5dbffd5c4e5155cbc808f10b8001210728719727fdc6d246a0536fdc60d35 > > commons-lang3-3.17.0-sources.jar=15954a47f38df821f97282d130c16e4885dcae16503e3876adc5518a3f6f7f3ecfa62b777b98b6ae11878e305f99ed28181c28f3369d4da2a3fb7c696d4be1d2 > > commons-lang3-3.17.0-src.tar.gz=e633b0caeb9556c68384c2bf20e374fbac910b9979b25774c632e50c1bec41e97c14362978dc092c8b5859291e54fe51e76ad7a61c9b2efbe1e4538f46c1e3ee > > commons-lang3-3.17.0-src.zip=7e715243fd2cd0464eadd5140949c751ae199b87f4f6db6a0b878fe3bcbc513e3a9603f7bc09a2251cb61b794843826f3ea9d5c21a7b3b5f78cae13ab7b10bed > > commons-lang3-3.17.0-test-sources.jar=bca1775e70313838191d530181ecf41ae832cb5bf041d2713af71e8b6d931307776ed9f10cf27a7f6f45a2b497a6ab717730e2a21605473eddb829738ca9e242 > > commons-lang3-3.17.0-tests.jar=b6138e9e92845ad790b2bbc43440ba16b92478700ee3f4e620b1fbb6d0796c2e110b53ab85f845d05a0d3e56f55417faf7eb01b15efe70339ccdf76ed3da76bc > > org.apache.commons_commons-lang3-3.17.0.spdx.json=b9ca110a8e4e5304091991db151ad64a43ddd6ac10c170b07596666daa84565df333cee5cf8d85af2f600233c692b27b826858db1af1a0ab2add7fcb77a1f3c0 > > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy -P > jacoco -P japicmp clean package site deploy' using: > > openjdk version "17.0.12" 2024-07-16 > OpenJDK Runtime Environment Homebrew (build 17.0.12+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /usr/local/Cellar/maven/3.9.9/libexec > Java version: 17.0.12, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac" > > Darwin **** 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT > 2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64 > > Details of changes since 3.16.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.17.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/lang/3.17.0-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.17.0-RC1/site/index.html > (note some *relative* links are broken and the 3.17.0 directories are > not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 3.16.0): > > https://dist.apache.org/repos/dist/dev/commons/lang/3.17.0-RC1/site/japicmp.html > > *** > Note that the above report notes several errors. > These are considered OK for the reasons stated below. > These exceptions are also noted in the Changes and Release Notes. > > Errors reported: > - methods added to interface: OK because that does not affect binary > compatibility. > - etc. > *** > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.17.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, 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-lang.git --branch > commons-lang-3.17.0-RC1 commons-lang-3.17.0-RC1 > cd commons-lang-3.17.0-RC1 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.17.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- > >
