+1 > On Mar 18, 2024, at 9:35 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > My +1 > > Gary > >> On Sun, Mar 17, 2024 at 4:36 PM Gary Gregory <garydgreg...@gmail.com> wrote: >> >> We have fixed a few bugs since Apache Commons Configuration 2.10.0 was >> released, so I would like to release Apache Commons Configuration >> 2.10.1. >> >> Apache Commons Configuration 2.10.1 RC1 is available for review here: >> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1 >> (svn revision 67980) >> >> The Git tag commons-configuration-2.10.1-RC1 commit for this RC is >> 81573fa387435e985cc05356c33c49273fc4a018 which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=81573fa387435e985cc05356c33c49273fc4a018 >> You may checkout this tag using: >> git clone https://gitbox.apache.org/repos/asf/commons-configuration.git >> --branch commons-configuration-2.10.1-RC1 >> commons-configuration-2.10.1-RC1 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1705/org/apache/commons/commons-configuration2/2.10.1/ >> >> These are the artifacts and their hashes: >> >> #Release SHA-512s >> #Sun Mar 17 20:27:50 UTC 2024 >> commons-configuration2-2.10.1-bom.json=ed21bbdf1666c55d2204fcb4134cbe34402516033f7b0a502f85c26002b1b603a926c5956fe87a477ef3b781247d253727d130dc616f11d732f2127c4ab14da1 >> commons-configuration2-2.10.1-javadoc.jar=fb986f680f30684b51550c28de4c50ae7b13a5dcb57204c3a73086fa5ea5e904a3e5a96da0950b54f4ea5387c9b95742c13b76baab899fdc27e3f2ea29afddaa >> commons-configuration2-2.10.1-src.zip=21192c0ee5ffa1af49afbd2556745f4c7183d47ee9abc40deca40800e0790594d17285756dded0b79702117d286d2bb09953c429b1c78037d33f199dcd04ce81 >> commons-configuration2-2.10.1-test-sources.jar=3610ad010fe2702b9c8481d568f0f448cdc8fa8a1b03695ab5991c6348e619766f096da2603062933cd74066034fcbb4310fc03241f15256e7cf69e1a3723161 >> commons-configuration2-2.10.1-src.tar.gz=cccaa29b59467e1bc08a2c62d84a057f342418003e10b5a0c259c67be2059db38c035224bfe520e48e789e55b656f105079f42486590e29624c35a436fcee257 >> commons-configuration2-2.10.1-bin.tar.gz=fc0d92d528c8e48615103c9f3022c36302a161f2b647d8df3cca1b0b9135d1de7bb5c92ea891bdee4a67ed4d98a6b5ed75ba53eba108dc84e518f369763d8950 >> commons-configuration2-2.10.1-sources.jar=aa63579bdaea11e84c5656af588026db4357006ca03dd4ef7405dcd0910f2b55998554e801c45e462587999adc49033c2cc50abc83d2a613cf396125ab28e4ea >> commons-configuration2-2.10.1-tests.jar=43a9a052f7fc36bbebb25c5850dc31252961388dac630b6608a9394f5c1c23f21c4aee9d04abec614d0a239004f7b47028bd2a229b9d2c5585c7b550706cfaae >> commons-configuration2-2.10.1-bom.xml=8449699ebf34b5e1e74ca006bfb5a06386e285b9c8fee0e1701300d10561749c21000e71affdfa4a29966ec3f4153f038956cf012a091ac5bd3a7bd78dc21c54 >> commons-configuration2-2.10.1-bin.zip=e1658a0c901b488b65f9373f439045a208547cf75e3cac43a45ab227589166d2a4c5993f76ec56956d0fc9d0d10231d4b909f5042a0d036259b92727e3da4760 >> org.apache.commons_commons-configuration2-2.10.1.spdx.json=351ca7d39367b6ce3a7afb39575c990aab7db2d753588ab83109fc29479d0e84fde2e017c61cfa176f43cf7d573116f1f07523f072ff9dab4df6968969aa1293 >> >> I have tested this with 'mvn' and 'mvn -V -Prelease -P jacoco -P >> japicmp clean package site deploy' using: >> >> openjdk version "17.0.10" 2024-01-16 >> OpenJDK Runtime Environment Homebrew (build 17.0.10+0) >> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing) >> >> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) >> Maven home: /usr/local/Cellar/maven/3.9.6/libexec >> Java version: 17.0.10, vendor: Homebrew, runtime: >> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home >> Default locale: en_US, platform encoding: UTF-8 >> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac" >> >> Darwin **** 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 >> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64 >> >> Details of changes since 2.10.0 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/site/changes-report.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/site/index.html >> (note some *relative* links are broken and the 2.10.1 directories >> are not yet created - these will be OK once the site is deployed.) >> >> JApiCmp Report (compared to 2.10.0): >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/site/japicmp.html >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.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, >> >> Gary Gregory, >> Release Manager (using key 86fdc7e2a11262cb) >> >> For 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.10.1-RC1 >> commons-configuration-2.10.1-RC1 >> cd commons-configuration-2.10.1-RC1 >> >> 1b) Download and unpack the source archive from: >> >> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.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 >> >> -the end- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
