We have added some enhancements since Apache Commons Parent 62 was
released, so I would like to release Apache Commons Parent 63.
Apache Commons Parent 63 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1
(svn revision 64275)
The Git tag commons-parent-63-RC1 commit for this RC is
0fd27a2962b49dce17e6825d3d0a3f9d506164cd which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0fd27a2962b49dce17e6825d3d0a3f9d506164cd
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-63-RC1 commons-parent-63-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1660/org/apache/commons/commons-parent/63/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Sep 30 13:31:17 EDT 2023
commons-parent-63-src.tar.gz=849823362a097cae5c3d6dd3be6a0369145da6a7a9a9ffaaac67bc0f4dd68c547a0b060055e5056e138d92aa029d84a0730c709797ac4392902fa5933059febb
org.apache.commons_commons-parent-63.spdx.json=7dd6414048549199d30dae095c65d1c42f783e622561451544453f8dae08a61121549edc4049019c475b2192e36b5377e81f89df9d9d6fc70bb43130c6c377d9
commons-parent-63-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
commons-parent-63-src.zip=c074bfa5526f5d0eaa8f631fa8e04798d97dcb07336d3f094f70b87d4917181f540c47145f77acfe6e78d32317312b90358984226f7a21b4255846180acb9011
commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2
commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744
I have tested this with
mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
using:
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /usr/local/Cellar/maven/3.9.4/libexec
Java version: 17.0.8.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
Details of changes since 62 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/index.html
(note some *relative* links are broken and the 63 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/63-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-63-RC1 commons-parent-63-RC1
cd commons-parent-63-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-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
Gary
-the end-
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
