We have fixed a few bugs and added enhancements since Apache Commons Parent
73 was released, so I would like to release Apache Commons Parent 74.
Apache Commons Parent 74 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/74-RC1 (svn
revision 71082)
The Git tag commons-parent-74-RC1 commit for this RC is
0508d45ed7dd36d666f2ee60cfbfbbbbe5c79f65 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0508d45ed7dd36d666f2ee60cfbfbbbbe5c79f65
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-74-RC1 commons-parent-74-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1776/org/apache/commons/commons-parent/74/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Aug 24 18:22:41 UTC 2024
commons-parent-74-bom.json=50737f868413d6a28de5542ed9e0d78bfddbf9a90c82537c86e031b552f5cdb34e1a3e151b8f19db8e518455d67166f82c6749fdf350ce22b54355d8e43eb8ad
commons-parent-74-bom.xml=7b9f4f67ebdf727b30882470a41ea84189bc02c8e62fc0becede36948cd9614ab7b99e371e8b1ae8832e3c2301a0c84466a7d7dcea42a1d86a684bf190955b67
commons-parent-74-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-74-src.tar.gz=0f248996196af5fa5f654000c9a16fc6916532552cc95ed7b410634e493a3a9fc2c0f040ab2ef212ac5fd6b2244d80529c6c277738d2b46abfdb5d2c8e3b43e7
commons-parent-74-src.zip=a1a2ea1d1a35d36f50573cf29c7dce56ad14d5820705c08e16f52e5f3a5028911d61d30458d4e2cd07cdc1a5ad2f114cd0e73c3d94301a593e4f40266bf0e959
org.apache.commons_commons-parent-74.spdx.json=367ed5ce9f5aed2a636412636b6bf0dd5819df008df9b81b639a3acbf77e2b6c4a40b602f9181267420cd8b6a34f13a3c4a5ed6c59e20271bcec298d84ed1335
I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:
openjdk version "17.0.12" 2024-07-16
OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /usr/local/Cellar/maven/3.9.9/libexec
Java version: 17.0.12, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.6.1", arch: "x86_64", family: "mac"
Darwin **** 23.6.0 Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT
2024; root:xnu-10063.141.2~1/RELEASE_X86_64 x86_64
Details of changes since 73 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/74-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/74-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/74-RC1/site/index.html
(note some *relative* links are broken and the 74 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/74-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, 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-74-RC1 commons-parent-74-RC1
cd commons-parent-74-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/74-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-
