Seeing other comments and votes, I believe there are no blockers, just a few 
things that need to be fixed.

So +0


Cheers
Bruno



________________________________
From: Bruno P. Kinoshita <brunodepau...@yahoo.com.br.INVALID>
To: Commons Developers List <dev@commons.apache.org> 
Sent: Thursday, 14 December 2017 12:11 AM
Subject: Re: [VOTE] Release Commons JCS 2.2.1 based on RC3



Hi,

Building from tag with `mvn clean install`. Build passing OK with Java 8, with 
the following environment settings:

Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 
2017-10-18T20:58:13+13:00)
Maven home: /opt/apache-maven-3.5.2
Java version: 1.8.0_151, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-103-generic", arch: "amd64", family: "unix"


Checked signatures from Maven artefacts. Everything looks OK.

There is some strange text in the release notes at the dist files and at the 
dist area (https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-NOTES.txt)


--- snip ---

$release.description.replaceAll("  ", "
") 
--- snip ---

Not sure if intentional, but I think it was some script that didn't run 
correctly? Don't have enough experience with the release process to tell 
whether that's correct or not, nor what could have happened exactly, sorry. Is 
it a blocker?

Could not create the site with `mvn clean test site` due to Java 8 issues in 
Javadocs, and found nothing in the BUILDING.txt. So built the site with `mvn 
clean test install site -Dmaven.javadoc.skip=true`

Reports look good, found no blockers. Few more PMD issues in one of the 
modules, but look like simple warnings.

Unless the release notes is a blocker, I'm ready to cast a vote in favor to 
release it (-:


Thanks for preparing the release Romain

Cheers
Bruno



________________________________

From: Romain Manni-Bucau <rmannibu...@gmail.com>
To: Commons Developers List <dev@commons.apache.org> 
Sent: Wednesday, 13 December 2017 9:03 PM
Subject: [VOTE] Release Commons JCS 2.2.1 based on RC3



As discussed quite verbosely already I'd like to release JCS 2.2.1. I

followed the commons procedure this time and hope it works for you.


JCS 2.2.1 RC3 is available for review here:

    https://dist.apache.org/repos/dist/dev/commons/jcs/ (svn revision 23702)


The tag is here:


http://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2.1-RC3/

(svn revision 1817933)


Maven artifacts are here:

    https://repository.apache.org/content/repositories/orgapachecommons-1298


I have tested this with JDK 7, 8 using Maven 3.5.0.


Details of changes since 2.2 are in the release notes:

    https://dist.apache.org/repos/dist/dev/commons/jcs/RELEASE-NOTES.txt


http://home.apache.org/~rmannibucau/commons-jcs-2.2.1-RC3/changes-report.html


Site:

        http://home.apache.org/~rmannibucau/commons-jcs-2.2.1-RC3/


Clirr Report (compared to 2.2):


http://home.apache.org/~rmannibucau/commons-jcs-2.2.1-RC3/commons-jcs-core/clirr-report.html


RAT Report:


http://home.apache.org/~rmannibucau/commons-jcs-2.2.1-RC3/rat-report.html

(the zipcodes.txt file is intended to not have headers)


KEYS:

  https://www.apache.org/dist/commons/KEYS


Please review the release candidate and vote.

This vote will close no sooner that 72 hours from now,

i.e. sometime after 08:15 UTC 16-December 2017


  [ ] +1 Release these artifacts

  [ ] +-0 Don't care

  [ ] -1 I oppose this release ${because}


Thanks!

Romain

---------------------------------------------------------------------
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

Reply via email to