We have fixed a few bugs and added enhancements since Apache Commons IO
2.17.0 was released, so I would like to release Apache Commons IO 2.18.0.

Apache Commons IO 2.18.0 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/io/2.18.0-RC1 (svn
revision 73112)

The Git tag commons-io-2.18.0-RC1 commit for this RC is
be0b1eaea246aba841510807484a6ddd6ee5fcdb which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=be0b1eaea246aba841510807484a6ddd6ee5fcdb
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
commons-io-2.18.0-RC1 commons-io-2.18.0-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1786/commons-io/commons-io/2.18.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Sat Nov 16 15:27:00 UTC 2024
commons-io-2.18.0-bin.tar.gz=c99462d341a9ee1436f38fb2a594a823625fefc31a9d2a51910fa66830c4f3a65fd21dc9a9c3004e9a3c90025691e2863c0753b748f81aa2f38e6e6dbf1b36b0
commons-io-2.18.0-bin.zip=1168eaa6b12afa623d3cbe13abf8de4419e39c2068de1803cd4470b2d6abc0a900fec46d692a175c213fdad902ad3fb99bf0fe9245df16c66a9c5364beb61a75
commons-io-2.18.0-bom.json=57c9eb5fdb5d96be5c918109aff3c24f1ab3e425c28f66672d3d5a0e4b0fd0199550f7dc5d0b9b37b19f5516888c89e25c6d1cbb77086ce0ee59124ea5fdafb5
commons-io-2.18.0-bom.xml=68716f0499647d9b66d377553971deb0e088a58c006f720c225e10d977f1f9690f6f1d34083d880f9ea96d3bb5a5fe88aa4553739bc55e4f35ff45a2fd2bad52
commons-io-2.18.0-javadoc.jar=940dd1e83bbd22dccb48aadc7798cb175dc964c296caa01a7405ec63082e22581edb15666ad685c82bb41e18a34d2ad738141e94761f5ef6f6962337a880ebda
commons-io-2.18.0-sources.jar=e8631e1525c1442e7a355bb36fca438c49cdb4dec2276ae42ea60b70a30a8aba9fdeb286165047961c2768e0804b4fe3ccfc0fd9eef59a3649872b44b637dc25
commons-io-2.18.0-src.tar.gz=0abc1dc252a72825c5256793780a6e1fa91b8a60436bf6badab1eba8a41f44e1e69b2b90b44c641ddfb78c28f95848e13ffc611793dedf68751bbb5272f86f85
commons-io-2.18.0-src.zip=0a2f6c99902a48a0c2d0ec0a1db9e81d18ce7716a2ee85fb44f41f7d1eae797a9646b37b097b29289a6a3cc34fdd403200665f9e362cd49277de934416d9b5ed
commons-io-2.18.0-test-sources.jar=32bd92e8547fbf1d2dd7c9cf8de7922cdcce4f9693e5b0597cb7362149f363e8d0e93835933c3ed7aec4dea5444cd813d91b5265374f85b97bd4a05e10efe405
commons-io-2.18.0-tests.jar=2391904c7578944ec48b627ff8f5874c07a57d05bfa4365434886277925dfc09e2df6bf85a73ddb2466cc5dcb5af881b9d5b80dceb99e5d9e1fe35274edc23cc
commons-io_commons-io-2.18.0.spdx.json=f2659d759a877bce3416628befcaeac50a569a2032d40a57b47c56dad0cf995fd5072c6ccbd9456364f1b75559b78f0b92869e4d69ca97a6d52c1c847ead5360



I have tested this with 'mavn' and 'mvn -e -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:

openjdk version "17.0.13" 2024-10-15
OpenJDK Runtime Environment Homebrew (build 17.0.13+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.13+0, mixed mode, sharing)

Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /usr/local/Cellar/maven/3.9.9/libexec
Java version: 17.0.13, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.13/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.1", arch: "x86_64", family: "mac"

Darwin **** 24.1.0 Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:27 PDT
2024; root:xnu-11215.41.3~2/RELEASE_X86_64 x86_64

Details of changes since 2.17.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/io/2.18.0-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/io/2.18.0-RC1/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/io/2.18.0-RC1/site/index.html
    (note some *relative* links are broken and the 2.18.0 directories are
not yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 2.17.0):

https://dist.apache.org/repos/dist/dev/commons/io/2.18.0-RC1/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/io/2.18.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-io.git --branch
commons-io-2.18.0-RC1 commons-io-2.18.0-RC1
cd commons-io-2.18.0-RC1

1b) Download and unpack the source archive from:

https://dist.apache.org/repos/dist/dev/commons/io/2.18.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

6) Build the site for a multi-module project

mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

Note that the project reports are created for each module.
Modules can be accessed using the 'Project Modules' link under
the 'Project Information' menu (see <path-to-site>/modules.html).

-the end-

Reply via email to