+1 Build, site, reports, api compatibility, release notes, sigs all OK There were a bunch of javadoc warnings for missing javadoc, but not a blocker for release.
Tested on Apache Maven 3.9.3 Java version: 17.0.11, openjdk OS name: "linux", version: "5.15.0-107-generic", arch: "amd64", family: "unix" Phil On Fri, Jun 7, 2024 at 6:53 AM Gary Gregory <ggreg...@apache.org> wrote: > We have fixed a few bugs and added enhancements since Apache Commons > Configuration 2.10.1 was released, so I would like to release Apache > Commons Configuration 2.11.0. > > Apache Commons Configuration 2.11.0 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.0-RC1 > (svn revision 69603) > > The Git tag commons-configuration-2.11.0-RC1 commit for this RC is > f428261556f4cba56a6d49a4824803cff056fbed which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=f428261556f4cba56a6d49a4824803cff056fbed > 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.11.0-RC1 > commons-configuration-2.11.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1741/org/apache/commons/commons-configuration2/2.11.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri Jun 07 13:40:47 UTC 2024 > > commons-configuration2-2.11.0-bin.tar.gz=c77fcb1dfb66fc780e122348cc4991a08f89e41cdb06e60feb7c6151ea059a88924ce55ccf86f3d6563902c2903647047a5da45ad90752457dc00b3b546b0877 > > commons-configuration2-2.11.0-bin.zip=30be0da66979268a71e4151fdc63ce02efa33351dba87260137108982759f3412f74bae4046e1c9c00ce10c592a67364be190e80428dbde7b451b347ba08d708 > > commons-configuration2-2.11.0-bom.json=3a0a6abbcd240e195991ee6a67bf6cd23e5c661a88e88ced892449661e620297e91148e56de3efb0274aeaa90e793fdba7e1acb0c425fd05b438c62636fafd82 > > commons-configuration2-2.11.0-bom.xml=4227e57f8aac9e06685a559d8123e058d7409ed1d6a3c8d1879c7a42628b3f30ee5d3c64e4d3a8621bc3d75ced0509987c1fb198151d12a0cab23966cdda07a0 > > commons-configuration2-2.11.0-javadoc.jar=4da6c6d18c9834ae714dcbd68fd917dc8cd901b554427f2d1208cfc3aef284f37787433155e0a0ec10acbff3679c66a6a47b75fe10a3c067ce3fbabdcb697464 > > commons-configuration2-2.11.0-sources.jar=0343f023a1da7cbe72b0059a2326d3d06d11f6471ee660cc183c38b602a2b2a4a631b715078c3a87dd437718c030658076794ea47e3932829fe8a3c2ce171a8f > > commons-configuration2-2.11.0-src.tar.gz=a7fa8d6599c54bf38eabe9be0458e657051d7db1785ee71c8187af4f084ed011e6325d245f2c8acc7cc15243feb6782804231e4fdca06cda184e58f11def305b > > commons-configuration2-2.11.0-src.zip=e60cc0384ff154888301e21772be59d7e61edfc0bf2ef16e3744caee6af25424fd3cf85664a98b46a0866d1bb42a3bdc943f4507b43bf8a2145a45ebb816c952 > > commons-configuration2-2.11.0-test-sources.jar=2b2f9f3cca97fb697842d4c04760a7973b47fc64a0160b67c6188af984ca48ae1906627b8d97c698dc89fb3dc66c26368144ca137d5ac1a3a134703aa1833281 > > commons-configuration2-2.11.0-tests.jar=3a283960e3f2ac488abdac0f460a4b68030513dad8ec7f6c8cf9b490fff2190441acff705152b9e77def9cd8b3dd9f989e86b64050e72b48700b3ad92c083788 > > org.apache.commons_commons-configuration2-2.11.0.spdx.json=9e2f291cfd176ff243efd7007c0fde1e1d92a0bd6642b6bb659f8914c77c9f16b3da907050bae9ddb4ab11bd11cb2086b68bb5938c70878fa262a32bd1a26c56 > > I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy > -P jacoco -P japicmp clean package site deploy' using: > > openjdk version "17.0.11" 2024-04-16 > OpenJDK Runtime Environment Homebrew (build 17.0.11+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing) > > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0) > Maven home: /usr/local/Cellar/maven/3.9.7/libexec > Java version: 17.0.11, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.5", arch: "x86_64", family: "mac" > > Darwin **** 23.5.0 Darwin Kernel Version 23.5.0: Wed May 1 20:09:52 > PDT 2024; root:xnu-10063.121.3~5/RELEASE_X86_64 x86_64 > > Details of changes since 2.10.1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.0-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.0-RC1/site/index.html > (note some *relative* links are broken and the 2.11.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.10.1): > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.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 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 > <https://gitbox.apache.org/repos/asf/commons-configuration.git--branch> > commons-configuration-2.11.0-RC1 > commons-configuration-2.11.0-RC1 > cd commons-configuration-2.11.0-RC1 > > 1b) Download and unpack the source archive from: > > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.11.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 > > -the end- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
