We have fixed a few bugs and added enhancements since Apache Commons
Parent 68 was released, so I would like to release Apache Commons
Parent 69.
Apache Commons Parent 69 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/69-RC1 (svn
revision 68202)
The Git tag commons-parent-69-RC1 commit for this RC is
e562e692afef1f6d28cfdd30cd6854c27dba189a which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=e562e692afef1f6d28cfdd30cd6854c27dba189a
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-69-RC1 commons-parent-69-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1709/org/apache/commons/commons-parent/69/
These are the artifacts and their hashes:
#Release SHA-512s
#Fri Mar 29 13:00:58 UTC 2024
commons-parent-69-src.tar.gz=a07b225d4db5280ece61d58f96d4caa63710fa5a451c31b37088cb42218662a51bb2a83a41317904bf5a88d326ae3a40475dbe2aac141dbc4647da6708518031
commons-parent-69-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-69-src.zip=b7a90318720156646a3b141d891544ce913bb53088696116552024c858755a0280b933a74e6f5c1a2d130779ed9048416b05ce6f8f3e7e55b0810379e9ca5339
org.apache.commons_commons-parent-69.spdx.json=923f916ebae1c712ed8a1a0f79de95c56e683f0b00b67f71d899cab59462407252acab856d29725dc6cabfb97bc039ca222eec655213201d6570d08ff07afc65
commons-parent-69-bom.json=f73ef951837fb13a9ea4357fd90fb1034b53ed9bf97641c98dffb8d7a20d62c1ae8a334cc38fc156e4cb5724ee9c852de5292f2288114ed0665fa84cbe71b219
commons-parent-69-bom.xml=d898f2fcf94a55ff845a7b23fe729b949bbc3d8cbb51014b9603551ae6ac6aac41de26b1c213006e40ba2a75e620cf88073505b28385bcca0b9a8f6bca40fa69
I have tested this with ''mvn' and 'mvn -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:
openjdk version "17.0.10" 2024-01-16
OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 17.0.10, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
Darwin **** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
Details of changes since 68 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/69-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/69-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/69-RC1/site/index.html
(note some *relative* links are broken and the 69 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/69-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-69-RC1 commons-parent-69-RC1
cd commons-parent-69-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/69-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
