We have fixed a few bugs and added enhancements since the release of
Apache Commons Release Plugin 1.9.2, so I would like to release Apache
Commons Release Plugin 1.10.0.

Apache Commons Release Plugin 1.10.0 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.10.0-RC1
(SVN revision 89140)

The Git tag commons-release-plugin-1.10.0-RC1 commit for this RC is
5e84decdc706277cbe194e7e291503b26f617e05, which you can browse here:
    
https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=5e84decdc706277cbe194e7e291503b26f617e05
You may check out this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git
--branch commons-release-plugin-1.10.0-RC1
commons-release-plugin-1.10.0-RC1

Maven artifacts are here:
    
https://repository.apache.org/content/repositories/orgapachecommons-1974/org/apache/commons/commons-release-plugin/1.10.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Sun Nov 08 16:39:46 UTC 2026
commons-release-plugin-1.10.0-bin.tar.gz=be995bac6a4dd52c53bc51e48efbee7fe113ff1150482be29e4883f9885af188c8662670d26d5e752cef0375e21cb4dc82d7ff5e7aec77adc1e102b8a115940f
commons-release-plugin-1.10.0-bin.zip=1da05a613be73e006f7a17f8b0e4b62df634477490053cda7a3505ae3971baebd5f3715f5d069541b7019c4df362ceef347d885836a209223cbe568e2dd74b4b
commons-release-plugin-1.10.0-bom.json=23cab12f6d663b623808114a96594a040e5054ec24ace21ad541f7591643e63c8a55fb54ced01c5819227acb51cec6d798ac23621cbcba080c9984a9be45cae7
commons-release-plugin-1.10.0-bom.xml=474732d1b2580166d570222c86b7922d50bff3c16357d94a15c26096359e8cfcd8cd6c4a50f30e54e339a5597a89578c76c696b92ec8cd444dcdbea7d30a7cda
commons-release-plugin-1.10.0-javadoc.jar=5ccbaaf58fe7f7bd6729d11389611655b59d3c2249e690baa15d879849848b9b2bbd8884a2a3426cb3278d6f745d33f842c973b685a5278ea72d77562a094da5
commons-release-plugin-1.10.0-sources.jar=cb9306d5d6832106c3add15826ab335bc8a7dbb1918684943bf7a800477bad8a3b39336a32bd6650c81bfd5bbf13ba22095d8e901d7b97853c718bd4f1b914b4
commons-release-plugin-1.10.0-src.tar.gz=8cf1e0b2a5d6a679590f28eb1d86f55679e4f15307841e7fff5befa27cbe1d04cc2d4334ce38895997d95bdc2ecc6ac349240901017befa6a307b910277594c8
commons-release-plugin-1.10.0-src.zip=8966812549b50e4b1522eec649a7ba7d42a3de54e6dbb428fa43724962f661eea9cec07a46933e89e8e3a868c42b3ffd2eaba4defcdbfe4a86732f6d5d53af24
commons-release-plugin-1.10.0-test-sources.jar=cb6221c6d10e630d5704449114b30e72bff3ae0dfd4e05cae9c8fce825980bc1c697d66cc42e7d2fd447b9f15aaaac5a7d556ffe40cfa4a659a4b4af6a5c97df
commons-release-plugin-1.10.0-tests.jar=dbe959359c9682e1a1abae447aca48f6f21ea8600d2d031c7a2604c82898977ce8ded247a062109b08cc9317d15090af2337c82c3d18814bb20d81700ea4c775
commons-release-plugin-1.10.0.jar=c4bbbca3839ed2188a1a7dc9d218280ca8deb0c1476f64ac3cc61de74558c2972d4814ccbb1b1db0029d7c01f5ddcc6a8a0cf46d8cc70b7a8acf496b40b0c8c4
commons-release-plugin-1.10.0.pom=7cd8c3c683011abfb79dbe7fb44041d83b1ff9538eec06c1c4afd1fd78c71c94fb8bc34912f70aaf06bd977230ee3c8aa5237dbae6cdbd1ab9317b13de9513ad
org.apache.commons_commons-release-plugin-1.10.0.spdx.json=e824330a211d1345f415216322edb39e17a77d1874bb68678c16794f7c6c5acc96b7b9eac3a3fb79604c83ee8e2e0a4b7e98b82a64d93f3e1f2162113a1a62e7


I have tested this with 'mvn' and 'mvn clean install site' using:

openjdk version "27.0.1.0.3" 2026-10-24
OpenJDK Runtime Environment Homebrew (build 27.0.1.0.3)
OpenJDK 64-Bit Server VM Homebrew (build 27.0.1.0.3, mixed mode, sharing)

Apache Maven 3.10.0 (c43a36b8d67be7e0805a411bc0898af1a51f5472)
Maven home: /opt/homebrew/Cellar/maven/3.10.0/libexec
Java version: 27.0.1.0.3, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk/27.0.1.0.3/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8, time zone: UTC
OS name: "mac os x", version: "26.7.2", arch: "aarch64", family: "mac"

Darwin Garys-MacBook-Pro.local 25.6.0 Darwin Kernel Version 25.6.0:
Mon Oct 12 00:39:48 PDT 2026;
root:xnu-12377.161.15.701.48~2/RELEASE_ARM64_T6041 arm64

Docker version 29.9.2, build a82e528


Details of changes since 1.9.2 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.10.0-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.10.0-RC1/site/changes.html

Site:
    
https://dist.apache.org/repos/dist/dev/commons/release-plugin/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.2): No report for this component.

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/release-plugin/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 530AA5F25C25011F)

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/release-plugin/1.10.0-RC1/source

1b) Check out the RC tag from Git (optional)

This is optional, as a reviewer must at least check source distributions.

git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git
--branch commons-release-plugin-1.10.0-RC1
commons-release-plugin-1.10.0-RC1
cd commons-release-plugin-1.10.0-RC1

2) Check the build

All components should include a default Maven goal, such that you can
run 'mvn' from the command line by itself.

3) 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

4) 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

5) 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 versions produced by -V in your VOTE reply.
To gather OS information from a command line:
Windows: ver
Linux: uname -a

6) Check reproducibility

To check that a build is reproducible, run:

# Verify using a JDK major version matching: 27.0.1.0.3
export TZ="UTC"
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.

7) 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