This vote passes with the following +1 votes cast: - Bruno P. Kinoshita, binding - Rob Tompkins , binding - Amey Jadiye, non-binding - Gary Gregory, binding
Gary On Fri, Jul 24, 2020 at 9:22 AM Gary Gregory <garydgreg...@gmail.com> wrote: > My +1 > > Gary > > > On Tue, Jul 21, 2020 at 4:56 PM Gary Gregory <ggreg...@apache.org> wrote: > >> Hi All, >> >> We have fixed a few bugs and added some enhancements since Apache Commons >> Text 1.8 was released, so I would like to release Apache Commons Text 1.9. >> >> Apache Commons Text 1.9 RC1 is available for review here: >> https://dist.apache.org/repos/dist/dev/commons/text/1.9-RC1 (svn >> revision 40617) >> >> The Git tag commons-text-1.9-RC1 commit for this RC is >> cb85bed468e99d34b88d0c81fe20eb3b1615660e which you can browse here: >> >> https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=cb85bed468e99d34b88d0c81fe20eb3b1615660e >> You may checkout this tag using: >> git clone https://gitbox.apache.org/repos/asf/commons-text.git >> --branch commons-text-1.9-RC1 commons-text-1.9-RC1 >> >> Maven artifacts are here: >> >> https://repository.apache.org/content/repositories/orgapachecommons-1508/org/apache/commons/commons-text/1.9/ >> >> These are the artifacts and their hashes: >> >> #Release SHA-512s >> #Tue Jul 21 16:40:42 EDT 2020 >> >> commons-text-1.9-bin.tar.gz=02d4f9bc28aad82c461c5e9b1ceeaa3e8f4ece93e70918f79c090f6e2e5d8b4053944b67f70c4db7e2bb3311194484916440e030aea13f8b2fa76416b052740a >> >> commons-text-1.9-bin.zip=2a6873186e69271edf038b6dfb986fee80970f32dd71a587578b1964e9c3ebdd38645fdd1c3b82b27a9235695ed3a8bf7206e996414417740110507078e67392 >> >> commons-text-1.9-javadoc.jar=ee587b5994bd3b0fdb5d3ba322e9a76ca427476a9480fab769c0f3b6145843fa672b89d8fd8498a809a65a1c802e585a75ca91bccc82fc30aa658bc71042e5a6 >> >> commons-text-1.9-sources.jar=9f09fae39b37a18101754ee65ba13e53909337644cacfbc4a86798b3fb1e23317c2c849a9975b077e72fa2f91f8af30c6ac10664ec11d6107a225b445cc93ae7 >> >> commons-text-1.9-src.tar.gz=53f993e79aaa6789d3388aa96b6b2a14cf646b27ff3774524390e511241a85288947cc929519eff61a8734578f25bdf3d9969d84da20c1a749b19d90a55da8ae >> >> commons-text-1.9-src.zip=455f3f1552d2b88496c5e9dee0a39f7bd42ff413e9b055eae5c6cc9bb122a55bfe3de7481acce5406fe0aef247b78d1a9f90a0a43ba69f7f7288610323aa742f >> >> commons-text-1.9-test-sources.jar=0ca935e0c3326bbc2627f9e2099fb1950643882ef268c14513f1fac46e8e779d3904f70c7eca20c9e905876efd18a1b1a6b747fc6375fcb15231149ac0371de6 >> >> commons-text-1.9-tests.jar=295a36064cdce3b2f7b6c51d19c2391ec53456019ac4a16f76085cd69f39958e7becc8ede3b6391d7bf19ec53afb513f13db884ac152f8749247d1df973ff75e >> >> I have tested this with >> >> mvn -V -Duser.name=%my_apache_id% >> -Dcommons.release-plugin.version=%commons.release-plugin.version% -Prelease >> -Ptest-deploy -P jacoco -P japicmp clean package site deploy >> >> using: >> >> 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 >> Files\Java\jdk1.8.0_251\jre >> Default locale: en_US, platform encoding: Cp1252 >> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" >> >> Details of changes since 1.8 are in the release notes: >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.9-RC1/RELEASE-NOTES.txt >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.9-RC1/site/changes-report.html >> >> Site: >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.9-RC1/site/index.html >> (note some *relative* links are broken and the 1.9 directories are >> not yet created - these will be OK once the site is deployed.) >> >> JApiCmp Report (compared to 1.8): >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.9-RC1/site/japicmp.html >> >> RAT Report: >> >> https://dist.apache.org/repos/dist/dev/commons/text/1.9-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.9-RC1 commons-text-1.9-RC1 >> cd commons-text-1.9-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 >> >> -the end- >> >>
