We have fixed a few bugs since Apache Commons IO 2.16.0 was released,
so I would like to release Apache Commons IO 2.16.1.

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

The Git tag commons-io-2.16.1-RC1 commit for this RC is
6d36827cdf894d9506924737269f08492e4096a1 which you can browse here:
    
https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=6d36827cdf894d9506924737269f08492e4096a1
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-io.git
--branch commons-io-2.16.1-RC1 commons-io-2.16.1-RC1

Maven artifacts are here:
    
https://repository.apache.org/content/repositories/orgapachecommons-1713/commons-io/commons-io/2.16.1/

These are the artifacts and their hashes:

#Release SHA-512s
#Thu Apr 04 20:35:11 UTC 2024
commons-io-2.16.1-javadoc.jar=cbf738198189737f691ad044bd731303a42ac24b3529236efabe813d173effd8e1d695be3b58ca70d39218fca08492dea7c018c9a694e2d382d1175a4321c1cd
commons-io_commons-io-2.16.1.spdx.json=e7553943c9a03f70b995d00313ece81d33142b1386f2c3af78dd0323a39d67022e588cb6350cdcd1fe18412ecf80964ad05ff66e9f7ae02dfd21201d0d7e9931
commons-io-2.16.1-bom.xml=b5b0701af1a828e52d4ae4e685f301efb592dcea21e6e2be5c65db21390c5a87cddb761b1b6043e412fe3c8120d9efa501f6156ab923bde5c54314ce507df979
commons-io-2.16.1-bin.zip=b697095f38f576299b444478a31e52ba642705cae2ce89f76da38232737576faa4a4eac441aece2122f1e92c705d25fa60cac5d636da12dc3e8e78a3dbf5e18e
commons-io-2.16.1-test-sources.jar=e258723f31cc058a39f70b23415c6eb4202f2a753f57ce3ea317c66b0fe69c0a814aaef8adb4aec12a9019caedd98cd2ea41d17991b7932383baf01290efcab6
commons-io-2.16.1-tests.jar=21b7c8d0a9730281a1dbe51e44ecc44745e43db1cbff1d64ab788ac63e249f1c9899c9c96d77488a299f1f59bb9c35b4b8c98e0eeab9f7f495277f34139edd5d
commons-io-2.16.1-sources.jar=bc8f3869160f64ab9c1b8a11d40b73d726e95e55ce66ec4c5e4e3df10d8341692b74bb0e5b4c65e832216be1912ff944d6179befc98d4aa79337e792cf32bb5b
commons-io-2.16.1-src.zip=59556ca25e29bcaf7cd091ed3376f4a0525dbaec822a360071d450e1b979a17475485d768c39ff45ec53e8b901cb9c98166ea2242557dad22c156ed4e2ccae11
commons-io-2.16.1-src.tar.gz=eb3558d0bd5a124217f4d81dde84ddae4ed47b0f9415062dc9e247a29b1101f850556d2e5eae65007e4ed597aaedcda1db0de42f98142e91d802d136ccdf4ca3
commons-io-2.16.1-bom.json=21dabe2118730a8635b3d97f2d4fba5f8a1d1c0ee2161804fe4ee4ba626195df1c66cb340e6cc97caf2d9d7abe7e60e9e6b4d669977635cc81fddc5797273ece
commons-io-2.16.1-bin.tar.gz=12a6069f66e0b3faa2a16ef4da9594766e5e69f04b11e0717879910df26e7ab179e1cb007abb2c68ee8071b794ea4b0651fc4ca880acddb6be458dbacc02fb44

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 2.16.0 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC1/site/changes-report.html

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

JApiCmp Report (compared to 2.16.0):
    
https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC1/site/japicmp.html
    There no API changes.

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/io/2.16.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)

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.1-RC1 commons-io-2.16.1-RC1
cd commons-io-2.16.1-RC1

1b) Download and unpack the source archive from:

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

Reply via email to