We have fixed quite a few bugs and added some significant enhancements
since Apache Commons IO 2.6 was released, so I would like to release Apache
Commons IO 2.7.
Apache Commons IO 2.7 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/io/2.7-RC1 (svn revision
39753)
The Git tag commons-io-2.7-RC1 commit for this RC is
6efbccc88318d15c0f5fdcfa0b87e3dc980dca22 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=6efbccc88318d15c0f5fdcfa0b87e3dc980dca22
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
commons-io-2.7-RC1 commons-io-2.7-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1498/commons-io/commons-io/2.7/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun May 24 16:10:47 EDT 2020
commons-io-2.7-bin.tar.gz=5bcb609bd0e1e96665ff06529b29cb35e77358e49cf9230a5b71202c616250bc045777a0f64428ef4be17211dff5e24116f6764d41e0aa3d249f048d344debf4
commons-io-2.7-bin.zip=32dfa4621204d48fe51c32ccdda87c3864bea5b88ff910b00d197aa698e69135ea003e9c7559085e1cd20580a739173fb62cc6514320094a614b36a5e35d9ab1
commons-io-2.7-javadoc.jar=230c9e7747d060574ffe0a4ad09cba17e8194a24c652352b350194ec63924fa4251e0cd8e9cdb5d752906256ae030750251a0d5c39e97d460c802b2197a432cc
commons-io-2.7-sources.jar=d8fd208cb67b31f8ce6f6cfa1cf55e66709503f435aeaf5c5102d82eda0da5c79d30058647e9a37c6f49e9b982a22ed98492e00e45155f03a6b126e0de29f4ea
commons-io-2.7-src.tar.gz=9898b59c2aebdc1c51a7f8aca14e3080a08b766404c2aff091b204ba55870129dd95643665a6d46e15e94cd9d4cb280488ab0a28a1c51f43d132f839b742edc3
commons-io-2.7-src.zip=a635c0345690aebe57dd74dfbef12581addaebc6d973c8d7ef174e1d67b2f824260a52cd005012f0efbac465f7ef3681f01f1cdb23c7d28202acc080a8703c41
commons-io-2.7-test-sources.jar=91d07cd12747cd2daeb399f330f565eff4d3919c00aad283b18bbd66417384402fa9a0ebb608fd0ad2482c2d214c016ead57de2288a0da7055faca229c3cee55
commons-io-2.7-tests.jar=2eaaa3280d7e95a8eed1308b97b0b2666b818ba644a23e37b0394498733f92ba412bf664248559616f708b6e222b439e6201d4cf4aedfdc62f65c72b0784567d
commons-io-2.7.jar.asc=e00353543e02498efb3536bedb564bd40864cf5cc6414ec99336b657e021c50365cba978bb7619ddd06252699855cb58b79c9b36e258a11dca9744b16ab6d741
I have tested this with:
mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
deploy
using:
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Java\apache-maven-3.6.3\bin\..
Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_251\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
Details of changes since 2.6 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/io/2.7-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/io/2.7-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/io/2.7-RC1/site/index.html
(note some *relative* links are broken and the 2.7 directories are not
yet created - these will be OK once the site is deployed.)
JApiCmp Report (compared to 2.6):
https://dist.apache.org/repos/dist/dev/commons/io/2.7-RC1/site/japicmp.html
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/io/2.7-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 that 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.7-RC1 commons-io-2.7-RC1
cd commons-io-2.7-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-
