Since Apache Commons Collections 4.5.0-M2 was released, we have fixed
a few bugs and added enhancements, so I would like to release Apache
Commons Collections 4.5.0-M3.

Apache Commons Collections 4.5.0-M3 RC1 is available for review here:
    https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M3-RC1
(svn revision 73699)

The Git tag commons-collections-4.5.0-M3-RC1 commit for this RC is
a67032e0e9d159f27a9ace79cf0ca183a881ba7a which you can browse here:
    
https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=a67032e0e9d159f27a9ace79cf0ca183a881ba7a
You may checkout this tag using:
    git clone https://gitbox.apache.org/repos/asf/commons-collections.git
--branch commons-collections-4.5.0-M3-RC1
commons-collections-4.5.0-M3-RC1

Maven artifacts are here:
    
https://repository.apache.org/content/repositories/orgapachecommons-1790/org/apache/commons/commons-collections4/4.5.0-M3/

These are the artifacts and their hashes:

#Release SHA-512s
#Sun Dec 15 15:25:41 UTC 2024
commons-collections4-4.5.0-M3-bin.tar.gz=bb35176a21316861b0bf1c8a46f9edcc737ac08d802e8c6461fdb4c33cbaf792f2a8a28ccf56bc561c6c935da7ed7351c3910f1ceacf2bd55d572b9a732d41d5
commons-collections4-4.5.0-M3-bin.zip=0b8765e632fc11b61cfc6ba8cff25351b3bc3200c04f1aa4d533366ea8f6557d34a056d9ba89d3287fddd020b0ea288c0ea7c792276530023c150344d082e844
commons-collections4-4.5.0-M3-bom.json=04302e7b983d994a05e3be4fbf8060a402551b723bfd6db201914cc08bab64fd5c1a057143770cb3809362206f48fcfb87280addfc1fee29d39e997335325c08
commons-collections4-4.5.0-M3-bom.xml=dd11ea1891841c4bb745b04f27f6c5cb02470074ed56d4b6c514c8c3037ffee3a0e4cf842358d41c92ba1dc52a38f110d32ac52834f927f12310b3e68bedf57a
commons-collections4-4.5.0-M3-javadoc.jar=3e628cf0d2185d183b4de69fd495b200b36508402ddf608e323d86facfb2776b6374fad410ca1740c701d51dd731af47cb045cad277269710985c2208fa38644
commons-collections4-4.5.0-M3-sources.jar=59ee55ced79379cf6ad2b145f00218fe6134264389a160b74e8b9320d8347556f572258b54f1706c90f7fad600a6f2ed343ada395f27d0d0da04c834c5448e14
commons-collections4-4.5.0-M3-src.tar.gz=770e8a99ce928c18ab1a5d2bb9fafaa5056a995a28f73a1098970084b8a360a7aa23087b841c51a4ffb181536f19f5a6ba7672fa4e6fde9d8b5cb26ec6705d4d
commons-collections4-4.5.0-M3-src.zip=325d9374fb815022bd13a6ccfdefd304c483260664966c9bc9b74ad5afe584fc9a271a602da50c926d865fb8d6191ab20198e34ec08b32644393b188b89965e3
commons-collections4-4.5.0-M3-test-sources.jar=1332980debf3c6f07c9fe8785c4eeb00620ff789b0b15293f971057974f547997e6b6d7cdde11bc9937ef3e2d30eaa7dd7fdb13ef66349a2dfb4b804bc5c477a
commons-collections4-4.5.0-M3-tests.jar=803308f367c1fb8a8b850770d35d27b0bbea0739817e387d3e3c0f1f481f89b44365d5dad2b0f978e50b2368492c4b7b59667bb6cfbac5cdeaa5e98dd18d6bd5
org.apache.commons_commons-collections4-4.5.0-M3.spdx.json=d890f8c0d84c6e1faf970a2b9f7b90bfde0ce32967a9e29930be8cce80ff889b65324dee2cb64b2d5d76629ae5ac7ed0f562dcc918fdf46c6967a22330715e4b



I have tested this with 'mvn' and 'mvn -V -Duser.name=$my_apache_id
-Prelease -P jacoco -P japicmp clean package site deploy' using:

openjdk version "21.0.5" 2024-10-15
OpenJDK Runtime Environment Homebrew (build 21.0.5)
OpenJDK 64-Bit Server VM Homebrew (build 21.0.5, mixed mode, sharing)

Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec
Java version: 21.0.5, vendor: Homebrew, runtime:
/opt/homebrew/Cellar/openjdk@21/21.0.5/libexec/openjdk.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "15.2", arch: "aarch64", family: "mac"

Darwin ****.local 24.2.0 Darwin Kernel Version 24.2.0: Fri Dec  6
19:03:40 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041 arm64
Docker version 27.3.1, build ce12230

Details of changes since 4.4 are in the release notes:
    
https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M3-RC1/RELEASE-NOTES.txt
    
https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M3-RC1/site/changes-report.html

Site:
    
https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M3-RC1/site/index.html
    (note some *relative* links are broken and the 4.5.0-M3
directories are not yet created - these will be OK once the site is
deployed.)

JApiCmp Report (compared to 4.4):
    
https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M3-RC1/site/japicmp.html

RAT Report:
    
https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M3-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-collections.git
--branch commons-collections-4.5.0-M3-RC1
commons-collections-4.5.0-M3-RC1
cd commons-collections-4.5.0-M3-RC1

1b) Download and unpack the source archive from:

https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M3-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: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to