Yes, thanks everyone for helping. Was a long journey to get here. On Tue, Sep 1, 2020 at 11:32 AM Alex Remily <alex.rem...@gmail.com> wrote:
> Thank you to everyone involved for their part in getting this out. > > On Tue, Sep 1, 2020 at 11:58 AM Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > This VOTE passes with the following +1s: > > > > - Alex Remily > > - Geoffrey Blake > > - Bruno P. Kinoshita, binding > > - Rob Tompkins, binding > > - Gary Gregory, binding > > > > Thank you all, > > Gary > > > > On Tue, Sep 1, 2020 at 11:52 AM Gary Gregory <garydgreg...@gmail.com> > wrote: > > > > > My +1. > > > > > > Gary > > > > > > On Fri, Aug 28, 2020 at 4:35 PM Gary Gregory <ggreg...@apache.org> > wrote: > > > > > >> We have fixed quite a few bugs and added some significant enhancements > > >> since Apache Commons Crypto 1.0.0 was released, so I would like to > release > > >> Apache Commons Crypto 1.1.0. > > >> > > >> Apache Commons Crypto 1.1.0 RC1 is available for review here: > > >> https://dist.apache.org/repos/dist/dev/commons/crypto/1.1.0-RC1 > (svn > > >> revision 41177) > > >> > > >> The Git tag commons-crypto-1.1.0-RC1 commit for this RC is > > >> 3b2561bcdd9a428d01235a3d646cd08fbb6e597a which you can browse here: > > >> > > >> > https://gitbox.apache.org/repos/asf?p=commons-crypto.git;a=commit;h=3b2561bcdd9a428d01235a3d646cd08fbb6e597a > > >> You may checkout this tag using: > > >> git clone https://gitbox.apache.org/repos/asf/commons-crypto.git > > >> --branch commons-crypto-1.1.0-RC1 commons-crypto-1.1.0-RC1 > > >> > > >> Maven artifacts are here: > > >> > > >> > https://repository.apache.org/content/repositories/orgapachecommons-1524/org/apache/commons/commons-crypto/1.1.0/ > > >> > > >> These are the artifacts and their hashes: > > >> > > >> #Release SHA-512s > > >> #Fri Aug 28 16:20:02 EDT 2020 > > >> > > >> > commons-crypto-1.1.0-bin.tar.gz=a7c65d04bce6f6e415de5f818b9d13953bf819884e343ea47465a67ac8caaeb017dd54a1a7b3b47aab4a71f94fe9a2b8af7ba505b9d2d4786e90d095c3befa48 > > >> > > >> > commons-crypto-1.1.0-bin.zip=5493b9b7967695efcb0c804fa3f3d27f66c3964b4a867c4e0ac3b92d116b71bce655254965092c8252882dd039e52b4386e42b8d306941811a839873a4c1e66a > > >> > > >> > commons-crypto-1.1.0-javadoc.jar=f37c1cadda93e87a5447cc6458d87441f03c0a4667ac2b647685b405b4b84f99bfbd6802741836a526303240671fcc0f89daabc851a6b31ecbf883f78b4bceed > > >> > > >> > commons-crypto-1.1.0-sources.jar=ed487f0100ca65ca6d5d0a7998a2ae86b2ed47f67040f3e5d60b0c27e145d9c64e79c51c3c179f4d7e06babd0c4fd1ed571ce58bf1190dd86a1c04d5cdc7a7f9 > > >> > > >> > commons-crypto-1.1.0-src.tar.gz=f5ad97c8fdc722ff633b62e1653fb094bd95a7c0629fd7d203c3760ff4d99d665d415ea4180ed522021835f27ac0b4a17e2cd547e52705a8e3b99c1272a56436 > > >> > > >> > commons-crypto-1.1.0-src.zip=3d877f5417d5446a79defa5c7575f903f37d8fcb19746a474f87ae6c39250cea8b2865238512892cc6f9394a590cbe4aa2cb80dde0333371e6731666c14625b9 > > >> > > >> > commons-crypto-1.1.0-test-sources.jar=7d120012f27caa98362a2d871edec226a3910f17265ae0c8d8f889370c096e5413c43dc0a106aa163aaf0809ca1d90ee1af81641c21a1f3f8556f1d1b1979e41 > > >> > > >> > commons-crypto-1.1.0-tests.jar=35d769a1a7f0a8163e3bbb16880476cf0fc33d80c56da280901fe2c9e0e31162e7b8d39a8c7973b0b72295defb9bd13be9c2e2d2e225572b209fa8c70e5dddbc > > >> > > >> 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 package site deploy' plus building > in > > >> Docker to produce the various native binaries using: > > >> > > >> Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) > > >> Maven home: /opt/apache-maven-3.6.3 > > >> Java version: 1.8.0_265, vendor: AdoptOpenJDK, runtime: > > >> /Library/Java/JavaVirtualMachines/adoptopenjdk-8.jdk/Contents/Home/jre > > >> Default locale: en_US, platform encoding: UTF-8 > > >> OS name: "mac os x", version: "10.15.6", arch: "x86_64", family: "mac" > > >> > > >> Details of changes since 1.0.0 are in the release notes: > > >> > > >> > https://dist.apache.org/repos/dist/dev/commons/crypto/1.1.0-RC1/RELEASE-NOTES.txt > > >> > > >> > https://dist.apache.org/repos/dist/dev/commons/crypto/1.1.0-RC1/site/changes-report.html > > >> > > >> Site: > > >> > > >> > https://dist.apache.org/repos/dist/dev/commons/crypto/1.1.0-RC1/site/index.html > > >> (note some *relative* links are broken and the 1.1.0 directories > are > > >> not yet created - these will be OK once the site is deployed.) > > >> > > >> *** JApiCmp Report (compared to 1.0.0): > > >> > > >> > https://dist.apache.org/repos/dist/dev/commons/crypto/1.1.0-RC1/site/japicmp.html > > >> > > >> RAT Report: > > >> > > >> > https://dist.apache.org/repos/dist/dev/commons/crypto/1.1.0-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 than 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-crypto.git > > >> --branch commons-crypto-1.1.0-RC1 commons-crypto-1.1.0-RC1 > > >> cd commons-crypto-1.1.0-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- > > >> > > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
