We have fixed a few bugs and added some enhancements since Apache
Commons Parent 56 was released, so I would like to release Apache
Commons Parent 57.
Apache Commons Parent 57 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/57-RC2
(svn revision 61436)
The Git tag commons-parent-57-RC2 commit for this RC is
21a0d410161312537687ab9188f9838af5bbd9e0 which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=21a0d410161312537687ab9188f9838af5bbd9e0
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-57-RC2 commons-parent-57-RC2
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1632/org/apache/commons/commons-parent/57/
These are the artifacts and their hashes:
#Release SHA-512s
#Sun Apr 23 10:21:43 EDT 2023
commons-parent-57-bom.json=465cc213bfafd2a47275ec9e7ada6ce7122486bce0c3e0191afd4b2dfb081a1bdd54d061bfc74e6911681d6470e87db54a785413099c495b4f69024bef6ad37f
commons-parent-57-bom.xml=2bba4d662318246b268ad78cc5a1774b348ac98a826e17e5a31cfad6ebb20974842d25fe44ddb8785cbb4564411096ae02671d7ab1a76ae4d119f95a24ddf365
commons-parent-57-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
commons-parent-57-src.tar.gz=fc57f72701b4e8d95a95fb972c8570c88e2976a9ac4270dea72bb961d46196ecdfee3cc9d5f7e18cf23a426412d0acdc15456955cd38707cd7ba3b34f877f2e6
commons-parent-57-src.zip=cccd197f9bad7bdbe39ef91717533d1007666039144ae1ab29934e074208d360f69e0a28d733f0cb25210fce3a8bd10e7d0c8fdc7f6f373e4148d2a548c856a8
org.apache.commons_commons-parent-57.spdx.json=6573ce664c4a0f0f940b649e77bd1ae4eb0130bdea29e6e861b50dfeb727bb73f22cdc708131b8accdfc44fc07a304ed51a47bf0d18632d2c4555f7e368f53e0
I have tested this with
mvn -V -Duser.name=$my_apache_id -Ddoclint=none -Prelease
-Ptest-deploy clean package site deploy
using:
Apache Maven 3.9.1 (2e178502fcdbffc201671fb2537d0cb4b4cc58f8)
Maven home: /usr/local/Cellar/maven/3.9.1/libexec
Java version: 1.8.0_362, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+362/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.3.1", arch: "x86_64", family: "mac"
Darwin **** 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar 6 21:00:17
PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64 x86_64
Details of changes since 56 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/57-RC2/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/commons-parent/57-RC2/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/57-RC2/site/index.html
(note some *relative* links are broken and the 57 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/57-RC2/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-57-RC2 commons-parent-57-RC2
cd commons-parent-57-RC2
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/commons-parent/57-RC2/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
