My +1 Gary
On Mon, Mar 23, 2020 at 10:20 AM Gary Gregory <ggreg...@apache.org> wrote: > We have fixed quite a few bugs and added some significant enhancements > since Apache Commons Lang 3.9 was released, so I would like to release > Apache Commons Lang 3.10. > > Apache Commons Lang 3.10 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/lang/3.10-RC1 (svn > revision 38600) > > The Git tag commons-lang-3.10-RC1 commit for this RC is > e0b474c0d015f89a52c4cf8866fa157dd89e7d1c which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=e0b474c0d015f89a52c4cf8866fa157dd89e7d1c > You may checkout this tag using: > git clone https://gitbox.apache.org/repos/asf/commons-lang.git > --branch commons-lang-3.10-RC1 commons-lang-3.10-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1495/org/apache/commons/commons-lang3/3.10/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Mon Mar 23 09:39:32 EDT 2020 > > commons-lang3-3.10-bin.tar.gz=1a17374c98c4d32838254d1a5ca258cc649a30b657a1c7d733d1fe6572f26787f2e901115a78d28c0931b7fa6d1738682644e8201aae0c3c16bbbc9c496393b6 > > commons-lang3-3.10-bin.zip=e12836fe36c8e03d0cfcf2af8fb1fc2d98476dbeda5e7a84594babae8657efb2b3dcc4de7c1a44caec50b191222cf2ad7cf2693345048bfde03b55f98c12d793 > > commons-lang3-3.10-javadoc.jar=3d01c1302bd1d3b624f6de38135f2afb6b69e275665a3ab65d3e49c932012f42f1452bb20fbee5ee740d0f64d9d7484f1cdee43640dcba1277738a49da93f1ef > > commons-lang3-3.10-sources.jar=876017954369013c82804736ca3532434fdd21d28347b157bd355d99a18ea93d566a31fb7678abc1fa49b24a233ad07fee74fd1f8e73ef97b132ebc394605706 > > commons-lang3-3.10-src.tar.gz=8c3e90e60bbb0b83c8e5e8d173d5a982d6f5bf3d2392e11cd17b153484a87c42f3003a7ae84ff3c34a11c16df61d7a4fb8e902b31e0e9c2cef2a17115c0c468b > > commons-lang3-3.10-src.zip=bb15e88b05855c65b0d25309d8c11c5fad73160a89950d60a74f898cbaee4d52a3ce88d59fa83a178e5773f08ec2f90fc0051027858cc86a65a48a339163b7c1 > > commons-lang3-3.10-test-sources.jar=6e23f31279e3e23b439cd2bdafe5d1c98c37fea2accb42ea2a97c13fe9f70b054c46eb2f62abb90485579a831ff362cbb8208daf2adb43fc2be6838f222e30e2 > > commons-lang3-3.10-tests.jar=18e6a11cb24df9f9839b4b74a141611b4e7843b1aced50a4f81c80ff776dd236431805037c6accd2b7c4d089d6320339c4e998d33c02fe8c4fd97b68f2d9f06c > > I have tested this with 'mvn -V -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_241, vendor: Oracle Corporation, runtime: C:\Program > Files\Java\jdk1.8.0_241\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" > > Details of changes since 3.9 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.10-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/lang/3.10-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.10-RC1/site/index.html > (note some *relative* links are broken and the 3.10 directories are > not yet created - these will be OK once the site is deployed.) > > CLIRR Report (compared to 3.9): > > https://dist.apache.org/repos/dist/dev/commons/lang/3.10-RC1/site/clirr-report.html > > JApiCmp Report (compared to 3.9): > > https://dist.apache.org/repos/dist/dev/commons/lang/3.10-RC1/site/japicmp.html > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/lang/3.10-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-lang.git --branch > commons-lang-3.10-RC1 commons-lang-3.10-RC1 > cd commons-lang-3.10-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- > >
