My non-binding +1

On Fri, Jan 31, 2025 at 10:36 AM Gary Gregory <garydgreg...@gmail.com>
wrote:

> My +1
>
> Gary
>
> On Fri, Jan 31, 2025 at 10:34 AM Gary Gregory <garydgreg...@gmail.com>
> wrote:
> >
> > We have fixed a few bugs and added enhancements since Apache Commons
> > BeanUtils 1.10.0 was released, so I would like to release Apache
> > Commons BeanUtils 1.10.1.
> >
> > Apache Commons BeanUtils 1.10.1 RC1 is available for review here:
> >     https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.1-RC1
> > (svn revision 74565)
> >
> > The Git tag commons-beanutils-1.10.1-RC1 commit for this RC is
> > 92dfc6cef8fadd7616f1fa97dfab57bc206aff23 which you can browse here:
> >
> https://gitbox.apache.org/repos/asf?p=commons-beanutils.git;a=commit;h=92dfc6cef8fadd7616f1fa97dfab57bc206aff23
> > You may checkout this tag using:
> >     git clone https://gitbox.apache.org/repos/asf/commons-beanutils.git
> > --branch commons-beanutils-1.10.1-RC1 commons-beanutils-1.10.1-RC1
> >
> > Maven artifacts are here:
> >
> https://repository.apache.org/content/repositories/orgapachecommons-1811/commons-beanutils/commons-beanutils/1.10.1/
> >
> > These are the artifacts and their hashes:
> >
> > #Release SHA-512s
> > #Fri Jan 31 15:24:52 UTC 2025
> >
> commons-beanutils-1.10.1-bin.tar.gz=b1d6fcd096830d6c3a5ef130402cf3fc9aa479b0f78974fd0227db8e55bae7266aced643a412a051615245b45dc1b817efc68da56a57d286603ef2a00a318c9b
> >
> commons-beanutils-1.10.1-bin.zip=752a348ac1a639d744adfef5fc274a78a8d5c0a8e956b41b73b2f0519975bc1776d2d154ec1210d49b6af0cefd4841e345bd4d855847ceb8cbdd732fb067dda3
> >
> commons-beanutils-1.10.1-bom.json=0369fa65306037672617ac3bff3bd2c5f5dd0ad998fd3b1b95cd46a9784a47fa92a50dd40f331b63194c90a1b70519ff6ef7aee2572549c339dc85cbd70d1e8f
> >
> commons-beanutils-1.10.1-bom.xml=e33f0b6700cf4f809964f02bf80acb581052833e677afee0f6b28a0acdf854e5d80bd18a20c3aedf85bc76ca706ddde94a1f3b7bfdf8ee5023285f51c46f9eaa
> >
> commons-beanutils-1.10.1-javadoc.jar=f5e421d77c9bac9e36d6f5476b543d3ba18361944a40f3888c893392ec869fce2a860332c9c3deb4e7160204cd18d05fa3edacf72bd8747e0c64e0dc47e1ab7d
> >
> commons-beanutils-1.10.1-sources.jar=a3fb2fb6f5859e4b25c5117a1ad8b7413ceada9d6d2ce6f5b5b52eaaa69ad0fff596787d0b2f998b94c6583aab44f1ab06dc2cedeac8af9d26ae60d4a99b9df5
> >
> commons-beanutils-1.10.1-src.tar.gz=063d4c0c9b8c77e9358e15c0ac8b1ad7abbb31e4760a5b3898bac2aee72d0a7eb4f7890769fa31bd096eb038759f97f10f4e7418a6fc4059c1a2050a20756581
> >
> commons-beanutils-1.10.1-src.zip=fc724b1bd0c130b30981520827ee46de40eb232eed4c76e90d4dd32bce09e0eb597caa95652a6e90398822903034c674d62c680055dbce33a04375e1406ebaf6
> >
> commons-beanutils-1.10.1-test-sources.jar=a7a0c7be16f23474f99fb45f0cb69338fbffeacbbd1143590e9fadfdae690124468667d9d9eb1b5d3677cb2b7d2170881415a437371c7e5a9d6c943c6e7ac37a
> >
> commons-beanutils-1.10.1-tests.jar=02fffe6aebb30fd381becdc63d18826b02f0ca44a939210daae831f34806dbba7efbc520b9dacf0af4150f731dd19b7d807d91f07e7a72518d8343112be731f5
> >
> commons-beanutils_commons-beanutils-1.10.1.spdx.json=664ba4915a4a9b537fbebea21adae779f7b4371f3cde9369c1812e37c35bb6835efd0324bd50695a81512fb96d12e2fb293a7def82c2ffd390959dfc3f1c22e1
> >
> >
> >
> > I have tested this with 'mvn' and 'mvn clean install site' using:
> > ***
> > Use the output from "mvn -version" for each combination you tested.
> > Windows: ver
> > Linux: uname -a
> > ***
> >
> > Details of changes since 1.10.0 are in the release notes:
> >
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.1-RC1/RELEASE-NOTES.txt
> >
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.1-RC1/site/changes.html
> >
> > Site:
> >
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.1-RC1/site/index.html
> >     (note some *relative* links are broken and the 1.10.1 directories
> > are not yet created - these will be OK once the site is deployed.)
> >
> > *** JApiCmp Report (compared to 1.10.0):
> >
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.10.1-RC1/site/japicmp.html
> >
> >     ***
> >     Note that the above report notes several errors.
> >     These are considered OK for the reasons stated below.
> >     These exceptions are also noted in the Changes and Release Notes.
> >
> >     Errors reported:
> >     - methods added to interface: OK because that does not affect
> > binary compatibility.
> >     - etc.
> >     ***
> >
> > RAT Report:
> >
> https://dist.apache.org/repos/dist/dev/commons/beanutils/1.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)
> >
> > 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/1.10.1-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-1.10.1-RC1 commons-beanutils-1.10.1-RC1
> > cd commons-beanutils-1.10.1-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
>
>

-- 
==============================
Melloware
melloware...@gmail.com
http://melloware.com
==============================

Reply via email to