[ X ] +1 Release these artifacts

Build passing for Oracle JDK 7, Oracle JDK 8, and IBM JDK 8.

Thanks a lot for preparing the release,
Bruno

________________________________
From: Benedikt Ritter <brit...@apache.org>
To: Commons Developers List <dev@commons.apache.org> 
Sent: Thursday, 8 June 2017 8:48 PM
Subject: [VOTE] Release Apache Commons Lang 3.6 based on RC3



Hello,


we have fixed quite a few bugs and added some nice new features since Commons 
Lang 3.5 was released, so I would like to release Commons Lang 3.6 based on RC3.

The following issues have been fixed since RC2:


- Site build now works from source distribution

- IBM JDK test failures have been fixed

- Automatic-Module-Name MANIFEST entry has been added for Java 9 compatibility


Commons Lang 3.6 R3 is available for review here:

https://dist.apache.org/repos/dist/dev/commons/lang (svn revision 19928)


The tag is here:

https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=tag;h=e454e79463ffbbd9114db43019dd211debbcc105


Commit ID the tag points at:

360198dfb6a2d68f1702f616dfacee34ae0541bb


Maven Artifacts:

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


These are the Maven artifacts and their hashes:


/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-javadoc.jar

(SHA1: c8adadb6c0b56c73f2cc2b4c77a09bfe34ec3a66)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-sources.jar.asc

(SHA1: 46347c179ca9246d146d653bdc7363bda6f17d44)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6.pom.asc

(SHA1: 1309d4f3dd41a01ff9dd1f3c1a6eee10dad1ef77)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6.pom

(SHA1: 0fb4499188c94c63b3cba44f12481e193708c4a8)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6.jar.asc

(SHA1: e67e7d44751f1e346c2fda496193cbe251cfe098)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-javadoc.jar.asc

(SHA1: 6b19fa12d319ced69c0f8a27001569514711f9dc)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-sources.jar

(SHA1: f89c1df082d6f67cb7c956715c56d7e7a0508d0a)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6.jar

(SHA1: e58ba08b01d37a023746f0987dcd910036a63021)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-tests.jar.asc

(SHA1: af050e8c29a801a5d6783268c56230b814f56240)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-test-sources.jar.asc

(SHA1: 71e4c11efb9e3b2eff402ba4648d21822fb8da4a)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-test-sources.jar

(SHA1: 04a0fc8293d4ed64a54dcc9ba5f996776a4657ea)

/org/apache/commons/commons-lang3/3.6/commons-lang3-3.6-tests.jar

(SHA1: 87993a16c14a251062e3fe860fa53b5ef5304a0f)


I have tested this with JDK 7, JDK 8 and JDK 9 EA b172 using Maven 3.5.0.


Details of changes since 3.5 are in the release notes:

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

  http://home.apache.org/~britter/commons/lang/LANG_3_6_RC3/changes-report.html


Site:

    http://home.apache.org/~britter/commons/lang/LANG_3_6_RC3

(note some *relative* links are broken and the 3.6 directories are

not yet created - these will be OK once the site is deployed)


Clirr Report (compared to 3.5):

  http://home.apache.org/~britter/commons/lang/LANG_3_6_RC3/clirr-report.html


RAT Report:

      http://home.apache.org/~britter/commons/lang/LANG_3_6_RC3/rat-report.html


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 11:00 CEST (UTC+2) 11-June 2017


[ ] +1 Release these artifacts

[ ] +0 OK, but...

[ ] -0 OK, but really should fix...

[ ] -1 I oppose this release because...


Thanks!

Benedikt

---------------------------------------------------------------------

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