We have fixed a few bugs and added some enhancements since Apache Commons
IO 2.12.0 was released, so I would like to release Apache Commons IO 2.13.0.
Apache Commons IO 2.13.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1 (svn
revision 62275)
The Git tag commons-io-2.13.0-RC1 commit for this RC is
c2f23c5ae6ebd0acd3e915f75a839b00f5b0984d which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=c2f23c5ae6ebd0acd3e915f75a839b00f5b0984d
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
commons-io-2.13.0-RC1 commons-io-2.13.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1638/commons-io/commons-io/2.13.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Jun 03 12:39:12 EDT 2023
commons-io-2.13.0-bin.tar.gz=fd6655daf94ee0bdb1bf9c840a6eecfb88a3473caf321e9eb081fe2e2caf59fdb12e9671c7aa82e54266dc15244e46943df91883d78bd3d0d69b5657616e9a0a
commons-io-2.13.0-bin.zip=57f8d9ccf3b78a3bffdf7128e50627828e65556dc0266929bbe1dd80c7dbe11a69f6b7b2e076ad1d14f61076f60759ceeef88c3af38ad515746bfeec581e4ffb
commons-io-2.13.0-bom.json=f2de674c1f45ed35c8dbf66647211ba9f06e4933c0ea9cbf6de2f792c3d9d816b0164f40900023f8b1f481515d161d3fe974243725f2682f5576fceb9625300c
commons-io-2.13.0-bom.xml=e7ef941130dd16e200bb5dab29a7f34a1a9b373b1544ed9bbb2d472cf45ba7ec339d4480063f2ea8d09a470f8f4afab8ab907e5860e437176bc1e46c4047de0a
commons-io-2.13.0-javadoc.jar=b5687a93d230cde63cb1073e7e55c6f1f6d0141e82cfa3b2071b6a4774a10889392285d9e8cc9fed43bbcb748205be1173c5fa23edcc71463ce59d60dce7b8a1
commons-io-2.13.0-sources.jar=e9facd7c29504211b1c21df40d0c4d43db80d203dd18139882eef03eb58cafe3b63765b7ff725f46c4ea10d52ac4a6c7d3857b7b7548c799be5102643fc7ec10
commons-io-2.13.0-src.tar.gz=187df4b73ac20caa28de99381b32f46673ee5a3b519e6804e6cd8ced49412ba89dd6f5cf43e4cfb54c221331cefa1ed20a180d8c9f0e4c361b4b9a2e98b26017
commons-io-2.13.0-src.zip=e92812ceb9e1c31b437d241ed44f11253b9f9e90772062c9f9ed165520e8d8003c50b85e9c5f5ed69ed83ccb77a705188d733e880dcade1fb0ebc655983d0d2b
commons-io-2.13.0-test-sources.jar=9aca47ee983d40228abb3c357de905a0f277e40bd26eed6eda9f71bfbd690bd9759e1a930fdd6f83e3e284844eae9f00bf23e71123e84e11bf7a004632504aa1
commons-io-2.13.0-tests.jar=e9df13feaa6ed0d0ae918568cf78e372887d40368f8676c505a1f9aa5cc10a088b6ca5c964370ba9f95a36a69fa5e07647a686da4477aaa2a28ba5bf1db9f7d6
commons-io_commons-io-2.13.0.spdx.json=94f3ad040d89cac2814df45c3310fc76c259e4762ae525a84f00adc306c05d6647da560a759d70ad5dddee0ac230c925928545ce73af7ae24579c0e3bfa3af63
I have tested this with
mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
deploy
Using:
Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
Maven home: /usr/local/Cellar/maven/3.9.2/libexec
Java version: 1.8.0_372, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+372/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.4", arch: "x86_64", family: "mac"
Darwin **** 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:51:50 PDT
2023; root:xnu-8796.121.2~5/RELEASE_X86_64 x86_64
Details of changes since 2.12.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/site/index.html
(note some *relative* links are broken and the 2.13.0 directories are
not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 2.12.0):
https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/site/rat-report.html
KEYS:
https://www.apache.org/dist/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.
1) Clone and checkout the RC tag
git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
commons-io-2.13.0-RC1 commons-io-2.13.0-RC1
cd commons-io-2.13.0-RC1
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-
