We have fixed one bug since Apache Commons Parent 60 was released, so
I would like to release Apache Commons Parent 61.
Apache Commons Parent 61 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/61-RC1
(svn revision 63644)
The Git tag commons-parent-61-RC1 commit for this RC is
54da14bf9d61b177fca512413556ed029aa0949a which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=54da14bf9d61b177fca512413556ed029aa0949a
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-61-RC1 commons-parent-61-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1651/org/apache/commons/commons-parent/61/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Aug 26 08:43:33 EDT 2023
org.apache.commons_commons-parent-61.spdx.json=c9404db24c145512f6d0e9f687ef10cf5b67f8e5371f46e3f9b23588859066bd4b2dd7d71e09379e48c1b16635ac5cd030bac9402a0c60b3b167f982916a64cf
commons-parent-61-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
commons-parent-61-src.zip=fc8d2fc1fc8e4c896910cf7bcff8ecda3491d957a70648728d005e6263dc3bad07a4e6a1da15978da610907bdea355ae18da57a1895a26a6f9816f109b8f42b8
commons-parent-61-bom.xml=c5968f5a1e8f38e6e01d865be00fc37540f1e53c43e1d6a75f974cb0dac34f6faeeb8e77202de2d578f7b9bb63393fa77b79202b3bdfa60462eb5f7b52a6203c
commons-parent-61-bom.json=38e1c8fb79c53011d2b5eb17624b0922a469bfed7e48e9ca1a59a9d61014054c2e83ec6a33baae9b8206a9a87896322748c918a07d1f892106f60cdee59562f3
commons-parent-61-src.tar.gz=b1b75bc06554158745e49ee7e36c210436baa121052964212fe40ac241cedd491644201177cf7d791e59898a4be4f72a873f5158312e5b6b0426917d059962d5
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: 11.0.20.1, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@11/11.0.20.1/libexec/openjdk.jdk/Contents/Home
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 60 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/61-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/commons-parent/61-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/61-RC1/site/index.html
(note some *relative* links are broken and the 61 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/61-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-61-RC1 commons-parent-61-RC1
cd commons-parent-61-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/61-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: [email protected]
For additional commands, e-mail: [email protected]
