My +1 Gary
On Fri, Nov 21, 2025 at 8:31 AM Gary Gregory <[email protected]> wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > Configuration 2.12.0 was released, so I would like to release Apache > Commons Configuration 2.13.0. > > Apache Commons Configuration 2.13.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/configuration/2.13.0-RC1 > (svn revision 80905) > > The Git tag commons-configuration-2.13.0-RC1 commit for this RC is > b0839875c7c1c442f1733f6143a326597dbd04c0 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=b0839875c7c1c442f1733f6143a326597dbd04c0 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-configuration.git > --branch commons-configuration-2.13.0-RC1 > commons-configuration-2.13.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1884/org/apache/commons/commons-configuration2/2.13.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri Nov 21 13:23:20 UTC 2025 > commons-configuration2-2.13.0-bin.tar.gz=7078056ca7dcd9b5aa50d0c9c5a11ac8ede78b2289d4a80b2af319af6947e429124a14a8782253a423400e9a377019365740dd8faceedb0a800fad95ce4ba776 > commons-configuration2-2.13.0-bin.zip=281554fb96e58c48f3c914e9f8cb85f3cc3ff6429947b6d8bf0be30305d2155a7dda8abf7d99db586f5f42666e1715b1a25de7a70b21cae7ae94d09bef823e13 > commons-configuration2-2.13.0-bom.json=162e707fb45b6a3a6270d56d24205067b640abe9ef7091eb2284c559721d7a8b52396d39087ebbdac3f0b1fda20acfdfbc68c8aaafe38fb350358b3cfd59b8e8 > commons-configuration2-2.13.0-bom.xml=937b2c540d610ba1987a876222d679a59b7fb492307b922f7bcda922710f68ec9f8944348c4aa67cc5e3a688fc9e44a6a21701208740d2b49e40716d0e8307a5 > commons-configuration2-2.13.0-javadoc.jar=a1afc396505e6627001e272627db7cc35e942fe29e5fb6818383ad2ba7821a495856e9020f5cc1a6c098d566ad7920ecdb412332558c2a8747ab0559e9588a0a > commons-configuration2-2.13.0-sources.jar=29c8db049a9bdf3a6fa0f06a4f852c11dd880548552475d3afb2c066c247614f957ce391738f075c14ac472e23447810a354b6992a63762897e65438dab339da > commons-configuration2-2.13.0-src.tar.gz=0efc3303c9d682d93b8d2eaca0904bca07c3187e3034b4dd9403f95d7208ae96f9c1b0015b192c974804de5a80b3010674b9384e183560d483259607d0bcfe8f > commons-configuration2-2.13.0-src.zip=6f6515031d2338617946d8f0554b9b29d3bc0b51f6f267d76993951dc0b586d42d5d3e37a340178a67c18bc3921f1bd6c891f10844e94f01869850217c36ecdb > commons-configuration2-2.13.0-test-sources.jar=a8b9625acdcddec5cf9f11acff55d451ae0203afaca2ce5391ab54f70c905ea9c3350a73c78cbe39f0f50679bff218cadc016391a159fba42157c87d608f86bf > commons-configuration2-2.13.0-tests.jar=53e60058caab92594171630f435c5e41eacc7cad315e1fff48409216f463b33efb09ffb5ae13a495ff61c4f9a530bc2b2b314e0e2b7888bb1d522cc051230d48 > org.apache.commons_commons-configuration2-2.13.0.spdx.json=f5508c56194b9b40f97aba376c2de2ca427df637863352ba8b01d9ca4904442e845c7ea3c7ca01b6be334b22bcb6e5c2af503cd4c5951e9a02c9b000bf0c5d15 > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.9" 2025-10-21 > OpenJDK Runtime Environment Homebrew (build 21.0.9) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.9, mixed mode, sharing) > > Apache Maven 3.9.11 (3e54c93a704957b63ee3494413a2b544fd3d825b) > Maven home: /opt/homebrew/Cellar/maven/3.9.11/libexec > Java version: 21.0.9, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.9/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.7.2", arch: "aarch64", family: "mac" > > Darwin ****-MacBook-Pro.local 24.6.0 Darwin Kernel Version 24.6.0: Wed > Oct 15 21:12:15 PDT 2025; > root:xnu-11417.140.69.703.14~1/RELEASE_ARM64_T6041 arm64 > > Docker version 28.4.0, build d8eb465 > > Details of changes since 2.12.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.13.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.13.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/configuration/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/configuration/2.13.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.13.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 530AA5F25C25011F) > > 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/configuration/2.13.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-configuration.git > --branch commons-configuration-2.13.0-RC1 > commons-configuration-2.13.0-RC1 > cd commons-configuration-2.13.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: [email protected] For additional commands, e-mail: [email protected]
