We have fixed a few bugs and added some enhancements since Apache
Commons Parent 67 was released, so I would like to release Apache
Commons Parent 68.
Apache Commons Parent 68 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/68-RC1 (svn
revision 68015)
The Git tag commons-parent-68-RC1 commit for this RC is
f0b82138cf36096ed7b42a716b8d56ffd1820b22 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f0b82138cf36096ed7b42a716b8d56ffd1820b22
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-68-RC1 commons-parent-68-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1706/org/apache/commons/commons-parent/68/
These are the artifacts and their hashes:
#Release SHA-512s
#Tue Mar 19 23:37:48 UTC 2024
commons-parent-68-bom.json=783ef834379f0931b2f888fa98f19662fa42189d7bbf581b949efb336241730595b698cae26d9cac3b88da6ad48a586b462fa35fe93775214a8e130e66f2e4b3
commons-parent-68-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-68-bom.xml=afbfaed1f67b2aa944c4853fc83f4d9b6e81a1f305e6c25897a521d95458e2d819a56d73c301ca1a95494eebf68d6bf0e536e08e0eed530c9da2301ca4b8f854
commons-parent-68-src.tar.gz=0bf750850dd54f9e2224d3b1de95e1a14b80ced78f9aa66dc2e9800d6413c9e325d7ae6052298b7060c3e23e002cc159dea7afb6992d81157ebeb6b5a5f3f7e2
commons-parent-68-src.zip=70b5ddc4aebaa48df29ac3bf6ae444276c91426122ab8de91b4a5631c57f45583502fb7a8c41914a9ae2b63a28a2eaf69b505119703fee9ec260b5d64afd9d04
org.apache.commons_commons-parent-68.spdx.json=77951bfc72dd89fd9f597a84e1e1a8daecbf5892864dc9bab4bc844ce8c2f8eba4474470b4240b59db1704dbd8552867d5e60403d27f51e3ac9329752b64f32b
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.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 67 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/68-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/68-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/68-RC1/site/index.html
(note some *relative* links are broken and the 68 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/68-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-68-RC1 commons-parent-68-RC1
cd commons-parent-68-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/68-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
