commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bruno P. Kinoshita" <>
Subject Re: [VOTE] Release Apache Commons Net 3.7.2 based on RC1
Date Wed, 14 Oct 2020 21:16:50 GMT
   [x] +1 Release these artifacts

Built from tag with Maven 3.5.4 and Java 8. Build passing OK, reports look good.
Checked signatures, found no issues. Inspected some files in binary/source folders of the
dist area, all looking good.
Thanks for managing this release Gary.


    On Thursday, 15 October 2020, 5:20:05 am NZDT, Gary Gregory <>
 We have fixed a few bugs since Apache Commons Net 3.7.1 was released, so I
would like to release Apache Commons Net 3.7.2.

Apache Commons Net 3.7.2 RC1 is available for review here: (svn
revision 41933)

The Git tag commons-net-3.7.2-RC1 commit for this RC is
deeb863e66598f51aac6410a85b814f721542ffe which you can browse here:;a=commit;h=deeb863e66598f51aac6410a85b814f721542ffe
You may checkout this tag using:
    git clone --branch
commons-net-3.7.2-RC1 commons-net-3.7.2-RC1

Maven artifacts are here:

These are the artifacts and their hashes:

#Release SHA-512s
#Wed Oct 14 12:02:40 EDT 2020

I have tested this with:

mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site


Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Java\apache-maven-3.6.3\bin\..
Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Details of changes since 3.7.1 are in the release notes:

    (note some *relative* links are broken and the 3.7.2 directories are
not yet created - these will be OK once the site is deployed.)

    CLIRR Report (compared to 3.7.1):

    JApiCmp Report (compared to 3.7.1):

RAT Report:


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.

1) Clone and checkout the RC tag

git clone --branch
commons-net-3.7.2-RC1 commons-net-3.7.2-RC1
cd commons-net-3.7.2-RC1

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

mvn site
Check the site reports in:
- Windows: target\site\index.html
- Linux: target/site/index.html

-the end-
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message