We have fixed a few bugs and added enhancements since Apache Commons Parent
76 was released, so I would like to release Apache Commons Parent 77.
Apache Commons Parent 77 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/77-RC1 (svn
revision 72148)
The Git tag commons-parent-77-RC1 commit for this RC is
80a06beec388a53716605075a35c8ce03e922b3d which you can browse here:
https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=80a06beec388a53716605075a35c8ce03e922b3d
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
--branch commons-parent-77-RC1 commons-parent-77-RC1
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-1782/org/apache/commons/commons-parent/77/
These are the artifacts and their hashes:
#Release SHA-512s
#Sat Oct 05 19:08:22 UTC 2024
commons-parent-77-bom.json=28648a6f96857b61542d92a165dcd932105bc33668db5a27b2b1d7d5c8509926c802fcca3b8f1118e32ea6c70379dc471995a5431672b4074b5141ba7ecfd321
commons-parent-77-bom.xml=9ad5bd716356981e42b07f7f0c6023e42952070152dced3c2d8691b4d3c67d5b614508d90ee988fb31d5148345113b253bb7fba6a680b35adaa234818e9e46fb
commons-parent-77-site.xml=67d93a8bd57621ef1ff9b3576e8708fe2e95a9e33ca3c37959dec286ebb14f518a987d4e20d72e4bc595bf7a623794c864ffca3202dfe02c227caad37b5a7bd8
commons-parent-77-src.tar.gz=bc693c6c9333b1576fe4c565fd36376b295cd27000fba515c4f2b0aa6fb975dd8ee82bf2caa72ce7afd06ffed9c81f6b405e45d1b601044e056357afabb78616
commons-parent-77-src.zip=2e2689d68dae093cc1ab56eabd2bf0d8056d143a3888deb26e779a79dbc29ed3a2b6cbeb52599641ae4df10175553d37cf4d15c77675567f019b92fe7afc9cb1
org.apache.commons_commons-parent-77.spdx.json=3bd8f74e92d2834b381c6080d9a29e5c025a2dbf25fa61dbbec44a8b881d8551aea5f7e982b3f28abd8dd65a7e315172a3ad0516191c3be02afa7a67156d87b0
I have tested this with 'mvn' and 'mvn -e -V -Prelease -Ptest-deploy -P
jacoco -P japicmp clean package site deploy' using:
openjdk version "17.0.12" 2024-07-16
OpenJDK Runtime Environment Homebrew (build 17.0.12+0)
OpenJDK 64-Bit Server VM Homebrew (build 17.0.12+0, mixed mode, sharing)
Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /usr/local/Cellar/maven/3.9.9/libexec
Java version: 17.0.12, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@17/17.0.12/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.0.1", arch: "x86_64", family: "mac"
Darwin ---- 24.0.0 Darwin Kernel Version 24.0.0: Tue Sep 24 23:36:30 PDT
2024; root:xnu-11215.1.12~1/RELEASE_X86_64 x86_64
Details of changes since 76 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/parent/77-RC1/RELEASE-NOTES.txt
https://dist.apache.org/repos/dist/dev/commons/parent/77-RC1/site/changes-report.html
Site:
https://dist.apache.org/repos/dist/dev/commons/parent/77-RC1/site/index.html
(note some *relative* links are broken and the 77 directories are not
yet created - these will be OK once the site is deployed.)
RAT Report:
https://dist.apache.org/repos/dist/dev/commons/parent/77-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,
Gary Gregory,
Release Manager (using key 86fdc7e2a11262cb)
The 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-77-RC1 commons-parent-77-RC1
cd commons-parent-77-RC1
1b) Download and unpack the source archive from:
https://dist.apache.org/repos/dist/dev/commons/parent/77-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-
