My +1 > On Apr 16, 2025, at 10:26 PM, Rob Tompkins <chtom...@apache.org> wrote: > > Hello 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.11.1. > > Apache Commons Configuration 2.11.1 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.1-RC1 > (svn revision 76324) > > The Git tag commons-configuration-2.11.1-RC1 commit for this RC is > 99e199f063107a37ce14af21d1dccd6b301bc613 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=99e199f063107a37ce14af21d1dccd6b301bc613 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-configuration.git > --branch commons-configuration-2.11.1-RC1 commons-configuration-2.11.1-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1828/org/apache/commons/commons-configuration2/2.11.1/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Wed Apr 16 22:17:44 EDT 2025 > commons-configuration2-2.11.1-bin.tar.gz=b56aa7893c69e7de0d9d6b7665513d9f11f49d693e631c9f964b1dc7ea5ac8f0875d0061a45dfa7e2d2a268e2025057ff5ad4152599361bcd387adac8119d598 > commons-configuration2-2.11.1-bin.zip=f94df0921cbf8de8453ee5750a2c11bdcaae8a59a14cb57a14aec315f4804385b944dda784e2f016414c796f93e4eaadde386cf3a137d809f733181ea65eb179 > commons-configuration2-2.11.1-bom.json=6eade4dbfa161a7f76472d3998f55414f354a011596cd3ee803a85f6e8e2b94fa821f399865330dbbd8a5bc98cd43a67bf6172df4475fcc611177945b186412f > commons-configuration2-2.11.1-bom.xml=d044fe5836b2e311a5f89c50404e2eeb711497bb72cfb2507a2aa2f8abb191bf1c44ba8cd4da09904a1eab8b20908d59cb54e561ddd5ebfd0e1150fcf12e3e21 > commons-configuration2-2.11.1-javadoc.jar=44a67d7ab8d2465e473462ba167b8db25bae362e48e8b60b33b91528d0e8b7889eaa90c8c1971a693e566d0bd2d6e26f06023957c9407fe7a32f1f78778647a0 > commons-configuration2-2.11.1-sources.jar=b02090d90aff05c27cb7d18d485866eb06fad7b0b2fbf1cdd53bca27117f0ff258061e93b00d57394587cd61a33da9c48a89d2c7f61aacf6e9cb0fc9007ff061 > commons-configuration2-2.11.1-src.tar.gz=8116b7c3eddf27b31925d2fe92ba5980f5d3f9c1a931d5498889365543493b67fd3006560ffe879b7fa56614058e8451edf309a443c3a506c01db54c7d4dd690 > commons-configuration2-2.11.1-src.zip=290c94ac2ae4bb563da2ebbe43a571bdea7c7130bff8333807c7204543d8ccc254b6421133c292962505467dc30c4d98345098daa1c3f1968393e0f17f2e7b8d > commons-configuration2-2.11.1-test-sources.jar=4ecf6dfeccbe9d8a44cd94b3856c95a389e423dc2988cbc401ec5da427388650385cbe3ae77ce727803950807f16f1ef06c886a5d30076cbd2428826e414b674 > commons-configuration2-2.11.1-tests.jar=abbfa1a0e83820756f6a157bd1a025c8d3e86351e3622d4015ea360d78bce57da4052c286c93943f62e1b8a6a0115350bb3c672b8e310e2b25dbfb61fa01cad7 > org.apache.commons_commons-configuration2-2.11.1.spdx.json=2ba07150b9a1a4a80a6f4b449b8ebdf287e0cfeb9e5bbd12aff08d0e1604061b3479665c67008a9e5edc08f81485a31b6c0946d39d2d9e01187006a4344b8018 > > > > I have tested this with ***'mvn clean 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.11.1-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.1-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.1-RC1/site/index.html > (note some *relative* links are broken and the 2.11.1 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.11.1-RC1/site/japicmp.html > > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.1-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, > 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.11.1-RC1 commons-configuration-2.11.1-RC1 > cd commons-configuration-2.11.1-RC1 > > 1b) Download and unpack the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.1-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
