My +1

> On Apr 22, 2025, at 5:48 PM, Rob Tompkins <chtom...@apache.org> wrote:
> 
> Hi all,
> 
> We have fixed a few bugs and added enhancements since Apache Commons 
> Configuration 2.11.0 was released, so I would like to release Apache Commons 
> Configuration 2.12.0.
> 
> Apache Commons Configuration 2.12.0 RC1 is available for review here:
>    https://dist.apache.org/repos/dist/dev/commons/configuration/2.12.0-RC1 
> (svn revision 76445)
> 
> The Git tag commons-configuration-2.12.0-RC1 commit for this RC is 
> 0dc817d3d665bd8c6faee626cfc505d1ae527322 which you can browse here:
>    
> https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=0dc817d3d665bd8c6faee626cfc505d1ae527322
> You may checkout this tag using:
>    git clone https://gitbox.apache.org/repos/asf/commons-configuration.git 
> --branch commons-configuration-2.12.0-RC1 commons-configuration-2.12.0-RC1
> 
> Maven artifacts are here:
>    
> https://repository.apache.org/content/repositories/orgapachecommons-1831/org/apache/commons/commons-configuration2/2.12.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Tue Apr 22 17:36:46 EDT 2025
> commons-configuration2-2.12.0-bin.tar.gz=ce7d27956ddff85676b4f76e06e39763b07c3e296dc2ad6668dd42915242574943b68658fedc5d3ba7d24b1ccc8afa2e33ef4018ad378529616be34f55235da1
> commons-configuration2-2.12.0-bin.zip=cbec1cb00f80dc2700f83075058ae34dbe6de8303ab2e008143d34621612c4da368d6aa89428c6880e8d3e520999a1d7dd525c6e1b7eae40bb50c57e03627157
> commons-configuration2-2.12.0-bom.json=66f8fe59e6d7e4206cf39f77be430eb472a1755c901a3e1335a67db1be2d2b46628e8f048f08aa8d165dbc6b6218eba03ee6b9b399ccce19de5e1fbbcab514e0
> commons-configuration2-2.12.0-bom.xml=d6d19154ac92f9df3c47235eacc6e99b9e628155d8e6891d657e9cbbfbd057da8634a778481e1fb3e05a69c3a39f5d241bd5f78f7796243b0cc6821690bfd92d
> commons-configuration2-2.12.0-javadoc.jar=98dfa030748cf05b08a4c91e3e5408bae2028c4bcadbcb7ad3378cf78c14cb4385e8788413ee8278d4637b25514684822ca106cf69eb484cfad17fadfd68b943
> commons-configuration2-2.12.0-sources.jar=cb70b0d0ac63d5da58fab6eb02fd53190834bccd300d4137cb19bea1a064a2a7c82fdf09ec4a175c57cc164dcad4d40313d1121391563cb374631711830a7f46
> commons-configuration2-2.12.0-src.tar.gz=d58c653e36d0c9db9152eb0f9cf69861346c35bfa5936e3d8c76f8becc7af08988f9ec5dd1e9cd44125b262fde9d619992bf47d1674f29c80cb87739222a98f1
> commons-configuration2-2.12.0-src.zip=6621d130fb21ab1d021141cde0e77be5f40c4dd995163c7a0aa0815ef7dc5a3f3a3487a0ae4b88ec3aa391457272e2b7f760fc832051d01e6d390f09dbb9c02b
> commons-configuration2-2.12.0-test-sources.jar=eecf2c2daa5286204d6be3059acd90592b25b407ed6c31352a7ecd239f1bb3b52d5c4c78a9173bc5e06828110d7d31ed9e8e246a582768d06d48214e2845d385
> commons-configuration2-2.12.0-tests.jar=4cfb1df42f4ed9be0badda66e54a29424f3ac2792eb5c8745774ffd28164baac90802a35bc983b86ef137ccd930ba909435653f7fd1a0c4750b0acbfbd7a24ff
> org.apache.commons_commons-configuration2-2.12.0.spdx.json=bebf52f81f0fae92908da995cad3e0d373b4858a98d79a38edf637408e8c2678143fcbde342409b5b5d24f8fd442f370912a8c724e9e6cd8f18d54f7870228a1
> 
> 
> 
> I have tested this with 'mvn clean test install site' using:
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /usr/local/Cellar/maven/3.9.9/libexec
> Java version: 21.0.6, vendor: Amazon.com Inc., runtime: 
> /Library/Java/JavaVirtualMachines/amazon-corretto-21.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "15.3.2", arch: "x86_64", family: "mac"
> 
> Details of changes since 2.11.0 are in the release notes:
>    
> https://dist.apache.org/repos/dist/dev/commons/configuration/2.12.0-RC1/RELEASE-NOTES.txt
>    
> https://dist.apache.org/repos/dist/dev/commons/configuration/2.12.0-RC1/site/changes.html
> 
> Site:
>    
> https://dist.apache.org/repos/dist/dev/commons/configuration/2.12.0-RC1/site/index.html
>    (note some *relative* links are broken and the 2.12.0 directories are not 
> yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.11.0):
>    
> https://dist.apache.org/repos/dist/dev/commons/configuration/2.12.0-RC1/site/japicmp.html
> 
> RAT Report:
>    
> https://dist.apache.org/repos/dist/dev/commons/configuration/2.12.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,
> 
> Rob Tompkins,
> Release Manager (using key 5ECBB314)
> 
> The 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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-configuration.git 
> --branch commons-configuration-2.12.0-RC1 commons-configuration-2.12.0-RC1
> cd commons-configuration-2.12.0-RC1
> 
> 1b) Download and unpack the source archive from:
> 
> https://dist.apache.org/repos/dist/dev/commons/configuration/2.12.0-RC1/source
> 
> 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
> 
> 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-
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to