[+1] Go ahead with the release.

Tomas Lanik


On Mon, Jul 14, 2025, 23:37 Gary Gregory <garydgreg...@gmail.com> wrote:

> We have fixed a few bugs and added enhancements since Apache Commons
> IO 2.19.0 was released, so I would like to release Apache Commons IO
> 2.20.0.
>
> Apache Commons IO 2.20.0 RC1 is available for review here:
>     https://dist.apache.org/repos/dist/dev/commons/io/2.20.0-RC1 (svn
> revision 78176)
>
> The Git tag commons-io-2.20.0-RC1 commit for this RC is
> c224bce839494ed651e5eba320b27c73ce8d804e which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=c224bce839494ed651e5eba320b27c73ce8d804e
> You may checkout this tag using:
>     git clone https://gitbox.apache.org/repos/asf/commons-io.git
> --branch commons-io-2.20.0-RC1 commons-io-2.20.0-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1846/commons-io/commons-io/2.20.0/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Mon Jul 14 21:29:47 UTC 2025
>
> commons-io-2.20.0-bin.tar.gz=0bd8e82292b3a77b15baac38716e9b0e5fea4125f6b83c055aca4c1c7ded5dbc217c2d9b7ada9b8989f803501fc86655776abf3ceab9c0b8facf16044bcbe126
>
> commons-io-2.20.0-bin.zip=c60c7b25095969c59da844eae6a5985a5edfcb95f695b5386c9ce13ec875c9577103e82f02da94329b83d6e1eef48093370b3a0ec6539c6b22de0ef1c729204b
>
> commons-io-2.20.0-bom.json=9f79980fe381da8ea4167fcb1726ab1dca26505ca0f91924da44632bfd092ac4de0eddbed400e9ca10b19bd1fd8681c04cef0e1f616aa949163fde63e8ecfe20
>
> commons-io-2.20.0-bom.xml=3886722c7e22306fe16a0037e79a50a138d9f1c496deaa3fd691700e9ed42877fd1d1e707dc4118530d3905fb76f158289b19db50f9d4cd27f566a42be4fa268
>
> commons-io-2.20.0-javadoc.jar=86e0c8e4f0dace7fce4e2423b563e821e73b2deb6a33a419d46ffffffbd8bb99d0eef128faef276f8538fc060926b7b810aed88a2620de836284e8f17fad028a
>
> commons-io-2.20.0-sources.jar=7d0f09c4f2ff502329d5e90583eb620ddc266520114a4ea401206c6d2b6ebc0332fca79ad2ddab1eb820769dfe3cdbb52d6d16b2e6c893b8d0cd679c53f26706
>
> commons-io-2.20.0-src.tar.gz=4c05970ad34e2aa32dc07de3b3335f46bb069dcb6f28fc6ed82867d890d4f31d6dfb5edb03ec3333f789f9ac0a57d84b5ffa782bd715ccffed41b1a9004217fb
>
> commons-io-2.20.0-src.zip=d6031232bda58a49d66e5ec2f26b24c955da226f088e4829e52b28337f094c648978147ae5ce592f2f98bb3f9979d1c956246794fed9401ae456ea7067ee8a8d
>
> commons-io-2.20.0-test-sources.jar=2ba7637dc1feca5b6ef46220dfd72fd0e6f0c6ea0d93c026eea7b3c4c9feb28bac0e7476995000930e1c33f79370fde2a44fa726664120e81ff5343ff67f93ff
>
> commons-io-2.20.0-tests.jar=8036d183275a8352149bc98b03374b51a6dc527c7ca425ef2e4b5bba6adc62eadbc22c0faf9d2c60c3c006011fc0c6ba15dc759aca0ec33003bf846dd6bcd6c8
>
> commons-io_commons-io-2.20.0.spdx.json=13f1ced7758f811430dfa271d6cada1ddd36fa2df9c8f0518216b6c1318263fba4986d2c70b152fccc101244e34a6547219030a361bf36c06bec3dadfd4f1e03
>
>
>
> I have tested this with 'mvn' and 'mvn clean install site' using:
>
> openjdk version "21.0.7" 2025-04-15
> OpenJDK Runtime Environment Homebrew (build 21.0.7)
> OpenJDK 64-Bit Server VM Homebrew (build 21.0.7, mixed mode, sharing)
>
> Apache Maven 3.9.10 (5f519b97e944483d878815739f519b2eade0a91d)
> Maven home: /opt/homebrew/Cellar/maven/3.9.10/libexec
> Java version: 21.0.7, vendor: Homebrew, runtime:
> /opt/homebrew/Cellar/openjdk@21/21.0.7/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac"
>
> Darwin ****.local 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22
> 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64
>
> Docker version 28.3.0, build 38b7060
>
> Details of changes since 2.19.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.20.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.20.0-RC1/site/changes.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.20.0-RC1/site/index.html
>     (note some *relative* links are broken and the 2.20.0 directories
> are not yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 2.19.0):
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.20.0-RC1/site/japicmp.html
>
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.20.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)
>
> The following is intended as a helper and refresher for reviewers.
>
> Validating a release candidate
> ==============================
>
> These guidelines are NOT complete.
>
> Requirements: Git, Java, and Maven.
>
> You can validate a release from a release candidate (RC) tag as follows.
>
> 1a) Download and decompress the source archive from:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.20.0-RC1/source
>
> 1b) Check out the RC tag from git (optional)
>
> This is optional, as a reviewer must check source distributions as a
> minimum.
>
> git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
> commons-io-2.20.0-RC1 commons-io-2.20.0-RC1
> cd commons-io-2.20.0-RC1
>
> 2) Checking the build
>
> All components should include a default Maven goal, such that you can
> run 'mvn' from the command line by itself.
>
> 2) Check Apache licenses
>
> This step is not required if the site includes a RAT report page which
> you then must check.
> This check should be included in the default Maven build, but you can
> check it with:
>
> mvn apache-rat:check
>
> 3) Check binary compatibility
>
> This step is not required if the site includes a JApiCmp report page
> which you then must check.
> This check should be included in the default Maven build, but you can
> check it with:
>
> mvn verify -DskipTests -P japicmp japicmp:cmp
>
> 4) Build the package
>
> This check should be included in the default Maven build, but you can
> check it with:
>
> 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
>
> 4b) Check reproducibility
>
> To check that a build is reproducible, run:
>
> mvn clean verify artifact:compare -DskipTests
> -Dreference.repo=
> https://repository.apache.org/content/repositories/staging/
> '-Dbuildinfo.ignore=*/*.spdx.json'
>
> Note that this excludes SPDX files from the check.
>
> 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