+1 > On Apr 19, 2025, at 10:11 AM, Gary Gregory <garydgreg...@gmail.com> wrote: > > We have fixed a few bugs and added enhancements since Apache Commons > Collections 4.5.0-M3 was released, so I would like to release Apache > Commons Collections 4.5.0. > > Apache Commons Collections 4.5.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-RC1 > (svn revision 76376) > > The Git tag commons-collections-4.5.0-RC1 commit for this RC is > 7f7fb0244abc940a2e9dd28b67508c0483a58c3e which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=7f7fb0244abc940a2e9dd28b67508c0483a58c3e > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-collections.git > --branch commons-collections-4.5.0-RC1 commons-collections-4.5.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1829/org/apache/commons/commons-collections4/4.5.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sat Apr 19 13:59:46 UTC 2025 > commons-collections4-4.5.0-bin.tar.gz=4aa80e2a7d9724befed334e5fa2770947c1691545d0f31f153c25cc3bfc4a3ef6ce6b5e07d61b531f2600cffa39b92519aafb6e98d4a20061a8dc3ef999ba65a > commons-collections4-4.5.0-bin.zip=1a9d624afdcaf170b41dd0950b895b699a1c6aee4e5c44a172b1da5947bed6fa656ad54c62d1668d7b579bc2dd1bba8319e3d98d6c61a92265da55013e46124b > commons-collections4-4.5.0-bom.json=90c278a7499b5df075b2b1928833fa5f6797f80aaf2bb5f41b8a7ad5c7deece87b9015571a7912bee1ea11db7532d74388eff8191e828c3bbfa83ac7fb705036 > commons-collections4-4.5.0-bom.xml=484aeb754f26679be307f76494d8a28f7c92543c6636002f8c4ba391bb0d59b97344dd3c78000fe36c0835626e14f71079e4d6dce42852864a977bfb12e2f39a > commons-collections4-4.5.0-javadoc.jar=b49097b887ed9843b9e8471b701f48f737628e6ec5ac7395853c88c7ef67491dbdaef585c236eae5955dbc5561e3f90b8f33df159340a25bf8bedaafcfb4600c > commons-collections4-4.5.0-sources.jar=a4fee5c097742b56ac407acd77a57fa2e755b65296e137e6762337a2faea901f19dd57ee22b1914c48e3120ef47778d210b07502456ec8c09e7933d4bcf2eb15 > commons-collections4-4.5.0-src.tar.gz=2a52a6b01cbef34185d9ff8df872db4a6a6b84d7be9982b331cfb6ff5d1b55f501e19e02930f904408048f5657d98aaa33d32e27faa66abe9dd9cc6213318984 > commons-collections4-4.5.0-src.zip=b1eae760d5208e308000c23d08e21b1512424651cd3961f689b468f15e524badedb9aaabcbe2a1ff84a9f0cc3d8cdd52e7b18002f5760e65daf5be317ea3b2ca > commons-collections4-4.5.0-test-sources.jar=4f7562730fbb39d01fd995087b39ad77af446320fafee596bf5d2c3d9f08eb6cae143b3e74d991166b2057468d643c7e5cfb0c40e5842973dd63258fc815e888 > commons-collections4-4.5.0-tests.jar=ba362c2ef85eb4829d1025ad2a58e5d9a857ee7b3bccc93118ce5c5be41d6ff55e75bfe23b216ba47c9e6c804b379e7ee50d9c27c729ac87ec8ae9dbb4e96e7e > org.apache.commons_commons-collections4-4.5.0.spdx.json=ccadebc6f86ead8fa6915b056cd2fc2aa979bfbb15d7012431fce28eac55d398bc3082b3c476e425f966c969729ec069caac2894a3bfaf212ade6d779a2864cb > > > I have tested this with 'mvn' and 'mvn -e -V -P release -P test-deploy > -P jacoco -P japicmp clean package site deploy' using: > > openjdk version "23.0.2" 2025-01-21 > OpenJDK Runtime Environment Homebrew (build 23.0.2) > OpenJDK 64-Bit Server VM Homebrew (build 23.0.2, mixed mode, sharing) > > Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937) > Maven home: /opt/homebrew/Cellar/maven/3.9.9/libexec > Java version: 23.0.2, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk/23.0.2/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "15.4.1", arch: "aarch64", family: "mac" > > Darwin ****.local 24.4.0 Darwin Kernel Version 24.4.0: Fri Apr 11 > 18:32:50 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T6041 arm64 > > Docker version 28.0.4, build b8034c0 > > > Details of changes since 4.4 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-RC1/site/index.html > (note some *relative* links are broken and the 4.5.0 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-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-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, and Maven. > > You can validate a release from a release candidate (RC) tag as follows. > > 1a) Download and decompress the source archive from: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must check source distributions as a minimum. > > git clone https://gitbox.apache.org/repos/asf/commons-collections.git > --branch commons-collections-4.5.0-RC1 commons-collections-4.5.0-RC1 > cd commons-collections-4.5.0-RC1 > > 2) Checking the build > > All components should include a default Maven goal, such that you can > run 'mvn' from the command line by itself. > > 2) Check Apache licenses > > This step is not required if the site includes a RAT report page which > you then must check. > This check should be included in the default Maven build, but you can > check it with: > > mvn apache-rat:check > > 3) Check binary compatibility > > This step is not required if the site includes a JApiCmp report page > which you then must check. > This check should be included in the default Maven build, but you can > check it with: > > mvn verify -DskipTests -P japicmp japicmp:cmp > > 4) Build the package > > This check should be included in the default Maven build, but you can > check it with: > > 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 > > 4b) Check reproducibility > > To check that a build is reproducible, run: > > mvn clean verify artifact:compare -DskipTests > -Dreference.repo=https://repository.apache.org/content/repositories/staging/ > '-Dbuildinfo.ignore=*/*.spdx.json' > > Note that this excludes SPDX files from the check. > > 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 > > 6) Build the site for a multi-module project > > mvn site > mvn site:stage > Check the site reports in: > - Windows: target\site\index.html > - Linux: target/site/index.html > > Note that the project reports are created for each module. > Modules can be accessed using the 'Project Modules' link under > the 'Project Information' menu (see <path-to-site>/modules.html). > > -the end- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org >
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
