We have fixed a few bugs and added some enhancements since Apache
Commons IO 2.9.0 was released, so I would like to release Apache
Commons IO 2.10.0.
Apache Commons IO 2.10.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1 (svn
revision 48259)
The Git tag commons-io-2.10.0-RC1 commit for this RC is
a73895fbefd57c23595a5e9e85f0649993c59080 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=a73895fbefd57c23595a5e9e85f0649993c59080
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-io.git
--branch commons-io-2.10.0-RC1 commons-io-2.10.0-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1551/commons-io/commons-io/2.10.0/
These are the artifacts and their hashes:
#Release SHA-512s
#Thu Jun 10 08:43:37 EDT 2021
commons-io-2.10.0-bin.tar.gz=14c08c93379e975ca28723086acc4c1ba9acb99ed4a36e21ea6cdf9eeebac53cb08f5f606ade69daa58af4aa7c56b4b286cf96d36604139d5de9ee3902fc09b9
commons-io-2.10.0-bin.zip=a5e32c8dbf76779247fb233646631e213b125c655a299edea895dfaddd86672fbe91396c548100b4d35d5647005066850243704d751d25028ecd13cafc3f36d8
commons-io-2.10.0-javadoc.jar=ecdd571aa8de94e41c1d507384fddcd52d845687b10471ef5641033040d4209eed28c5018bd2e3283233132c70ad9188c604c586e36f4bbb93fe748c4713ebc7
commons-io-2.10.0-sources.jar=8152939638af55595858a7214e9a38804911b1f8e7a7a9d49c1456e258577bfc72671915d33c05d33e40f41c14e0090ddc2789e7ba0020c8f391448ae14d735d
commons-io-2.10.0-src.tar.gz=227a2293c4e0ab209da1a78db07e93a940c45393dfc48764552c432c37bed974f1cff6379edd4240bec8d635919e4a7008ce39687ce43ae3463cee42337a3335
commons-io-2.10.0-src.zip=6f6088ec14c896ea84b4e31867925d51b770c7750d7ca108296b778fa0b45fe70514a3f590ad1f00343ad5adb7882d9a905237f30a07058c5ab80e51b072f402
commons-io-2.10.0-test-sources.jar=2591d6038d829f3ec0b58a00bc4e884ce37ebace91a7ec7cad364419d13bebec5a98a7cadb8fa2534f9f98a1b0718bb669311125054f2ace85c985c1f074ee2d
commons-io-2.10.0-tests.jar=b5eddbdc6c2b335e1afc08ce64acc9a008396839384fcdb61790d536eb96e5d920cfb213eaeee9b9d8368d45f9f2c0b9625babaf2c0ac1ee6c4d68c977461061
I have tested this with 'mvn -V -Prelease -Ptest-deploy -P jacoco -P
japicmp clean package site deploy' using:
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: /usr/local/Cellar/maven/3.8.1/libexec
Java version: 1.8.0_292, vendor: AdoptOpenJDK, runtime:
/Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
Details of changes since 2.9.0 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/index.html
(note some *relative* links are broken and the 2.10.0 directories
are not yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 2.9.0):
https://dist.apache.org/repos/dist/dev/commons/io/2.10.0-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/io/2.10.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.10.0-RC1 commons-io-2.10.0-RC1
cd commons-io-2.10.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-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
