My +1 Gary
On Fri, Sep 13, 2019 at 9:23 PM Gary Gregory <garydgreg...@gmail.com> wrote: > We have fixed a few bugs and added some enhancements since Apache Commons > Configuration 2.5 was released, so I would like to release Apache Commons > Configuration 2.6. > > Apache Commons Configuration 2.6 RC1 is available for review here: > https://dist.apache.org/repos/dist/dev/commons/configuration/2.6-RC1 > (svn revision 35830) > > The Git tag commons-configuration-2.6-RC1 commit for this RC is > 32d6be96f6b101dfd18d21d79788980ee08e5965 which you can browse here: > > https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=32d6be96f6b101dfd18d21d79788980ee08e5965 > You may checkout this tag using: > git clone > https://gitbox.apache.org/repos/asf/commons-configuration.git --branch > commons-configuration-2.6-RC1 commons-configuration-2.6-RC1 > > Maven artifacts are here: > > https://repository.apache.org/content/repositories/orgapachecommons-1469/org/apache/commons/commons-configuration2/2.6/ > > These are the artifacts and their hashes: > > #Release SHA-512s > #Fri Sep 13 21:09:00 EDT 2019 > > commons-configuration2-2.6-bin.tar.gz=f4a6bc8aa066c53a74eefcea75d17e602ced8f8bc57c69ef342091b61b73ea511b38b82d4b5d519d12bb24bf99bd3ca48c9e83d40cf5b8c0d074694efc2d4859 > > \commons-configuration2-2.6-bin.zip=3c1ff55c7a0bed2e577557979650c44b34e93d591a36484000adea06043fb158e4824829a09dd6f3368db6752a85f11e5c2f538670a0a6c73c2a6227450f896e > > commons-configuration2-2.6-javadoc.jar=3efe4fcb28e0cc6d26b97eb911fcd0de6f11e4ef371e69f215aecb1ca7789805ba4b89ea7862b2140538be30ad77d38cfeff6bb1fd4896498b8678f7c1c5ad5d > > commons-configuration2-2.6-sources.jar=f90209da07281a22c0761840bdd90bcebd2992c5e85c565c9df4bb7efb4dbc7962b2543e85f30e2186e2a235fe1c458da793b2e37c39c5c5c43aa580a10b2c66 > > commons-configuration2-2.6-src.tar.gz=dd22a7dcaab4fb0160df50242c0e2c2bd91ec223a2725c12bbb8a873bbc1e365733d64c3521f6e580003161dbe3ea159f83da755a736ff7152bb49f4eda3e167 > > commons-configuration2-2.6-src.zip=2ea6031054fc606b94b6957056d09b61251ca3fc2a32fb6a26bf59a6eda7dba55b2b9c46bac30a4931bc776929bba8bc1e6360e9e1c2e2bf026740dcbd30fdc9 > > commons-configuration2-2.6-test-sources.jar=fe032ba3ffc3fbc1bdb51d6525421e43962617accdbe7a969e6e8e254c634d8f7d079a7eec78216c6f34e9a8c583f096eaaa7b2440f8194fdfa0e89b8eaff069 > > commons-configuration2-2.6-tests.jar=294970a14771866593efcc6164916d31bb1877c484dbc52881da173fa50eb34509f3a4817eeb6bfb911b6dd1d1c711635e5856ee77d921de13453c2d69ca0cf2 > > I have tested this with > > mvn -V -Prelease -Pjacoco -Ptest-deploy clean package site deploy > > using: > > Apache Maven 3.6.2 (40f52333136460af0dc0d7232c0dc0bcf0d9e117; > 2019-08-27T11:06:16-04:00) > Maven home: C:\Java\apache-maven-3.6.2\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 2.5 are in the release notes: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.6-RC1/RELEASE-NOTES.txt > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.6-RC1/site/changes-report.html > > Site: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.6-RC1/site/index.html > (note some *relative* links are broken and the 2.6 directories are not > yet created - these will be OK once the site is deployed.) > > JApiCmp Report (compared to 2.5): > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.6-RC1/site/japicmp.html > > Note that this release adds new _default_ methods to interfaces which are > binary compatible. > > RAT Report: > > https://dist.apache.org/repos/dist/dev/commons/configuration/2.6-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-configuration.git > --branch commons-configuration-2.6-RC1 commons-configuration-2.6-RC1 > cd commons-configuration-2.6-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- >
