We have fixed one bug since Apache Commons Parent 61 was released, so I
would like to release Apache Commons Parent 62.
Apache Commons Parent 62 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/62-RC1
(svn revision 63744)
The Git tag commons-parent-62-RC1 commit for this RC is
b07ecd5204794c818d0c885c05944c83830b3577 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=b07ecd5204794c818d0c885c05944c83830b3577
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-62-RC1 commons-parent-62-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1653/org/apache/commons/commons-parent/62/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Sep 02 09:54:14 EDT 2023
commons-parent-62-bom.json=ea2fa1f0334cb99dc3a984886c0fbe7369fbb11017ba3e24b0b4541f1b1e45bda64c9cc156f6deb400c290979635ac330e949e75f5d3bd7a7d39999c64ca024c
commons-parent-62-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
commons-parent-62-bom.xml=a9dd18751162e1e7c737671e179c83c51c180869f40c98fda3a502d61e4f647553ea573fb0e8a7e3625df657ca6e4c94f8ffadd805b37b1d679e6ceeb613c119
org.apache.commons_commons-parent-62.spdx.json=b05249edd0d8354c741b4fb2907402a0e31900c6ea1d6d704bd6bb4c6110976d6b49909d7352512a9ebd2129d9e7b5014e9068e87331c5414a07eac1a85c7066
commons-parent-62-src.zip=2db114298e6b8bba06103802633ce32a8458a74a0d5e4530e6029f88e26a4f13aafa3f406c701e34f28553a6dea03b271c727d7227dec5feec53a07200f63160
commons-parent-62-src.tar.gz=94e9093a19a1ec6c0b3ff531607481ebd8fbaabf215868ddeed9046954fe5883b2c0d436bddb3cab0c0ae40b061aaef866d4baaa8512471836e64fc92f90661b
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_382, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+382/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.5.1", 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_64
Details of changes since 61 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/62-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/commons-parent/62-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/62-RC1/site/index.html
(note some *relative* links are broken and the 62 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/62-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-62-RC1 commons-parent-62-RC1
cd commons-parent-62-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/62-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
--end--
