We have fixed a few bugs and added enhancements since Apache Commons
Parent 66 was released, so I would like to release Apache Commons
Parent 67.
Apache Commons Parent 67 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/67-RC1 (svn
revision 67659)
The Git tag commons-parent-67-RC1 commit for this RC is
f040949b0609d576090204c0df00427adc66f955 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f040949b0609d576090204c0df00427adc66f955
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-67-RC1 commons-parent-67-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1694/org/apache/commons/commons-parent/67/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Mar 02 04:04:40 UTC 2024
commons-parent-67-bom.json=7215c4657647588d4ab9b9e2320616afb468aaa60c9ab47433e2932c6f155232977e4a590dffe7950ec0d56bd7f05e48ed7b2c586af9966b6b5ba6fd992678b2
commons-parent-67-bom.xml=2478de38dc1d151c3300f50cbcfbf4227346ae3e543e5a82590aabd61566687de807817b78a4e5fe5aa71fa12c80ba47043bf99a957ba801e96a46698301f77e
commons-parent-67-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-67-src.tar.gz=da8f770011943e5b501a0d9f41594bb4c46832936f9d12d97830c53eaa7adb5e0bd2451d50db52d2fad22eb97314811dd6717f9b15e549f9868949279d97797d
commons-parent-67-src.zip=22fce1b37cef35bc42a20a648b06c046ab8ef56812952e5b1b0db594ad1d322b9a7584fd964813b6fd0d1479a31329f36367c634a6cefcd4177c2f304b917495
org.apache.commons_commons-parent-67.spdx.json=baf145c1986457136b23c981a3f992037a12b864062ceb5a72e87c89f2041fe288a6553e89d445f9b0ee644e67addecc2e52fa2a74b3c55d06a63f406bf6ac1b
I have tested this with:
mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
using:
openjdk version "21.0.2" 2024-01-16
OpenJDK Runtime Environment Homebrew (build 21.0.2)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 21.0.2, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk/21.0.2/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
Darwin **** 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
Details of changes since 66 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/67-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/67-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/67-RC1/site/index.html
(note some *relative* links are broken and the 67 directories are
not yet created - these will be OK once the site is deployed.)
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/parent/67-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)
For 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-parent.git
--branch commons-parent-67-RC1 commons-parent-67-RC1
cd commons-parent-67-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/67-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-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
