commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Tompkins <>
Subject [LAZY][VOTE] Release Apache Commons Release Plugin 1.6 based on RC1
Date Sat, 09 Mar 2019 13:53:02 GMT
We have fixed quite a few bugs and added some significant enhancements since Apache Commons
Release Plugin 1.5 was released, so I would like to release Apache Commons Release Plugin

Apache Commons Release Plugin 1.6 RC1 is available for review here: (svn revision

The Git tag commons-release-plugin-1.6-RC1 commit for this RC is 201c6ff24ca85355ece3574f788eca250c03b241
which you can browse here:;a=commit;h=201c6ff24ca85355ece3574f788eca250c03b241

You may checkout this tag using:
    git clone --branch commons-release-plugin-1.6-RC1

Maven artifacts are here:

These are the Maven artifacts and their hashes in Nexus:

#Nexus SHA-1s

#Release SHA-512s
#Sat Mar 09 08:30:24 EST 2019

I have tested this with 'mvn clean install site' using: 
Apache Maven 3.6.0 (97c98ec64a1fdfee7767ce5ffb20918da4f719f3; 2018-10-24T14:41:47-04:00)
Maven home: /usr/local/Cellar/maven/3.6.0/libexec
Java version: 1.8.0_191, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk1.8.0_191.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.14.3", arch: "x86_64", family: "mac"

Details of changes since 1.5 are in the release notes:

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

CLIRR Report (compared to 1.5):
RAT Report:


Please review the release candidate and vote.
This vote will close no sooner that 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,

Rob Tompkins, 
Release Manager (using key B6E73D84EA4FCC47166087253FAAD2CD5ECBB314)

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:

git clone -b commons-release-plugin-1.6-RC1
cd commons-release-plugin-1.6-RC1

2) Check Apache licenses:

mvn apache-rat:check

3) Build the package:

mvn -V clean package

You can record the Maven and Java version produced by -V in your VOTE reply.

4) Build the site for a single module project:

mvn site
Check the site reports in:

4) Build the site for a multi-module project:

mvn site
mvn site:stage
Check the site reports in:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message