This vote passes with the following +1 votes: This vote passes with the following binding +1 votes:
- Melloware Inc (non-binding) - Piotr P. Karwasz (ppkarwasz) - Gary Gregory (ggregory) - Arnout Engelen (engelen) TY all, Gary On Sun, May 25, 2025 at 10:18 AM Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > BeanUtils 2.0.0-M1 was released, so I would like to release Apache > Commons BeanUtils 2.0.0-M2. > > Apache Commons BeanUtils 2.0.0-M2 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/beanutils/2.0.0-M2-RC1 > (svn revision 77118) > > The Git tag commons-beanutils-2.0.0-M2-RC1 commit for this RC is > 5d09ef79376511519b0b4aafcb5bbe79a70bd3c7 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-beanutils.git;a=commit;h=5d09ef79376511519b0b4aafcb5bbe79a70bd3c7 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-beanutils.git > --branch commons-beanutils-2.0.0-M2-RC1 commons-beanutils-2.0.0-M2-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1838/org/apache/commons/commons-beanutils2/2.0.0-M2/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun May 25 14:05:13 UTC 2025 > commons-beanutils2-2.0.0-M2-bin.tar.gz=94212b341e6832c98cff40d4728c543ecebe28e7b942dd0f7072675a4905d88e8bd5c141331cc9f0f7d4104cfeeca8507822ddd0b2066a98310589459897a4c4 > commons-beanutils2-2.0.0-M2-bin.zip=98276590b76d8362d9c380288c4c665e926c2719615ed6d2d08e1c70410efeac57ca5a1e093d832485a3176898fd968ee6661f15e160f7a4fd561cd56dc844b6 > commons-beanutils2-2.0.0-M2-bom.json=96699595e8f269cbe56c94ef3c43f8d2e6bd1fa6354725e0cfd2634e7e35b7220944b85c00655eb060af2ceb2094797cdcf4bd55949933ff3202f2c9076115da > commons-beanutils2-2.0.0-M2-bom.xml=ff3fbb0f65b948c19d619d37d4e00de9d2c8ff3be8806705d711c0b76dbb7fd742ca9885ca08c36e1631da7094ea9c14bd586bae694a36952dc2d4f5a56c058e > commons-beanutils2-2.0.0-M2-javadoc.jar=49a28d840c9aa52af738b761acd2071a59147212a599f027da60960166596416f6cd2fb16c4dc6070fc68b6c26323f71f15ff0550867a666c3ab95c54c5c85f1 > commons-beanutils2-2.0.0-M2-sources.jar=340132393969a094d838c667ef390f4b34e6f08e5e623ea196505a73aedf4d36a3ab3ad629282723110127be0996653e9694af685f32585fde6b6bcf9c2f8d22 > commons-beanutils2-2.0.0-M2-src.tar.gz=3097dce40ff3c62db1f330d6320c2df6c32f0b413d9de2f6170c28b97c66df260bc98c2db3fbcfff4793b425a2b18d2ee1e63310cb51959c9dbc586363c8e85b > commons-beanutils2-2.0.0-M2-src.zip=dca62e297ac5b87caaf63c6793764a8ce743e2539766dd59588ab319d5051a5adaa145aba584c38d0fa0624e481d4d0584629bf88f56785613fb87bf4b7bc4b9 > commons-beanutils2-2.0.0-M2-test-sources.jar=5039e108dd08d21299e29f896e121c0d1ac7a665cb02be621b7743ca3f4687fe15974cd45521947989539d29c05170cb539a0f75250ef6844c5c6492d34a4c0e > commons-beanutils2-2.0.0-M2-tests.jar=79254682d72f9984ffa2f328d80a65aeea3fa11fc05427e9b17724c58ec35f1fe9171e9a370adfda98166371baffca13219325c8b0c8b4666703e1ea08a5f3d7 > org.apache.commons_commons-beanutils2-2.0.0-M2.spdx.json=f02f32993af6ca714ddba110921271a5e14d6aad7c42f532b386d86bfebcf0d9044e7b10f07413873a89e30226cdab850f2f86290d806818c90df4e93110a80e > > > I have tested this with 'mvn' and 'mvn -e -V -P release -P test-deploy > -P jacoco -P japicmp clean package site deploy' using: > > openjdk version "21.0.7" 2025-04-15 > OpenJDK Runtime Environment Homebrew (build 21.0.7) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.7, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec > Java version: 21.0.7, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.7/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.5", arch: "aarch64", family: "mac" > > Darwin ***.local 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 > 19:53:27 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6041 arm64 > > Docker version 28.0.4, build b8034c0 > > > Details of changes since 2.0.0-M1 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/beanutils/2.0.0-M2-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/beanutils/2.0.0-M2-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/beanutils/2.0.0-M2-RC1/site/index.html > (note some *relative* links are broken and the 2.0.0-M2 > directories are not yet created - these will be OK once the site is > deployed.) > > JApiCmp Report (compared to 2.0.0-M1): > > https://dist.apache.org/repos/dist/dev/commons/beanutils/2.0.0-M2-RC1/site/japicmp.html > Note that the above report notes several incompatibilities. > These are considered OK since until we finalize 2.0.0. > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/beanutils/2.0.0-M2-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 24 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, and Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1a) Download and decompress the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/beanutils/2.0.0-M2-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must check source distributions as a minimum. > > git clone https://gitbox.apache.org/repos/asf/commons-beanutils.git > --branch commons-beanutils-2.0.0-M2-RC1 commons-beanutils-2.0.0-M2-RC1 > cd commons-beanutils-2.0.0-M2-RC1 > > 2) Checking the build > > All components should include a default Maven goal, such that you can > run 'mvn' from the command line by itself. > > 2) Check Apache licenses > > This step is not required if the site includes a RAT report page which > you then must check. > This check should be included in the default Maven build, but you can > check it with: > > mvn apache-rat:check > > 3) Check binary compatibility > > This step is not required if the site includes a JApiCmp report page > which you then must check. > This check should be included in the default Maven build, but you can > check it with: > > mvn verify -DskipTests -P japicmp japicmp:cmp > > 4) Build the package > > This check should be included in the default Maven build, but you can > check it with: > > 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 > > 4b) Check reproducibility > > To check that a build is reproducible, run: > > mvn clean verify artifact:compare -DskipTests > -Dreference.repo=https://repository.apache.org/content/repositories/staging/ > '-Dbuildinfo.ignore=*/*.spdx.json' > > Note that this excludes SPDX files from the check. > > 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
