My +1. Gary
On Thu, May 21, 2026, 10:28 Gary Gregory <[email protected]> wrote: > [VOTE] Release Apache Commons Configuration 2.15.1 based on RC2 > > We have fixed 2 bugs since the release of Apache Commons Configuration > 2.15.0, so I would like to release Apache Commons Configuration > 2.15.1. > > Apache Commons Configuration 2.15.1 RC2 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC2 > (svn revision 84665) > > The Git tag commons-configuration-2.15.1-RC2 commit for this RC is > 51f8140ab63e2904c6a5c46fecf841fd5e34c492, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=51f8140ab63e2904c6a5c46fecf841fd5e34c492 > You may checkout this tag using: > git clone > https://gitbox.apache.org/repos/asf/commons-configuration.git > --branch > <https://gitbox.apache.org/repos/asf/commons-configuration.git--branch> > commons-configuration-2.15.1-RC2 > commons-configuration-2.15.1-RC2 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1941/org/apache/commons/commons-configuration2/2.15.1/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Thu May 21 14:18:26 UTC 2026 > > commons-configuration2-2.15.1-bin.tar.gz=4c17de44fa9180ac5bce2b4db6ad794a07b72d960309f7dd38db076649bd5652363c7475cd46614aeec3bda94a3492ea68785fd779c57989547aa9b3b67ea98a > > commons-configuration2-2.15.1-bin.zip=7992f89a79c9f4f03eed3b01189a65c9f3c2abe17fdefa74997034a6e290da794cb25e68daa0cf47c5601db2117bcef68e579e3be89da1ed02694d011690d4da > > commons-configuration2-2.15.1-bom.json=9fc27a1427f7e00995469cd84e9255a3352be01502bfc7f62ca030bb918bc32aeda9ed1bbf6bb916e6ae764683f5446d9721f746d9e1fe1473a2df7babaf6ce3 > > commons-configuration2-2.15.1-bom.xml=a3a2e0da3df209672cb93d794afe67ba01cf4e5247c75075dc6c14aefd336f2079d387e6e8fa70ea67e280485236ea3d42673c0b8f31df21a1cdf13c586acefe > > commons-configuration2-2.15.1-javadoc.jar=f6aa016a723a9173a3cd746684e6bba676eae86b818061fb64770034eae37dd18e82bbd43ecd5fb495077bf1a708f2aac4633e6a2bd891d4d9a0b792b93329b0 > > commons-configuration2-2.15.1-sources.jar=a25d6b545bc14cb99175b92b246dae212e6450f2704afbfc3a6cb31ab0fd4086381ccb67d1ca5655d3a76c295de1d018d6ce20908225e9ad823b8155d66447d2 > > commons-configuration2-2.15.1-src.tar.gz=5d270df2decef297c2051f5e72f31d73ee53161e6823a650ab0cbbb36e18b01cfce5c237eb8d6e2787d5e5ce7e5707bed0127b464da50b1b959a386065f6c292 > > commons-configuration2-2.15.1-src.zip=f6db154456ab60cb9b9eb903373a136ecf22a1e3a1f95817b12b6ba022f5c04a8999837f8331a2bb5c8e6c492b14649f686ba9438683c7b27ac6e75f159bbcfb > > commons-configuration2-2.15.1-test-sources.jar=907186e932d7050d107c16d105cc80f50312c205d7514db3e4738fb239d9c54a2e5d5853797bc9a60edbf33212a57991f36efd1607a07714afc738000800814e > > commons-configuration2-2.15.1-tests.jar=d0ab8ce7f89092d38648f6a58f1096e9971809c516462a3a8a7319c5ca338c8e20c1b09861bf00f46cd7f9168abbd3c4649d2804f8a3a895314876207dbf8562 > > org.apache.commons_commons-configuration2-2.15.1.spdx.json=4321c58c72512de195b75c1bd41ef46d29725c651d93553d279beaaa61bab330730ead08d57ed6e052673a5bff840e8e9c6d137530bcdd4d2ffa8506617cf0c0 > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.11" 2026-04-21 > OpenJDK Runtime Environment Homebrew (build 21.0.11) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.11, mixed mode, sharing) > > Apache Maven 3.9.16 (2bdd9fddda4b155ebf8000e807eb73fd829a51d5) > Maven home: /opt/homebrew/Cellar/maven/3.9.16/libexec > Java version: 21.0.11, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.11/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.5", arch: "aarch64", family: "mac" > > Darwin Garys-MacBook-Pro.local 25.5.0 Darwin Kernel Version 25.5.0: > Mon Apr 27 20:41:15 PDT 2026; > root:xnu-12377.121.6~2/RELEASE_ARM64_T6041 arm64 > > Docker version 29.4.3, build 055a478 > > > Details of changes since 2.15.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC2/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC2/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC2/site/index.html > (Note some *relative* links are broken and the 2.15.1 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.15.0): > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC2/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.15.1-RC2/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.15.1-RC2/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must at least check source distributions. > > git clone https://gitbox.apache.org/repos/asf/commons-configuration.git > --branch > <https://gitbox.apache.org/repos/asf/commons-configuration.git--branch> > commons-configuration-2.15.1-RC2 > commons-configuration-2.15.1-RC2 > cd commons-configuration-2.15.1-RC2 > > 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 > > 6) Build the site for a multi-module project > > mvn site > mvn site:stage > Check the site reports in: > - Windows: target\site\index.html > - Linux: target/site/index.html > > Note that the project reports are created for each module. > Modules can be accessed using the 'Project Modules' link under > the 'Project Information' menu (see <path-to-site>/modules.html). > > -the end- >
