We have fixed quite a few bugs and added some enhancements since
Apache Commons Parent 59 was released, so I would like to release
Apache Commons Parent 60.
Apache Commons Parent 60 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/60-RC1
(svn revision 63521)
The Git tag commons-parent-60-RC1 commit for this RC is
f1b4803b7c297d4deec220cdd3c41c7372c27217 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=f1b4803b7c297d4deec220cdd3c41c7372c27217
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-60-RC1 commons-parent-60-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1649/org/apache/commons/commons-parent/60/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Aug 20 11:00:27 EDT 2023
commons-parent-60-bom.json=35066e16384f2b055d2b14c885fab5ef2dc40b00f26604905bbd9d4df6899c527327ed6b3e3d40dd9874a026c8cc2f08938356a8e0197678d90c5f51e6e1d566
commons-parent-60-bom.xml=7c18832814d658d015809a7b136cce5e3b60dcbe06737b8217d19d908cd9a55ea458efac2818012e628756f65b7e7e9ab1591d27764703b5b5d18c7902c62df2
commons-parent-60-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
commons-parent-60-src.tar.gz=f2f84a31ed827e1f8706d4e7f8e998a73f2cfb18c3df0781a48f186e9065119604b38d1f80264ea1fb2576a0268fc2beeedd5b204c68351707fde17a6dd38695
commons-parent-60-src.zip=ccf82b4929059cee090cddd56933506b00133f9fd697dc451447125221318612a4d7b126de91d15cd8c960e6d052f22f9209455abfaddbf90a9a3c4329183ae9
org.apache.commons_commons-parent-60.spdx.json=3cc806141c4249d9ce1263b1da19973ed693d090dc1f3141824cafba12a483f641a876214cd02bab1ad2b65528c568697fca40a341b8650002d6e73cccb9a9e5
I have tested this with
mvn -V -Ddoclint=none -Prelease -Ptest-deploy clean package site deploy
Using:
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /usr/local/Cellar/maven/3.9.4/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.5", arch: "x86_64", family: "mac"
Darwin **** 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul 5 22:21:56
PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_6
Details of changes since 59 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/60-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/commons-parent/60-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/60-RC1/site/index.html
(note some *relative* links are broken and the 60 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/60-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,
garydgregory,
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-60-RC1 commons-parent-60-RC1
cd commons-parent-60-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/60-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
