Re: [VOTE] Release Apache Commons Text 1.8 based on RC1

[Gary Gregory <ga...@gmail.com>]

My +1

Gary


On Fri, Aug 30, 2019 at 4:06 PM Gary Gregory <ga...@gmail.com> wrote:

> We have fixed quite a few bugs and added some  enhancements since Apache
> Commons Text 1.7 was released, so I would like to release Apache Commons
> Text 1.8.
>
> Apache Commons Text 1.8 RC1 is available for review here:
>     https://dist.apache.org/repos/dist/dev/commons/text/1.8-RC1 (svn
> revision 35474)
>
> The Git tag commons-text-1.8-RC1 commit for this RC is
> b63df8d66e8306b2608c16be3661248348e78a2f which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=b63df8d66e8306b2608c16be3661248348e78a2f
> You may checkout this tag using:
>     git clone https://gitbox.apache.org/repos/asf/commons-text.git
> --branch commons-text-1.8-RC1 commons-text-1.8-RC1
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1462/org/apache/commons/commons-text/1.8/
>
> These are the artifacts and their hashes:
>
> #Release SHA-512s
> #Fri Aug 30 15:57:03 EDT 2019
>
> commons-text-1.8-bin.tar.gz=bc40b63519308f6361d3bb206a7affd52429eb07d63d17ff4ea1f9304115b84448f69e376d93050105ab2d08b639dc5615c5c962347c17bc89abc41e1995f351
>
> commons-text-1.8-bin.zip=0f15f8e87453b959a38be6ff439360cee7b192cf535f4a0cdec702d042af0e85cffb1257d4732bb2603f8326392e54504c050aff5319064f8a1523267dccf798
>
> commons-text-1.8-javadoc.jar=c84918cf93104e62807c1a21e11e03139c9dab8879e505a01e66f9821b73db25de449c200e1645d5b340799beb47a051674c27448d79b3e3088f4b2d004f0e47
>
> commons-text-1.8-sources.jar=732edde41145d05ae37c398799d9b7d337643579be52e5c8319dc05fd1a89bfd5ce492ed1de6a9e812180ebcf8a9c3c54991b01578c62af526ec2b45526662a0
>
> commons-text-1.8-src.tar.gz=7e0bd5bf45c4cffd325f28eee0e8b1b26729c0805f7dabf4a92c82344e86aa1f3b248d78026696e5a0694155e9a0d2470768ce47a8413c23526001e914097594
>
> commons-text-1.8-src.zip=033930730290fc355b79aba9aed83a4dae8622b0a0cb8924345f0cbf5257054d92f20340872208adfa946072d3e7fa121303af614830204b91c2f273b3d9e275
>
> commons-text-1.8-test-sources.jar=b303063a7c9a324da09127303a28945f03c4650becf38635e8ddc6a3bfb3432652ccbc8b924fc46fbdc5ab52460ab28b0a94fc66da2864a41fb5f7c96a58eb6d
>
> commons-text-1.8-tests.jar=c1bed5f313b38df69ec3f1292cd7ab4e5ea7f7d30956c1e08990d28d64be0c78000020435bdee4818672e25f7963054940b436d9d98fb99f18e6474371ceaf80
>
>
> I have tested this with 'mvn -V -Ddoclint=none -Prelease -Pjacoco
> -Ptest-deploy clean package site deploy' using:
>
> Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555;
> 2019-04-04T15:00:29-04:00)
> Maven home: C:\Java\apache-maven-3.6.1\bin\..
> Java version: 1.8.0_221, vendor: Oracle Corporation, runtime: C:\Program
> Files\Java\jdk1.8.0_221\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>
> Details of changes since 1.7 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.8-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.8-RC1/site/changes-report.html
>
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.8-RC1/site/index.html
>     (note some *relative* links are broken and the 1.8 directories are not
> yet created - these will be OK once the site is deployed.)
>
> CLIRR Report (compared to 1.7):
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.8-RC1/site/clirr-report.html
>
> JApiCmp Report (compared to 1.7):
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.8-RC1/site/japicmp.html
>
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.8-RC1/site/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.
>
>   [ ] +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 https://gitbox.apache.org/repos/asf/commons-text.git --branch
> commons-text-1.8-RC1 commons-text-1.8-RC1
> cd commons-text-1.8-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
> packaged.
>
> mvn site
> Check the site reports in:
> - Windows: target\site\index.html
> - Linux: target/site/index.html
>
> 6) Build the site for a multi-module project
>
> mvn site
> mvn site:stage
> Check the site reports in:
> - Windows: target\site\index.html
> - Linux: target/site/index.html
>
> -the end-
>