Note that:
Apache Commons BeanUtils 1.10.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.0-RC1 (svn
revision 73866)
should be revision 73999.
TY,
Gary
On Thu, Dec 26, 2024 at 3:27 PM Gary Gregory <garydgreg...@gmail.com> wrote:
> We have fixed one important bug and added minor enhancements since Apache
> Commons BeanUtils 1.9.4 was released, so I would like to release Apache
> Commons BeanUtils 1.10.0.
>
> Apache Commons BeanUtils 1.10.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.0-RC1
> (svn revision 73866)
>
> The Git tag commons-beanutils-1.10.0-RC1 commit for this RC is
> 1a57099612f32e771943b26ff4407c0261ccf78a which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-beanutils.git;a=commit;h=1a57099612f32e771943b26ff4407c0261ccf78a
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-beanutils.git
> --branch commons-beanutils-1.10.0-RC1 commons-beanutils-1.10.0-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1793/commons-beanutils/commons-beanutils/1.10.0/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Thu Dec 26 20:19:26 UTC 2024
>
> commons-beanutils-1.10.0-bin.tar.gz=b35735dc99bad9889b120839274104593c1f54d12d1274b1023856453a37b749362bf28a639b2dd3a3ee6bcbb3e97bb4976f1616bb09335295baa7f42f9e6e8c
>
> commons-beanutils-1.10.0-bin.zip=9d952a6b2f41a7b0a6d03b02d680183d92c1cacb094da385600e7c96682089e78f5a2e682c0dd12998dda33fc3ae983c9dbb3c1fcff85f36850bb5b1feaae704
>
> commons-beanutils-1.10.0-bom.json=4fc7741a3f87655157e20f7fb552b9dfb5960783e9f23c7ab4393d12a2c97a940421b2be4b879ab746a2674274e0fc764523a151aea28107634664259ff99629
>
> commons-beanutils-1.10.0-bom.xml=0eaf7cd1690fd3e41e9e01a3d24c921c003cb40f601edcb76310a173d3818efdfa6feae83ad5b93d324200f5ee77917d72ad2e1d6451ab992052fd53cce89d9e
>
> commons-beanutils-1.10.0-javadoc.jar=969c9dbcd1fbe07bb93859c14c6e3ae0501e09c449ee7036c302a9d692a329cfa5b7c69874d9caeaaf96d94986af60c45fb0a299a6eab7890931067914705bc0
>
> commons-beanutils-1.10.0-sources.jar=8077253382d1dc936985e6aa5ced9ca985cc5ec0e8e4a5015b7ee1cc61356baff0b3347ced1726c82570687b15bca3c93a68eee5d24f2851e841a1cd4879f1b9
>
> commons-beanutils-1.10.0-src.tar.gz=94960a3901d9c3a2428e883e26e647742b8ec590b269228cc16acecfd5bbf7180d772c4372fb3a09af48d25d0d7dcb166233825f87ce9c8428358967cfe6c6ea
>
> commons-beanutils-1.10.0-src.zip=c3ad212a2ee20673fb1b73a62651e4e7b18f1c6e67461c29cc06f26010a952b1fc5e3056ee9c7a8eb1801c648314cfa9773391e35c49afeef632342b17919651
>
> commons-beanutils-1.10.0-test-sources.jar=db92cb27183c7898c06ac8e10045a73a6f2a6b579f20a9b83b1e7bb670933b6ea49cc842c67f6fe151763bae12ac5d5821812fe8b46167261a830c12a6810781
>
> commons-beanutils-1.10.0-tests.jar=a8075664ad4e287401a648e2a36abab1416ab6519c04eb543fe29df2eb7b2185f787e736ad2b0d061ccbdfb35475eb5fffddcebcd3e45d153457e02e7bdc5e71
>
> commons-beanutils_commons-beanutils-1.10.0.spdx.json=d5458812e43288956c752d0583444967833cc5d8adbabc55f89a8de9615765c9aabaa59f361ace4c0b9d7553296bf70e646581567232ed8c4be83bee53f39563
>
>
> 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.13" 2024-10-15
> OpenJDK Runtime Environment Homebrew (build 17.0.13+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.13+0, mixed mode, sharing)
>
> Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
> Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec
> Java version: 17.0.13, vendor: Homebrew, runtime:
> /opt/homebrew/Cellar/openjdk@17/17.0.13/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "15.2", arch: "aarch64", family: "mac"
>
> Darwin ****.local 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec 6 19:03:40
> PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 arm64
> Docker version 27.3.1, build ce12230
>
> Details of changes since 1.9.4 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.0-RC1/site/changes-report.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.0-RC1/site/index.html
> (note some *relative* links are broken and the 1.10.0 directories are
> not yet created - these will be OK once the site is deployed.)
>
> JApiCmp Report (compared to 1.9.4):
>
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.0-RC1/site/japicmp.html
>
> Note that the above report notes several errors.
> These are considered OK because we bump the platform requirement from
> Java 6 to 8.
>
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.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)
>
> 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-beanutils.git
> --branch commons-beanutils-1.10.0-RC1 commons-beanutils-1.10.0-RC1
> cd commons-beanutils-1.10.0-RC1
>
> 1b) Download and unpack the source archive from:
>
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.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-
>
>
