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

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

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

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

These are the artifacts and their hashes:

#Release SHA-512s
#Sat Oct 21 14:59:24 EDT 2023
commons-io-2.15.0-bin.tar.gz=026dc2e2ba6edea920813dff5d8e09a5d4e2af5c91b79096159375731bebfefa38be6c1394e57f0f9cef6969c906472ca25f1fa67a1ca84e8a50e2e33763d683
commons-io-2.15.0-bin.zip=74d3db69f9cd015ae5c0a8fffe4eb2bb08a7bd1091db8d75bb7cda1e520fd690045c05e73cca5792e9589f17f3f98eab0add765d4d5cdc90f1ae6e1ace0fd4ce
commons-io-2.15.0-bom.json=ed58acb14027e9abd66676e0acbfbc3e38d832ba12e97d89479d7b9f1a931b326995e0994c66ced7ed10c890d0e5f0630b09b5814b755e6f059babe254677ab5
commons-io-2.15.0-bom.xml=2ac587fc41277f159aa2f70dc8cfd41889dc8e2cdd570540918c186b7b71be1187eae2f034352888015beea5a5058917743921e71374e9a564e29c9cc66b1b73
commons-io-2.15.0-javadoc.jar=3f214472b9d579827a23b498de30d21afe577c59bbfae668d4f42fd9419c2d341499e66bd38cbba074be72f79671dbcb30f2b151d397e90489c4a98b456cc049
commons-io-2.15.0-sources.jar=89a37db267284ba002c6cf2d570b76359f684c354e5b605c94d602f4e3f510264fb05ff2e890362ac13211164933cc640f051c9e49475156e22a833212ec505c
commons-io-2.15.0-src.tar.gz=a8df05b8da8f39408473588a8f4672dee8f4215e50e1001c0132f9bd046b32f5816f2939db471d21578e6748a5f8a998337e3adbc6dbada798d64c39ff1370d0
commons-io-2.15.0-src.zip=4d600f130dbcee703620b7916b6a34ebb36d4ec71ae00da1a1339976cec9bdcea936386b31ac7dcf2e225ac6e0ae1a13bbad0f0ea78bac4dbe4a68a73d347c8b
commons-io-2.15.0-test-sources.jar=5fab0e764cfba8165d4e608e89cee40702cd43739b23f9a5f6c86ecd78fde98f403755e362de2cdefb5ce3ab24ee4f9e049200b76bc365228bd1d5c6d850ab11
commons-io-2.15.0-tests.jar=3e402eeed7ef3093bd75deda30a41cd1a811bf2a95f974a37c4fde114234966298b69b0503ce260e25f66560828668449f7a0d0e2c885e4e5134dcac6492c37e
commons-io_commons-io-2.15.0.spdx.json=606503b5c9d7a9d865ebfea7edf9e4420c580254f47e69cf012089bf934b39bf6e99c74904693c566e0cec994d487cc0bc06d5114f5fa13eb1f38bd0e66f11d2

I have tested this with

mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy

Using:

Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
Maven home: /usr/local/Cellar/maven/3.9.5/libexec
Java version: 21, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"

Details of changes since 2.14.0 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/io/2.15.0-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/io/2.15.0-RC1/site/changes-report.html

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

JApiCmp Report (compared to 2.14.0):
    
https://dist.apache.org/repos/dist/dev/commons/io/2.15.0-RC1/site/japicmp.html

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/io/2.15.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.15.0-RC1 commons-io-2.15.0-RC1
cd commons-io-2.15.0-RC1

1b) Download and unpack the source archive from:

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

Reply via email to