We have added enhancements since Apache Commons Parent 69 was
released, so I would like to release Apache Commons Parent 70.
Apache Commons Parent 70 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/70-RC1 (svn
revision 69104)
The Git tag commons-parent-70-RC1 commit for this RC is
e3c255492606a669eca37c5addd70a4387071fbf which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=e3c255492606a669eca37c5addd70a4387071fbf
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-70-RC1 commons-parent-70-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1726/org/apache/commons/commons-parent/70/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat May 11 14:27:12 UTC 2024
commons-parent-70-bom.json=cb08056ebb04bb12b7b4c0411b67fac9c425d1288d644fbdda12936bfff44db73571c054bce29b9eed6ce6f70f2310a24bcf92c2aea7d0190f25f95c89ea7035
commons-parent-70-bom.xml=e2d9a7a8a612373d555c9bbc9f325173244ce6a25edbebde4006ba07817f9f3c2dc9eefc0735ab7d6984b956b1f86b1abbf217ced6cfcafa2a258339f2f43e75
commons-parent-70-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
commons-parent-70-src.tar.gz=5a2a007517a40493f5e74fb72063fca24200db812324b9820f5f5d0b5dad4e147535a0fe9e5d7a90ddb9e425e43f6491b1cc16cf4fc244ac289f4bf2edea0a34
commons-parent-70-src.zip=93d1b8a7b762c74d7043ed3655491d4fed1dd83d64256c5909becadb1e49e7781bf64b1a020eaab7bf3854d161771b871b17f135de16317e68034bc95d23ac6d
org.apache.commons_commons-parent-70.spdx.json=16b2ccbd6591a99ee405b92ebe29f32dd609c07de6f53367564abb0d0d200c8d89cc8810463c3ec85592757930201f2422064c97f5be3fd21c45164c3343c524
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.11" 2024-04-16
OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /usr/local/Cellar/maven/3.9.6/libexec
Java version: 17.0.11, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.11/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 69 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/70-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/70-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/70-RC1/site/index.html
(note some *relative* links are broken and the 70 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/70-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-70-RC1 commons-parent-70-RC1
cd commons-parent-70-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/70-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
6) Build the site for a multi-module project
mvn site
mvn site:stage
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html
Note that the project reports are created for each module.
Modules can be accessed using the 'Project Modules' link under
the 'Project Information' menu (see <path-to-site>/modules.html).
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
