My vote: +1 Release these artifact. On Sun, Mar 31, 2024 at 6:19 PM Gary Gregory <garydgreg...@gmail.com> wrote:
> We have fixed a few bugs and added enhancements since Apache Commons > Collections 4.4 was released, so I would like to release Apache > Commons Collections 4.5.0-M1. > > Apache Commons Collections 4.5.0-M1 RC1 is available for review here: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1 > (svn revision 68212) > > The Git tag commons-collections-4.5.0-M1-RC1 commit for this RC is > 2f8305d6a268d51e4b41e183f6d8b61c3c1ef99b which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=2f8305d6a268d51e4b41e183f6d8b61c3c1ef99b > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-collections.git > --branch > <https://gitbox.apache.org/repos/asf/commons-collections.git--branch> > commons-collections-4.5.0-M1-RC1 > commons-collections-4.5.0-M1-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1711/org/apache/commons/commons-collections4/4.5.0-M1/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Mar 31 16:04:35 UTC 2024 > > commons-collections4-4.5.0-M1-javadoc.jar=c5bc0c8d481c4120e2e16d9f7c762dd6bdca8e215f9782a6d4da0444133839c9f25ef97d1b981b16fefa306969aba7bfefad42f261990897e06250e7a0c893c0 > > commons-collections4-4.5.0-M1-test-sources.jar=63e6c0888b1c8ed992968a329ff61e1309292dbac1743de68180d66a4b945baa7c7b5c415a14f179fe8ad27a782374f6a78e36e7d1fb34ec5133fe0a86d836aa > > org.apache.commons_commons-collections4-4.5.0-M1.spdx.json=5bbb207506f97064a04da82b9f6be20610818f07f77e00a18c33aea65cc1e6228860088bdfefd6ee52411563ab1f96ae9baea688806c2c6ba2d15278ba1d2706 > > commons-collections4-4.5.0-M1-src.zip=51cf6b96a2110d5c0f73bda94d377fb96391bb5b3f2636fb253fc1beaca23a50f6988008d4e824b3a709aecd9df316df0fb8c71925f0d7a970014a33fce7fcde > > commons-collections4-4.5.0-M1-bom.xml=fc7d0a283aaa4e7559705cdf4b69479379a9deda422123222af87f121f70600bc1939c055e6add0ef900abb7c2172af7ecfa53f2bd0f5808db9d4befd9fc4486 > > commons-collections4-4.5.0-M1-bom.json=965229073d7f9fd63212ad65fcc943d76ed9569a2e1cbbe7ebd97ff442461914be83a96ac957095d478dbfdb9c805b30325fd3f5e3118d50ce50c91d06ec7e3b > > commons-collections4-4.5.0-M1-bin.zip=a016e7cde33c7ffcf03b9f899582babff802d98f22d9a292ce204dc0867b050c83cc8815f2cfc66d7ba721c7792cf81963405bdbe9f4cde1eaf376be3db6fd4c > > commons-collections4-4.5.0-M1-tests.jar=02f4d82750827b4c322a03ea52de1d4ae9c28168480ee49c20e790bb8fe9cf6df41f00cb4d44d90486e9eb17c7df1ed38e000aafea247109b92970f48db64611 > > commons-collections4-4.5.0-M1-bin.tar.gz=fe8ddd1a9ca34e43753a41718e56e408ff7f9a1ca1c9e2fb0a457ebb07e4debed2ed95a214e78e07e03609048b92076dedfda1065f69cba7ef82d1b615554e8e > > commons-collections4-4.5.0-M1-sources.jar=f041903fcf3702f15f0a042d96880c1f84aed249d05a6c791cb0b099d711bda43b0d3ca7d1fbac14b1ab3780f6032eafe5045c559b68308a692634d9475535f3 > > commons-collections4-4.5.0-M1-src.tar.gz=0aefd67c7f027ebfa90ec975f9088d17326d2599c56d3d2f926597f69247290bdda5fc601f740997315514b8e3bfae9511afda61680e90d0b466df17220854a9 > > I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P > jacoco -P japicmp clean package site deploy' using: > > openjdk version "17.0.10" 2024-01-16 > OpenJDK Runtime Environment Homebrew (build 17.0.10+0) > OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing) > > Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae) > Maven home: /usr/local/Cellar/maven/3.9.6/libexec > Java version: 17.0.10, vendor: Homebrew, runtime: > /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac" > > Darwin **** 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05 > PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64 > > Details of changes since 4.4 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/site/index.html > (note some *relative* links are broken and the 4.5.0-M1 > 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-M1-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-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) > > 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-collections.git > --branch > <https://gitbox.apache.org/repos/asf/commons-collections.git--branch> > commons-collections-4.5.0-M1-RC1 > commons-collections-4.5.0-M1-RC1 > cd commons-collections-4.5.0-M1-RC1 > > 1b) Download and unpack the source archive from: > > > https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-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 > > -- Ing. Tomas Lanik CEO KvantaNet s.r.o. Školská 689/20 110 00 Praha 1 Czech Republic Phone: +420 777 407 074 E-mail: tomas.la...@kvantanet.com E-mail: resea...@kvantanet.com WWW: https://www.kvantanet.com/ <http://www.kvantanet.com/>
