My +1

Gary

On Sun, Oct 5, 2025 at 7:25 AM Gary Gregory <[email protected]> wrote:
>
> We have fixed a few bugs through dependencies since Apache Commons
> Parent 88 was released, so I would like to release Apache Commons
> Parent 89.
>
> Apache Commons Parent 89 RC1 is available for review here:
>     https://dist.apache.org/repos/dist/dev/commons/parent/89-RC1 (svn
> revision 79808)
>
> The Git tag commons-parent-89-RC1 commit for this RC is
> 8f53f8df6668e82cb4f64a040f2754466098a006 which you can browse here:
>     
> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=8f53f8df6668e82cb4f64a040f2754466098a006
> You may checkout this tag using:
>     git clone https://gitbox.apache.org/repos/asf/commons-parent.git
> --branch commons-parent-89-RC1 commons-parent-89-RC1
>
> Maven artifacts are here:
>     
> https://repository.apache.org/content/repositories/orgapachecommons-1863/org/apache/commons/commons-parent/89/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Sun Oct 05 11:16:12 UTC 2025
> commons-parent-89-bom.json=bb705036c858491d47e8f99d7fa5f8108f3baeb5d9f08c3afaaa2e8a2261375a853257736dae89b9160b6ffc712a876279e1a1fbb47eee3a9e91b8bda3a42e98
> commons-parent-89-bom.xml=98fc9a37cb800147a2b660e39c9ab96763d4c926d40097cfa9d46b73230556bf890f19703bb6a292a4104e696c6f7f70cfaefe0065c1cfa6d025360671f51681
> commons-parent-89-site.xml=013e428312ff3bda9c7e9bc2f61ddf5e3c3507409169aabf81d899a2d4d851e8a51534ab0458542b42a5b60e64fd50f092993572164157948146829ede0cb8d2
> commons-parent-89-src.tar.gz=b663dcf7b58f96fd072f4935daedb12e0426c8e6e37b4ad0fa3c199fd3d4c3d89ef0d6dbe897eddc2ed71a292510c73e68b2f245a3974ea33f35b5468b7935f8
> commons-parent-89-src.zip=56c18f6ea8f08beb22cbfcaba09e12ede36652524379c34e76604790b4efa03a8960fc7aa225978d23e50c030af22b3cc395b4bd7ae55245317db41c0426be06
> org.apache.commons_commons-parent-89.spdx.json=6a7055359496c0cbe357d33efa2498815639a498099f4eab387e5a59b17154a7ecc6e7d77946037b4b3318c0000f063f2ccc9303c43584838a8ca24379c0a328
>
>
>
> 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 88 are in the release notes:
>     
> https://dist.apache.org/repos/dist/dev/commons/parent/89-RC1/RELEASE-NOTES.txt
>     
> https://dist.apache.org/repos/dist/dev/commons/parent/89-RC1/site/changes.html
>
> Site:
>     
> https://dist.apache.org/repos/dist/dev/commons/parent/89-RC1/site/index.html
>     (note some *relative* links are broken and the 89 directories are
> not yet created - these will be OK once the site is deployed.)
>
> *** JApiCmp Report (compared to 88):
>     
> https://dist.apache.org/repos/dist/dev/commons/parent/89-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/parent/89-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/parent/89-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-parent.git
> --branch commons-parent-89-RC1 commons-parent-89-RC1
> cd commons-parent-89-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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to