+1 Build passing 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-101-generic", arch: "amd64", family: "unix" Site reports look good, checked dist area files and found no issues. Thanks! On Mon, 25 Mar 2024 at 14:51, Gary Gregory <ggreg...@apache.org> wrote: > We have fixed a few bugs and added some enhancements since Apache > Commons IO 2.15.1 was released, so I would like to release Apache > Commons IO 2.16.0. > > Apache Commons IO 2.16.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1 (svn > revision 68124) > > The Git tag commons-io-2.16.0-RC1 commit for this RC is > c0d44bcc782372980c9e6881537c801e6d84219f which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=c0d44bcc782372980c9e6881537c801e6d84219f > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-io.git > --branch commons-io-2.16.0-RC1 commons-io-2.16.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1708/commons-io/commons-io/2.16.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Mon Mar 25 13:40:18 UTC 2024 > > commons-io-2.16.0-src.tar.gz=a97c6467f1ea48be8118c85f71360e775991b971b860b7371c3e184418bf14a3ac39a87379e427bab4aa8bd0283c1367882f06ae2f2fae423a0ed48b23335a70 > > commons-io-2.16.0-javadoc.jar=87d02e2bcc0d07b7bbf9d84fbade92b3964343c1d73fd931a78731a94edc18f3b2f0b5b726b8914d8d40c713f291b1d7b960079a34b240c183549c296120b48e > > commons-io-2.16.0-test-sources.jar=429106f6a17b81617107691307f3601fe160fd625b277e9983d27b5085e416b9570b6f41919d9d2a915ea0e1f788e43d46f88d9a0ff4468df12aa3b8dbbabc16 > > commons-io-2.16.0-bom.json=d29cad554cabb2cc68576bbff94956c0d096b70caca91e74729c749e615bbf40d49e398bb552676708f29a5b710e8d5a4797d72b9b3e1b5790bddba60bccb455 > > commons-io-2.16.0-bin.tar.gz=cae78a84809046989be88d8e2205597f14362c6deba5bd87744ed36d097b2395fdb3602ee2bd9017ea382e8772393565ac780eed15ca4c2b9c0e45b1fdb362cc > > commons-io-2.16.0-src.zip=a1e12a4b54ebe1c56359a962174a0d5457f91fcaef15827d84b03618ac876540e5f08551a5d11fe67e5d5c19c6ea5d987687ed5c74d372df08d95eb98e088dfa > > commons-io-2.16.0-bom.xml=75f6682f694432a76c3435c08a6f01c1dc6bec79026f1751c69af5957129ae876f82dfbf5464bfbaa084f9c0cdc5af671900230e76df6a4106d3e5d1ad5260c1 > > commons-io_commons-io-2.16.0.spdx.json=a76f8f587a6ee1d869ed789fd73ae13e3984462507a56807302eb8f4dc6ae406ae15b47e3f6c2f01de3252c6108a92c293a8d32f54be18aa77838314bbe878f6 > > commons-io-2.16.0-bin.zip=c40c47572f6716814a992c00291032a80a5ec6ac2910850f260450fea883288a7a582e583344a165235457eda4ef116c6e417e9eaeabfd7870e121a477416c62 > > commons-io-2.16.0-tests.jar=721cde073c07d2ae145309f9cebd568e1910d5a3809efeb7fc2cb04e789c4012fa45e36074e43d93b7795cf607acb8f3dfcf998aad996657e49c58618607f463 > > commons-io-2.16.0-sources.jar=6826bc3886a56e330fec6225d7e5550de640298e1bdd33739276819294e320334ffb81c9e04bea8c0b5138f2e135b6fee197b27f4347d59119c8728783b1841c > > 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.3.1", arch: "x86_64", family: "mac" > > Darwin **** 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 > PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64 > > Details of changes since 2.15.1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/site/index.html > (note some *relative* links are broken and the 2.16.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.15.1): > > https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/io/2.16.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-io.git --branch > commons-io-2.16.0-RC1 commons-io-2.16.0-RC1 > cd commons-io-2.16.0-RC1 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/io/2.16.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 > For additional commands, e-mail: dev-h...@commons.apache.org > >
