[x] +1 Release these artifacts

Building OK with JDK 11 and Maven 3.6.3. Reports look good. Inspected dist area 
archives and found no issues.

Thanks Gary!

Bruno


    On Saturday, 10 July 2021, 1:52:51 pm NZST, Gary Gregory 
<garydgreg...@gmail.com> wrote:  
 
 We have fixed a few bugs and added some enhancements since Apache Commons
IO 2.10.0 was released, so I would like to release Apache Commons IO 2.11.0.

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

The Git tag commons-io-2.11.0-RC1 commit for this RC is
8985de8fe74f6622a419b37a6eed0dbc484dc128 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=8985de8fe74f6622a419b37a6eed0dbc484dc128
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
commons-io-2.11.0-RC1 commons-io-2.11.0-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1555/commons-io/commons-io/2.11.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Fri Jul 09 21:42:55 EDT 2021
commons-io-2.11.0-bin.tar.gz=b28938f197f29a7145f6e43e41b917ebd98bd6ba308e3b7ba85a455b77e3e5a7d62beac1a83e20246ac07ba19048fb4f952e3f5323c714f2b515dd94a1524d46
commons-io-2.11.0-bin.zip=0aedf61b2cc8c9464dcf2eda7826e4a8f8f83db98b3e908d3ec00fefd07a07fd51d2be868732cc2d2a57804e714e15af384bd4522c463719d033ca0925e5dc95
commons-io-2.11.0-javadoc.jar=a657ad8ce37d6391f0b99110d497fbf19330d1f7e32df25ab461857b5b15d370bfe4fe2e7f751bfc43752bd695f053f8bf5e14673a178caea39aec5bf1064616
commons-io-2.11.0-sources.jar=c4364f695d7cbf7de476c74546d0a9413181fce93fc87e72e30fb85ebc718982c9b3048d8d172a88e9a835cb15d64d4d0025108bdf6d43a8c42737b38772087f
commons-io-2.11.0-src.tar.gz=e2ab8ebc9c328093a460f8f5f96c80bb45f5073ec7aaa0beabdcdeac2e97324292eab2e2cb8b64d8e78b2c5d89048ba84e50daa0965dffcbe2fd0da7ab789ee3
commons-io-2.11.0-src.zip=055313d358ee9e0fee5404b062b2ceeaf4ec3a6ec7ae35e0a8f24656112716634985ce185572c215637566ec9302e8588bd261235638e30a5b9c9b40d729165d
commons-io-2.11.0-test-sources.jar=ca7d5e72f52760edabcc61674ad0740292d5a443a86ae4c9f1b64929ffb4f2d685d6b868d6c9cae6e95080b320150707f3308bfad07f996e38093d453562ace6
commons-io-2.11.0-tests.jar=e4c47d94dd099bc772c5e643ee63ebdc6086e2505349f57e561dd88621869ac68aabb3c963a0a386ce060bee13032e2230400cdd52736614acf3a2db48605ada


I have tested this with the default Maven goal 'mvn' and 'mvn -V
-Duser.name=$my_apache_id
-Dcommons.release-plugin.version=$commons_release_plugin_version -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"

Darwin gdg-mac-mini.local 20.5.0 Darwin Kernel Version 20.5.0: Sat May  8
05:10:33 PDT 2021; root:xnu-7195.121.3~9/RELEASE_X86_64 x86_64

Details of changes since 2.10.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/io/2.11.0-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/io/2.11.0-RC1/site/changes-report.html

Site:

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

JApiCmp Report (compared to 2.10.0):

https://dist.apache.org/repos/dist/dev/commons/io/2.11.0-RC1/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/io/2.11.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.11.0-RC1 commons-io-2.11.0-RC1
cd commons-io-2.11.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-
  

Reply via email to