My +1 Gary
On Sun, Mar 15, 2026 at 12:30 PM Gary Gregory <[email protected]> wrote: > > We have fixed a few bugs and added enhancements since the release of > Apache Commons Net 3.12.0, so I would like to release Apache Commons > Net 3.13.0. > > Apache Commons Net 3.13.0 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/net/3.13.0-RC1 (svn > revision 83089) > > The Git tag commons-net-3.13.0-RC1 commit for this RC is > 35fa0dff3e8660359832e72631ff3cf557b543a8, which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-net.git;a=commit;h=35fa0dff3e8660359832e72631ff3cf557b543a8 > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-net.git > --branch commons-net-3.13.0-RC1 commons-net-3.13.0-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1924/commons-net/commons-net/3.13.0/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Sun Mar 15 16:25:11 UTC 2026 > commons-net-3.13.0-bin.tar.gz=4827d6ea3cfcfba317dfac35c0ca013b737935253639302c274ebf2adeaa4d2fa36ccc36f92be32f76dd25c8bef72a116b308ca3e823b50af1b843f389c30b6f > commons-net-3.13.0-bin.zip=68c634bdd40c378f4b45ea4555c6f2799dbb489701a94a27df8f01d907063e5259b8399d0ecb603ce5be4740373add0e61add51891dd6633854ac8bc4a03d7e3 > commons-net-3.13.0-bom.json=b94a5e1a7764decfeff3c8ca82cc4aa8dbac5b9d34f5215f9d86ce4d294945176ff614df500b4ecd4a5c26ba841acdaf0b5886e7f43d2fe58f0dcaa9f90f81a2 > commons-net-3.13.0-bom.xml=17f84d3a77a3014fda9385eae0762f5502c4d283d2621a158b83663226675db02bb585c4c086c99e8071cb10392cd5cb6a1dc8488b884cc98527c1887670deb3 > commons-net-3.13.0-javadoc.jar=bb7d341e158956819c16769f9a2f74a4fdff1fb8474e2b9233244c10ef1aab89fc77beef8fe02b8bdc3ee94d6d9e1b060dce05d2604fd0fd188e759997061fc9 > commons-net-3.13.0-sources.jar=22b9e2c36690fe0807aa664f5d833bb357b4baaa42071bedc39a0dbdfebd73af4760b64f9156dab5d58604c4d22ebba46e6f7adc6f70d39453cadb187939d909 > commons-net-3.13.0-src.tar.gz=fda78dd1c0a49f331a3e25802613c2438c5cdfc5441c52e57cc7d2d5c7873df85133945b9fd620b26bcf98594106c8fedad6036f80e4bdc445c0af47b60af04e > commons-net-3.13.0-src.zip=113796bd7f6167565bd956f2e321edcf999270aecee0a23c6f4160f58b255e869fd1f1879fe3a623cfc77cdca56752d5db9d2c5f6c00b18b9928892d1286f8f3 > commons-net-3.13.0-test-sources.jar=6d802530f1acebe16ce7a4d4690dd615f2aba4a654323cde584b7933b5a73ada5e902eb75a763281a7aeaf918852c79805b0d05e5e95073c800ddd2d731bfaf8 > commons-net-3.13.0-tests.jar=044d0970d6ec7c531f4075b02c6ade2d56645cd3ad7ad6199d04cc2cb301f2b393dcf8fbbd9d3fb24731d4c3640a692c718d88d942c43f5e454c25ac24a95172 > commons-net-examples-3.13.0.jar=75082c08be86d6f8f58bfe189df8e18077d634d585a2d1ebc636dfb7ade088fd1943bf427c0cccd0fcf901d126c44186bfeb7969ed7bd479ced4aca6e635f48e > commons-net-ftp-3.13.0.jar=4147dd6836c0b3f5218420bfec6c348f59e51a98dcff56fa000a15d8f19596f14172404e270e0fa45807a9d8a0844637b8f20d29cb294e1226569bd37c3fc92e > commons-net_commons-net-3.13.0.spdx.json=a21b4470c204db0b47bae169d9bc4953cd62a69df156d91434371443f9ba06fc7223b4eea2392f35bdf31134ee05a172df915d1d4c2196a348722ba97526b7c7 > > > I have tested this with 'mvn' and 'mvn clean install site' using: > > openjdk version "21.0.10" 2026-01-20 > OpenJDK Runtime Environment Homebrew (build 21.0.10) > OpenJDK 64-Bit Server VM Homebrew (build 21.0.10, mixed mode, sharing) > > Apache Maven 3.9.14 (996c630dbc656c76214ce58821dcc58be960875b) > Maven home: /opt/homebrew/Cellar/maven/3.9.14/libexec > Java version: 21.0.10, vendor: Homebrew, runtime: > /opt/homebrew/Cellar/openjdk@21/21.0.10/libexec/openjdk.jdk/Contents/Home > Default locale: en_US, platform encoding: UTF-8 > OS name: "mac os x", version: "26.3.1", arch: "aarch64", family: "mac" > > Darwin Garys-MacBook-Pro.local 25.3.0 Darwin Kernel Version 25.3.0: > Wed Jan 28 20:51:28 PST 2026; > root:xnu-12377.91.3~2/RELEASE_ARM64_T6041 arm64 > > Docker version 29.2.1, build a5c7197 > > > Details of changes since 3.12.0 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/net/3.13.0-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/net/3.13.0-RC1/site/changes.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/net/3.13.0-RC1/site/index.html > (Note some *relative* links are broken and the 3.13.0 directories > are not yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 3.12.0): > > https://dist.apache.org/repos/dist/dev/commons/net/3.13.0-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/net/3.13.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 530AA5F25C25011F) > > 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/net/3.13.0-RC1/source > > 1b) Check out the RC tag from git (optional) > > This is optional, as a reviewer must at least check source distributions. > > git clone https://gitbox.apache.org/repos/asf/commons-net.git --branch > commons-net-3.13.0-RC1 commons-net-3.13.0-RC1 > cd commons-net-3.13.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 > > -the end- --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
