We have updated the Apache Commons POM since Apache Commons Parent 58
was released, so I would like to release Apache Commons Parent 59.
Apache Commons Parent 59 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/59-RC1
(svn revision 63135)
The Git tag commons-parent-59-RC1 commit for this RC is
86b1b6f9575219f9009cdc89ddf3f1450e9f8982 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=86b1b6f9575219f9009cdc89ddf3f1450e9f8982
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-59-RC1 commons-parent-59-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1646/org/apache/commons/commons-parent/59/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Jul 22 16:24:00 EDT 2023
commons-parent-59-bom.json=094208bc437b500fd33853d186fda8728257519ab0fe59dbfcb1d0eb96a822a9f0fbbcb103d29539dada9b2ddd7ef530197bfd2558d112e006e327931ceb35da
commons-parent-59-bom.xml=1a7b5b636ceb6c2b1cd23a31d2b4c19f35fe7c037502e439132d86e85b367fbc173c17a7a60449a6b9073194b2c2987762a4cc54e68211a55015745bdb1a5c88
commons-parent-59-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
commons-parent-59-src.tar.gz=71acd5fb605fa2eaede743319a7ad0aed57bfa438152a84dd284bf075807d91a4db52251c718c0d3428a80f43d0022f678ca74a784a80f14f063d1973e6ade7b
commons-parent-59-src.zip=080f4deab4863f64f5324e4f43e25a1b7dfef96962dd4afc3227356155aa1aa7fdc314c8499777058789b0748f332b8ad91ba3d5f2b67457a494e9380204d758
org.apache.commons_commons-parent-59.spdx.json=b9614d9c1143eb8c7f5d79c3ec19f701ba395fe903e3f18280b245e35296e0a9f4ad53eeea85e6b59c0751c85e1a6db71cf5fd5a58b0c0e6ee9da09737626657
I have tested this with
mvn -V -Ddoclint=none -Prelease -Ptest-deploy clean package site deploy
using:
Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
Maven home: /usr/local/Cellar/maven/3.9.3/libexec
Java version: 1.8.0_372, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+372/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
Darwin **** 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun 8 22:22:22
PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
Details of changes since 58 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/59-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/commons-parent/59-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/59-RC1/site/index.html
(note some *relative* links are broken and the 59 directories are
not yet created - these will be OK once the site is deployed.)
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/59-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 DEADBEEF)
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-59-RC1 commons-parent-59-RC1
cd commons-parent-59-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/59-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
