Re: [VOTE] Release Apache Commons Codec 1.17.0 based on RC1

2024-04-26 Thread Rob Tompkins
+1

Thanks a ton Gary!

> On Apr 20, 2024, at 2:18 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added enhancements since Apache Commons
> Codec 1.16.1 was released, so I would like to release Apache Commons
> Codec 1.17.0.
> 
> Apache Commons Codec 1.17.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/codec/1.17.0-RC1
> (svn revision 68679)
> 
> The Git tag commons-codec-1.17.0-RC1 commit for this RC is
> 5d809fe3d729bde9b507a51d2b2ed659da053692 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=commit;h=5d809fe3d729bde9b507a51d2b2ed659da053692
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-codec.git
> --branch commons-codec-1.17.0-RC1 commons-codec-1.17.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1723/commons-codec/commons-codec/1.17.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Apr 20 18:11:51 UTC 2024
> commons-codec-1.17.0-bin.tar.gz=24bb52e8260c74b7abb0e47d1634d74e35f7f8174c7ce1daec478411b16615542f9675297d2f374bba1135623e260627c5a0300e7b5c3b77309bb13a2a0fa2a9
> commons-codec-1.17.0-bin.zip=6895c1282bff2cb72d64883759ed706a577afe2ebeae1474bf73473b79b67f62d39ce8025543411468a4bdfdc030dd9392f08a2c9c96d548d373edb3c7071dec
> commons-codec-1.17.0-bom.json=eccbb26e56f9d92ada5bf5b790cb2311eac42016ab9f77cc185f530a094a4739e0c19f26360ebe397de4f9870ab553a35cb71fcc29a2b23532de64b67e32b344
> commons-codec-1.17.0-bom.xml=e74a440e5b9b4e740d8d03561925c48ce72c7596fa1ec44bea827abd245eed2efbadbaa8694d1cbef6a41cad5857070d48fc6b7addfa1857567ab17ab331d97b
> commons-codec-1.17.0-javadoc.jar=c89da8a94284b074e16edb41dc0a895bf2e8c5f201022e393927b634c85743c2be467b953a43e0492db0d76c7aeb9c17be96a8bac1c631536e7481817e6f6f31
> commons-codec-1.17.0-sources.jar=f51dffee159b257db43d3371b4c5bc7e43729948b20f95085b0f7088c1803321fed29eaede5709404a0e17ad6a68f3f9286623af9eb2744e95dda7461f6dc956
> commons-codec-1.17.0-src.tar.gz=afa4425e84cc8f2a29b4b95c5129233696180828fcb51dece8febd55d565cc53a4960f543aa430c027b96ed50768c9584b08f55f43c0a35cd22bb3126e3fbea9
> commons-codec-1.17.0-src.zip=af5fc7d3c8d597729c6c90b4c6a50144a2b14432edd2741e9cbdef794a82f847952bdf7c0603ba20781cc38d0db334c435ae9acbfdefae2aea6b2226cd693e93
> commons-codec-1.17.0-test-sources.jar=a8eefd6c9f5bcd8d539d1c0becd7994b8b706a25dd7cbf7c529a4533c9e51bb9ff4e7357174601e307fa3d110c7875bf096a46e83a13dcaf8324ffb03cfea860
> commons-codec-1.17.0-tests.jar=caa3cbc353bca5de9c3823a5ba19950c4fe6155969bed0bdaf9d654e91c4720f2cb6c507b452148d1bb3ad6f543cb4b3b4c1f738569f619df74fbcc498c58130
> commons-codec_commons-codec-1.17.0.spdx.json=728bad36fe918a0e63a6deb53d3c11d0e1c7fa0b2069ad5a46b24d0ab319819300a93e2694eabf9e19a3875141e49ebb7aea75b874d812bf40a1ec6dcc87ebbf
> 
> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
> jacoco -P japicmp clean package site deploy' using:
> 
> openjdk version "21.0.2" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 21.0.2)
> OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 21.0.2, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.2/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.16.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.17.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.17.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.17.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.17.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.16.1):
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.17.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.17.0-RC1/site/rat-report.html
> 
> KEYS:
>https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons BCEL 6.9.0 based on RC1

2024-04-26 Thread Rob Tompkins
+1 here 

Thanks Gary!!

> On Apr 25, 2024, at 4:48 PM, Gary D. Gregory  wrote:
> 
> Ping :-)
> 
> On 2024/04/22 18:48:21 Bruno Kinoshita wrote:
>> +1
>> 
>> Building OK from tag on
>> 
>> Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
>> Maven home: /opt/apache-maven-3.8.5
>> Java version: 17.0.10, vendor: Private Build, runtime:
>> /usr/lib/jvm/java-17-openjdk-amd64
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "5.15.0-105-generic", arch: "amd64", family:
>> "unix"
>> 
>> 
>> 
>> On Sun, 21 Apr 2024 at 19:20, Gary Gregory  wrote:
>> 
>>> We have fixed a few bugs and one enhancement (Java 16 records) since
>>> Apache Commons BCEL 6.8.2 was released, so I would like to release
>>> Apache Commons BCEL 6.9.0.
>>> 
>>> Apache Commons BCEL 6.9.0 RC1 is available for review here:
>>>https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1 (svn
>>> revision 68692)
>>> 
>>> The Git tag commons-bcel-6.9.0-RC1 commit for this RC is
>>> c240a615d2fcb2497c7d77ad3993e4c66c16e03a which you can browse here:
>>> 
>>> https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=c240a615d2fcb2497c7d77ad3993e4c66c16e03a
>>> You may checkout this tag using:
>>>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
>>> --branch 
>>> commons-bcel-6.9.0-RC1 commons-bcel-6.9.0-RC1
>>> 
>>> Maven artifacts are here:
>>> 
>>> https://repository.apache.org/content/repositories/orgapachecommons-1724/org/apache/bcel/bcel/6.9.0/
>>> 
>>> These are the artifacts and their hashes:
>>> 
>>> #Release SHA-512s
>>> #Sun Apr 21 17:07:12 UTC 2024
>>> 
>>> bcel-6.9.0-bin.tar.gz=e2ac07716a8203405040a18e6dddb84445c0cbc874da382fc67b082c20f3659228ecabf6cba3fbe83b60d36d08c2d9493dfd731960f5aec073f87d9f2e8126f2
>>> 
>>> bcel-6.9.0-bin.zip=93efcf6194077fc216ca81a0f37ca6dc2f5e4032483cfee34c789fe859917be0924221c502ed886fb4582e3681907e73e4f5af11591d1d6a6b2fd779b871bbda
>>> 
>>> bcel-6.9.0-bom.json=4c085990c8b5ece5092f8032b56fd7c87a686443f37b04a2701904b37d7fb1f7147013f82110d67b12d449b78d4743634112f5fa9bfa80de03ec71a06755d934
>>> 
>>> bcel-6.9.0-bom.xml=5759c53a32588f25d672daf90955cee7e2f21a60d98b06a2a8d0fb15ff5308f90885a87eadfbd835cb5b86c856866daac5af04f6723d28495118e984d1d3eff4
>>> 
>>> bcel-6.9.0-javadoc.jar=ac65e56220c0b8fffd67d03a2b003631c34742f33e385249a3b9c511fce50574771afc800ae6d8521ef6195cfc0f448f64b7b7b21a4d80cfe6ba7af86dd1fb19
>>> 
>>> bcel-6.9.0-sources.jar=5e9f448c48604edbfcc2416994649d118e58de596212cd034dc21895277829f8540e43f76f3e45396fa29a060b17b1e1b9086068043131e7f771213449a18349
>>> 
>>> bcel-6.9.0-src.tar.gz=d0a7099257ee30e1ff56896d3d855ba03d2d3efb92a9ac0fba7464ef3052ab26ad7c8ed3a37e551ad5f944a0f04cc811047b20f90c81133ab9aaa008bf517da4
>>> 
>>> bcel-6.9.0-src.zip=37b632c1f921a8aa476571085ce43bdf63db8150a94640775c7bc56d737613cd24e5531a236223ab3ee2e0b15416f3a5722012edd126defdd0f5f8e6ea6c11d0
>>> 
>>> bcel-6.9.0-test-sources.jar=9f9d9a56fb477f767ac9d3e7637a4ef1de032d70594bba3c0999b8a616de73d3ba590f32a154d2699efb0ae2a0932e97229e2dba25758402b6412112086afb95
>>> 
>>> bcel-6.9.0-tests.jar=f645062309b71990440ada1b7cea4b37a24eadcefbe7e0c7a2358905516d713172704c8cfe6f765d89bf8e4a60bfa51096b42efebbe0b5a249f7dc3fecad3e4c
>>> 
>>> org.apache.bcel_bcel-6.9.0.spdx.json=52ee76059ef22938aabbe6fb62d3d71bc3289d38c2b2cac4ddb415b8e7603c90af9cad33baa9d583f6baf96c1206b66c85fb5576e372473cf3ec1939f3792ea9
>>> 
>>> 
>>> 
>>> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
>>> jacoco -P japicmp clean package site deploy' using:
>>> 
>>> openjdk version "17.0.11" 2024-04-16
>>> OpenJDK Runtime Environment Homebrew (build 17.0.11+0)
>>> OpenJDK 64-Bit Server VM Homebrew (build 17.0.11+0, mixed mode, sharing)
>>> 
>>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
>>> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
>>> Java version: 17.0.11, vendor: Homebrew, runtime:
>>> /usr/local/Cellar/openjdk@17/17.0.11/libexec/openjdk.jdk/Contents/Home
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
>>> 
>>> Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
>>> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
>>> 
>>> Details of changes since 6.8.2 are in the release notes:
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1/RELEASE-NOTES.txt
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1/site/changes-report.html
>>> 
>>> Site:
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1/site/index.html
>>>(note some *relative* links are broken and the 6.9.0 directories
>>> are not yet created - these will be OK once the site is deployed.)
>>> 
>>> JApiCmp Report (compared to 6.8.2):
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/bcel/6.9.0-RC1/site/japicmp.html
>>> 
>>> RAT Report:
>>> 
>>> 

Re: [VOTE] Release Apache Commons Imaging 1.0.0-alpha5 based on RC1

2024-04-15 Thread Rob Tompkins
+1

> On Apr 15, 2024, at 1:01 PM, Bruno Kinoshita  wrote:
> 
> +1
> 
> Thank you Gary!
> 
>> On Mon, 15 Apr 2024 at 15:36, Gary Gregory  wrote:
>> 
>> We have fixed a few bugs and added enhancements since Apache Commons
>> Imaging 1.0.0-alpha4 was released, so I would like to release Apache
>> Commons Imaging 1.0.0-alpha5.
>> 
>> Apache Commons Imaging 1.0.0-alpha5 RC1 is available for review here:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1
>> (svn revision 68532)
>> 
>> The Git tag commons-imaging-1.0.0-alpha5-RC1 commit for this RC is
>> 6dc0ba92f62056584af40a24f6c8a8215469ca8f which you can browse here:
>> 
>> https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=6dc0ba92f62056584af40a24f6c8a8215469ca8f
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-imaging.git
>> --branch 
>> commons-imaging-1.0.0-alpha5-RC1
>> commons-imaging-1.0.0-alpha5-RC1
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1720/org/apache/commons/commons-imaging/1.0.0-alpha5/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Mon Apr 15 13:22:38 UTC 2024
>> 
>> commons-imaging-1.0.0-alpha5-bom.xml=b76ae4de3f358c9d3c47925005ba0ea76ad48c0c523e6785d34d9e106dbb2b019b43e974ceb3eff598c03e6ae507b51bf9a5b0cee6fa04664f0dd589540a359e
>> 
>> commons-imaging-1.0.0-alpha5-bin.zip=a94f25a37942b921742765931f89d640320ce5b6d7588ecf9bfb89fa8ea64d4940f88c4062cb5621e64aa9ae18e72bed81e6f517a2695b58d91d972b1f12ed9d
>> 
>> org.apache.commons_commons-imaging-1.0.0-alpha5.spdx.json=43cea02387f469d5b4760a5a34697f81467e7de48567767bbda494f4c25f9543d44fcaac750876aec8834c1781e706e7f7884e36bf8b321ee06bfac0742ee51d
>> 
>> commons-imaging-1.0.0-alpha5-bom.json=79e8a06869238c75a84f817986ba090bbde0124ea885efee11f24eb2f18efc8ab5ffb9699233feb08f3dedfb89580ca702c65bcc9948be5ebcbe3a9796049721
>> 
>> commons-imaging-1.0.0-alpha5-src.zip=78c930ad5edc1f897f049ad357a4b32e5a1c50bd5e9c127296c2209fa22f0705d981828b45c8c4e17efaea34c3c9f68f95fd416dbd6317aeeb3e4908eec0fc50
>> 
>> commons-imaging-1.0.0-alpha5-tests.jar=4a371d7c4fd0f16c084533cedfaafd0eb98d229758ed3455d749bc135564504e788bcf3ceb20a5c8db29aaa837744be3e06ed29d312ffbfbebfa32ff4030c9ce
>> 
>> commons-imaging-1.0.0-alpha5-test-sources.jar=9cc2712d43a5f7d3591940a20dde807730cf0c9e9e74d3105b487f6929f3df5635e4499c9c174550516779cad02b44c7b853c971b9f0a2c206c5357a2d95345d
>> 
>> commons-imaging-1.0.0-alpha5-src.tar.gz=fe6c8b94fecae6a694f22ec10aafe20dd4cac2fcc3811f87ac9ac5d51df11f528fc550f0e7e1e336f900cd8e92a80dedc8c3b00ff31c6e4fb03075d86c19dd3c
>> 
>> commons-imaging-1.0.0-alpha5-javadoc.jar=4bd1c9229e443a8367fbf1402d99cc6fbf2a7f159903ddf34edb46de4d02e91f900cd3c8f9cea6c400da1c62184320c9d71729a5259748d9896cb15f5e76b530
>> 
>> commons-imaging-1.0.0-alpha5-sources.jar=ee27d8161b2b2b93d26b44153b319a790bb0227894cf9ab241182f02f51e2b499911253cbf0f6deef60964559bbb31414e5ee695916ef8275482d11a51b4de1d
>> 
>> commons-imaging-1.0.0-alpha5-bin.tar.gz=ad98e5b49cfc6382c341af86ae2011da0587354dd45a7427a0507310d878b618d790ed6fc6cfdfd610801699015db1d46668a3d1eed79c5977ce00da37c2d602
>> 
>> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
>> jacoco -P japicmp clean package site deploy ' using:
>> 
>> openjdk version "17.0.10" 2024-01-16
>> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
>> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
>> 
>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
>> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
>> Java version: 17.0.10, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
>> 
>> Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
>> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 1.0.0-alpha4 are in the release notes:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/RELEASE-NOTES.txt
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/site/changes-report.html
>> 
>> Site:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/site/index.html
>>(note some *relative* links are broken and the 1.0.0-alpha5
>> directories are not yet created - these will be OK once the site is
>> deployed.)
>> 
>> JApiCmp Report (compared to 1.0.0-alpha4):
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/site/japicmp.html
>>This is an alpha release with one API break.
>> 
>> RAT Report:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha5-RC1/site/rat-report.html
>> 
>> KEYS:
>>https://downloads.apache.org/commons/KEYS
>> 
>> Please review the 

Re: [VOTE] Release Apache Commons CLI 1.7.0 based on RC1

2024-04-15 Thread Rob Tompkins
+1 site, release-notes, signatures, and builds all check out

Thanks!!

-Rob

> On Apr 13, 2024, at 7:29 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added enhancements since Apache Commons
> CLI 1.6.0 was released, so I would like to release Apache Commons CLI
> 1.7.0.
> 
> Apache Commons CLI 1.7.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1 (svn
> revision 68470)
> 
> The Git tag commons-cli-1.7.0-RC1 commit for this RC is
> caed6714a73ce366aebccebf4a21e287d6d34ae0 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=caed6714a73ce366aebccebf4a21e287d6d34ae0
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> --branch commons-cli-1.7.0-RC1 commons-cli-1.7.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1718/commons-cli/commons-cli/1.7.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Apr 13 02:26:30 UTC 2024
> commons-cli-1.7.0-bom.json=fd710316564b50a1af147751c01f25c473c8ccee4af117e3ebd12f7e1eda9524b10389e8ae8705922cc82c0164bc1c5a2977327eb22eac449ce4b149b15d3d90
> commons-cli-1.7.0-test-sources.jar=7b1e4940a6d0b2c84939146122849db1086730d93b8c540047a6fd2b6112eba9c420008302300557c8187821316cddbb7b0599664f04fa21e325e04bd4bb06f0
> commons-cli-1.7.0-src.zip=e0f684163327c6180098c61d89705ff49041239b04dcd0235dd0b7b3b9ac590c23da85236ae4458135b1d804824d639db2f4a85ee9cfa281c2cc49ec2f5775f1
> commons-cli-1.7.0-javadoc.jar=fea0659ba7c7f23940547f2aa6ae15d85817a7ecf9d537083b7c5873012e85b39aa9dbf1054f69f49a86b30b3ea06e037dc5b972c1bc553caa2c6004be409613
> commons-cli_commons-cli-1.7.0.spdx.json=1527955bcb67fdbefac08bd6905290f01c3397e6921eb5980e4b96145cf68a4a6745f28b29435fb4e181f051cd1c9d43017d53db5df6a12e76244bd642c5213a
> commons-cli-1.7.0-bin.zip=07a2a6698ba1010c5952ec26ad2e4ce73a87476f0fd97dd34cb5280f0563c0a0bdeb65e3cc9afbe9bca50c149f2570fa716f0a617c9f277b1ffdd9baa75081d0
> commons-cli-1.7.0-tests.jar=08338e5488c6d12e28a65b2d5ea2da172a087832c0c58915f47e1078038b10873bf5594237dc2275a6079027487745d5a76722424c5482c5f786ba95f5c34acb
> commons-cli-1.7.0-src.tar.gz=d97be4df213e0df72a3866b8271e34064e984e98debb2ae8bdd1bef94ea1fd358655dbc730866cb62b4232bad7888d69b4d964a101139f2cf36cd0fcfb39d28b
> commons-cli-1.7.0-sources.jar=9bc86da3391d3fc87806384fda1272b8e0a0313eb529ae4e9eaf7d5fc63708a90449f6fe72b4d29da730c21c4fc497f395c01812b625803479884e08f0593090
> commons-cli-1.7.0-bom.xml=40623202b108d74635fee720a826e730ed63b838596db45a887f4718be949db9ca01f9661be3c03067b2d1d9246d7fde1524c83c7718db1cb2202e0d3ed748d2
> commons-cli-1.7.0-bin.tar.gz=c429f22021bbb80f11e9b27bc768ec28b797d9d6fc18b3af369bfc7278641f2585c62cd6d6736b7f1813e3f9690390f8fd304743f123ae9fff496edd1942cac6
> 
> 
> I have tested this with 'mvn' and '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:
> 
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.10, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
> 
> Darwin * 23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.6.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.7.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.6.0):
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.7.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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
> ==
> 
> 

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

2024-04-15 Thread Rob Tompkins
+1 - all site, signatures, reports, and builds check out.

Thank you!

> On Apr 13, 2024, at 1:20 PM, Bruno Kinoshita  wrote:
> 
> +1
> 
> Building OK from tag on
> 
> Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
> Maven home: /opt/apache-maven-3.8.5
> Java version: 17.0.10, vendor: Private Build, runtime:
> /usr/lib/jvm/java-17-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "5.15.0-102-generic", arch: "amd64", family:
> "unix"
> 
> Thanks
> 
> On Sat, 13 Apr 2024 at 15:44, Gary Gregory  > wrote:
> 
>> We have fixed a few bugs and added enhancements since Apache Commons
>> Text 1.11.0 was released, so I would like to release Apache Commons
>> Text 1.12.0.
>> 
>> Apache Commons Text 1.12.0 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1
>> (svn revision 68475)
>> 
>> The Git tag commons-text-1.12.0-RC1 commit for this RC is
>> 2c2d0818b0540c59f055f5174db51d0574af46da which you can browse here:
>> 
>> https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=2c2d0818b0540c59f055f5174db51d0574af46da
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-text.git
>> --branch 
>> commons-text-1.12.0-RC1 commons-text-1.12.0-RC1
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1719/org/apache/commons/commons-text/1.12.0/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sat Apr 13 13:34:53 UTC 2024
>> 
>> commons-text-1.12.0-bom.xml=43b65ff31fc8fbc65cb87b3dd4ccfc819ca3f22986d7b494184d6039dcef27f87879d86bc2b0b8aa11b1076fa08b940e211cbf0c717039cbb166d47ebc052244
>> 
>> commons-text-1.12.0-bom.json=5f3d52977598686724506ff0daf329cea26d1bb9d069b62f1f24e2ed483360fbd56ba3a7687590695a7a23dbffd90b03f9b59d73779eb6c057ce7aba40bda464
>> 
>> org.apache.commons_commons-text-1.12.0.spdx.json=32401c4d64fc0edc6aba525462309b86aa758ffe2201b89732f2c75845403c835b398fd783b3b670cd5c22875bdefe13dade05d3394d0642a45912de82e9ae59
>> 
>> commons-text-1.12.0-src.tar.gz=6f995d6b120109466c1af4aba7ba7678b1c7461628d78d0ae3139720c099411bc106a7d492727bb54b7714fb0c443a4844913b3d6f0f18befa9e3bc6e8171af0
>> 
>> commons-text-1.12.0-src.zip=f98f9fde5221914c133d6c1cb685d50ba6652991090cde27e3c3310eec4ed24229d0741107f671821bef216f4a5b2efa0488555a57e0d3c226d53c6497e2e502
>> 
>> commons-text-1.12.0-javadoc.jar=6e4d9493cef82660663b6af99f6c32f7fefdca2cb98c1ec8bbd4a01fb123b3348fdab7c32593b5cf3ddd69107ebf58124dc19b6679182d8568a43454e2a7602a
>> 
>> commons-text-1.12.0-bin.tar.gz=c2f5cedf0a2f31fc0657241c9efb3113e221d8a4d53654448745f0ba853b4fa31ffa061810c53114ba16adee34d8c8dcc0e465e827dfeae03e9f91a2618f5bac
>> 
>> commons-text-1.12.0-tests.jar=33381e48a5239a43458beb597cbd9c65c3d8ce8687a974dd1d21fe9d7bdb7acb6fc534ba3d9bd18c00cd5bf3e44b33b99a8c0bf2a7dc85613f789767bdf57605
>> 
>> commons-text-1.12.0-test-sources.jar=d9c9d7fc9473536ea6c92df58f3d33d489f26b0f44b6363d8fcc7a366e1a8ecda3ec366eac26ea61f5722c3438f602385ff9b777c30e895a6bfaeeb83524ace5
>> 
>> commons-text-1.12.0-sources.jar=eed680391a6181d44b5c6e6b0e99b7c36ed5d4d34e496f4299b7d77e9f0c0851966a6ccf4037a2ebc729c3dbdff67dd644a0534df651766f47ea8d16a7e18dc7
>> 
>> commons-text-1.12.0-bin.zip=fe50ac094fed72a8de3f92a275ee6d8be2a1ae6e94dc0b53df69444064574e7319b9fa6a265437ba6faf260f11a1f8c220ee3ed37ccde791f1488aea8f29a9d9
>> 
>> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
>> jacoco -P japicmp clean package site deploy' using:
>> 
>> openjdk version "17.0.10" 2024-01-16
>> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
>> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
>> 
>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
>> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
>> Java version: 17.0.10, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
>> 
>> Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
>> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 1.11.0 are in the release notes:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/RELEASE-NOTES.txt
>> 
>> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/site/changes-report.html
>> 
>> Site:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/site/index.html
>>(note some *relative* links are broken and the 1.12.0 directories
>> are not yet created - these will be OK once the site is deployed.)
>> 
>> JApiCmp Report (compared to 1.11.0):
>> 
>> https://dist.apache.org/repos/dist/dev/commons/text/1.12.0-RC1/site/japicmp.html
>> 
>> RAT Report:
>> 
>> 

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

2024-04-05 Thread Rob Tompkins
Ah…pardon. Here’s my local info:

 % mvn -version
Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
Maven home: /opt/homebrew/Cellar/maven/3.9.4/libexec
Java version: 17.0.9, vendor: Amazon.com Inc., runtime: 
/Library/Java/JavaVirtualMachines/amazon-corretto-17.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "14.3", arch: "aarch64", family: "mac"

> On Apr 5, 2024, at 11:28 AM, Gary D. Gregory  wrote:
> 
> Rob, 
> 
> What OS and such (mvn -version)?
> 
> Gary
> 
> On 2024/04/05 14:51:39 Rob Tompkins wrote:
>> -0.5: building with java17 from the src zip I get the following for the 
>> jcs-core module
>> 
>> [INFO] Results:
>> [INFO] 
>> [ERROR] Failures: 
>> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:116 
>> message not received
>> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:138 
>> message not received
>> [ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast:157 
>> message not received
>> [INFO] 
>> [ERROR] Tests run: 426, Failures: 3, Errors: 0, Skipped: 0
>> 
>> 
>> -Rob
>> 
>>> On Apr 4, 2024, at 10:49 AM, Thomas Vandahl  wrote:
>>> 
>>> Hi folks,
>>> 
>>> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I 
>>> would like to release Apache Commons JCS 3.2.1.
>>> 
>>> Apache Commons JCS 3.2.1 rc1 is available for review here:
>>>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1 (svn 
>>> revision 68312)
>>> 
>>> The Git tag commons-jcs3-3.2.1-rc1 commit for this RC is 
>>> 0b20664b6c60b025cfe0e95c33e86f3239822a12 which you can browse here:
>>>   
>>> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=0b20664b6c60b025cfe0e95c33e86f3239822a12
>>> You may checkout this tag using:
>>>   git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
>>> commons-jcs3-3.2.1-rc1 commons-jcs3-3.2.1-rc1
>>> 
>>> Maven artifacts are here:
>>>   
>>> https://repository.apache.org/content/repositories/orgapachecommons-1712/org/apache/commons/commons-jcs3/3.2.1/
>>> 
>>> These are the artifacts and their hashes:
>>> 
>>> 5ea0cfd1ea5d17689ce35fd4a26ad104028b2b0d3209cf8c3d58d1a8e62c77442de95d51af278ad810a28117d0297725ded41b18553e05212dfc9e9db1dd185c
>>>   commons-jcs3-dist-3.2.1-bin.tar.gz
>>> ce7151767ebcf5ce08c9e91689ef1b240344b874963edc3042c0a6958e02deb95551aa9de1a8f63fd6e87198f179ad90501a0b76f96cf6c2c10cd546e867c8bf
>>>   commons-jcs3-dist-3.2.1-bin.zip
>>> 8abc08f18edf6fcd86d9fcb8834ef4584d6932a6a7dca8936b199b6aec3622e634c20f639fdb5cd1077d2492e1a8fd3dafb0ceb9a259127c3dfc3ec54d6cea1b
>>>   commons-jcs3-dist-3.2.1-src.tar.gz
>>> e7a2796bc07b9da4d8e5db0423baa758e0e139e8cdc35aa6d50e32cdfa9163b874eeedfd52e90c599049faa1963546109389fb967e60df8a0198a025a3d75869
>>>   commons-jcs3-dist-3.2.1-src.zip
>>> 
>>> I have tested this with ***'mvn clean install site'*** using:
>>> 
>>> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
>>> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
>>> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
>>> Default locale: de_DE, platform encoding: UTF-8
>>> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
>>> 
>>> Details of changes since 3.2 are in the release notes:
>>>   
>>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/RELEASE-NOTES.txt
>>>   
>>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/changes-report.html
>>> 
>>> Site:
>>>   
>>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/index.html
>>>   (note some *relative* links are broken and the 3.2.1 directories are not 
>>> yet created - these will be OK once the site is deployed.)
>>> 
>>> JApiCmp Report (compared to 3.2):
>>>   
>>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/japicmp.html
>>> RAT Report:
>>>   
>>> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/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.
>>> 

Re: [VOTE] Release Apache Commons IO 2.16.1 based on RC2

2024-04-05 Thread Rob Tompkins
+1 build, signatures, site all checkout fine.

-Rob

> On Apr 4, 2024, at 9:36 PM, Gary Gregory  wrote:
> 
> [ The difference with RC1 is https://github.com/apache/commons-io/pull/609 ]
> 
> We have fixed a few bugs since Apache Commons IO 2.16.0 was released,
> so I would like to release Apache Commons IO 2.16.1.
> 
> Apache Commons IO 2.16.1 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC2 (svn
> revision 68321)
> 
> The Git tag commons-io-2.16.1-RC2 commit for this RC is
> 290d72eda9152d1e11b79d48453908ff3f6b9897 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=290d72eda9152d1e11b79d48453908ff3f6b9897
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-io.git
> --branch commons-io-2.16.1-RC2 commons-io-2.16.1-RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1714/commons-io/commons-io/2.16.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Fri Apr 05 01:25:31 UTC 2024
> commons-io-2.16.1-javadoc.jar=8ea8e38bdf89d93adfdfdb5746cab218ec4939e271ae5b814a47a672e8339c6cfbf924397821e098ae9bf9733718153e03b2953a5d749f0b99b74f7a2a3490fc
> commons-io_commons-io-2.16.1.spdx.json=d97014ef9bd54283478c80df289076b7ba79170c0bc769904fd1ce251a7a16974e0fcf0a73b8e73bd5d3af10f8aef873e11b06a9e3a980cdd34c41796fab50f3
> commons-io-2.16.1-bom.xml=b5b0701af1a828e52d4ae4e685f301efb592dcea21e6e2be5c65db21390c5a87cddb761b1b6043e412fe3c8120d9efa501f6156ab923bde5c54314ce507df979
> commons-io-2.16.1-bin.zip=25c0a1fd11bb28cd80b1ea23f6c7ae4bd5bc779edd298bace619133be5a72706ef716ea75b8a7e96685ae7b32c780e61275454c79c48c965b7816a8b53cd43bd
> commons-io-2.16.1-test-sources.jar=5de8eae4411002a6c97c327f8af79c1b4cf872986a0ef45e7ee107c23fd114fcdc08b23a7fbb82df628aa456eedf06f00c5dd8afb8510e2173fa57b5bb9bb4ea
> commons-io-2.16.1-tests.jar=7ba5684fd4e37f9ef7097536303bec45423aa466f211252c4f71e1c837646e57ccf7fd1de46b28a31a444b9f80699c7530c7d16f0654e7ae43f892316e284733
> commons-io-2.16.1-sources.jar=4d54c30603e6c5d09b485bc77de11672822114f2938946c574f5aa398abe3834d57e31b20c95a6593d5ee17c3346bdb3c2780b1ce47a5c5f663f77e79b8c5791
> commons-io-2.16.1-src.zip=6396cf423054aca88cd796e436680a943474953c94dedc01d5343dd1a9a02912d4a1c0fd03419c63b709b4e1e09fb0e2660f212edfb0d4589bdaf4eef5fa7b8b
> commons-io-2.16.1-src.tar.gz=07298e3af85726f2ec07a660fbb743f82cd88f8043a57e2e1063b758c81429dfafd77a024e2cdd48efe5d403299c20e898f5b3dd729f52bd55b8a6fb50c9a13a
> commons-io-2.16.1-bom.json=21dabe2118730a8635b3d97f2d4fba5f8a1d1c0ee2161804fe4ee4ba626195df1c66cb340e6cc97caf2d9d7abe7e60e9e6b4d669977635cc81fddc5797273ece
> commons-io-2.16.1-bin.tar.gz=4b132b8ad88483e58b1dcbf21f31d0d1095e05b5ee7bf4e586d0652d61e00818cdbf6c940535ae0aa00e5090af6b7c3a43edc22f57e313ef0b8f1fbe6f3fe1ad
> 
> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
> jacoco -P japicmp clean package site deploy' using:
> 
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.10, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
> 
> Details of changes since 2.16.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC2/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC2/site/index.html
>(note some *relative* links are broken and the 2.16.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.16.0):
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC2/site/japicmp.html
>There are no API changes.
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.1-RC2/site/rat-report.html
> 
> KEYS:
>https://downloads.apache.org/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.
> 

Re: [VOTE] Release Apache Commons JCS 3.2.1 based on rc1

2024-04-05 Thread Rob Tompkins
-0.5: building with java17 from the src zip I get the following for the 
jcs-core module

[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   UDPDiscoverySenderEncryptedUnitTest.testPassiveBroadcast:116 message 
not received
[ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRemoveBroadcast:138 message 
not received
[ERROR]   UDPDiscoverySenderEncryptedUnitTest.testRequestBroadcast:157 message 
not received
[INFO] 
[ERROR] Tests run: 426, Failures: 3, Errors: 0, Skipped: 0


-Rob

> On Apr 4, 2024, at 10:49 AM, Thomas Vandahl  wrote:
> 
> Hi folks,
> 
> We have fixed a few bugs since Apache Commons JCS 3.2 was released, so I 
> would like to release Apache Commons JCS 3.2.1.
> 
> Apache Commons JCS 3.2.1 rc1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1 (svn revision 
> 68312)
> 
> The Git tag commons-jcs3-3.2.1-rc1 commit for this RC is 
> 0b20664b6c60b025cfe0e95c33e86f3239822a12 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=0b20664b6c60b025cfe0e95c33e86f3239822a12
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2.1-rc1 commons-jcs3-3.2.1-rc1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1712/org/apache/commons/commons-jcs3/3.2.1/
> 
> These are the artifacts and their hashes:
> 
> 5ea0cfd1ea5d17689ce35fd4a26ad104028b2b0d3209cf8c3d58d1a8e62c77442de95d51af278ad810a28117d0297725ded41b18553e05212dfc9e9db1dd185c
>   commons-jcs3-dist-3.2.1-bin.tar.gz
> ce7151767ebcf5ce08c9e91689ef1b240344b874963edc3042c0a6958e02deb95551aa9de1a8f63fd6e87198f179ad90501a0b76f96cf6c2c10cd546e867c8bf
>   commons-jcs3-dist-3.2.1-bin.zip
> 8abc08f18edf6fcd86d9fcb8834ef4584d6932a6a7dca8936b199b6aec3622e634c20f639fdb5cd1077d2492e1a8fd3dafb0ceb9a259127c3dfc3ec54d6cea1b
>   commons-jcs3-dist-3.2.1-src.tar.gz
> e7a2796bc07b9da4d8e5db0423baa758e0e139e8cdc35aa6d50e32cdfa9163b874eeedfd52e90c599049faa1963546109389fb967e60df8a0198a025a3d75869
>   commons-jcs3-dist-3.2.1-src.zip
> 
> I have tested this with ***'mvn clean install site'*** using:
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> 
> Details of changes since 3.2 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/index.html
>(note some *relative* links are broken and the 3.2.1 directories are not 
> yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.2):
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/japicmp.html
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2.1-rc1/site/commons-jcs3-core/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,
> 
> Bye, Thomas 
> Release Manager (using key 88817402)
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons Collections 4.5.0-M1 based on RC1

2024-04-01 Thread Rob Tompkins
+1 all looks good.

> On Mar 31, 2024, at 12:19 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added enhancements since Apache Commons
> Collections 4.4 was released, so I would like to release Apache
> Commons Collections 4.5.0-M1.
> 
> Apache Commons Collections 4.5.0-M1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1
> (svn revision 68212)
> 
> The Git tag commons-collections-4.5.0-M1-RC1 commit for this RC is
> 2f8305d6a268d51e4b41e183f6d8b61c3c1ef99b which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-collections.git;a=commit;h=2f8305d6a268d51e4b41e183f6d8b61c3c1ef99b
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-collections.git
> --branch commons-collections-4.5.0-M1-RC1
> commons-collections-4.5.0-M1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1711/org/apache/commons/commons-collections4/4.5.0-M1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Mar 31 16:04:35 UTC 2024
> commons-collections4-4.5.0-M1-javadoc.jar=c5bc0c8d481c4120e2e16d9f7c762dd6bdca8e215f9782a6d4da0444133839c9f25ef97d1b981b16fefa306969aba7bfefad42f261990897e06250e7a0c893c0
> commons-collections4-4.5.0-M1-test-sources.jar=63e6c0888b1c8ed992968a329ff61e1309292dbac1743de68180d66a4b945baa7c7b5c415a14f179fe8ad27a782374f6a78e36e7d1fb34ec5133fe0a86d836aa
> org.apache.commons_commons-collections4-4.5.0-M1.spdx.json=5bbb207506f97064a04da82b9f6be20610818f07f77e00a18c33aea65cc1e6228860088bdfefd6ee52411563ab1f96ae9baea688806c2c6ba2d15278ba1d2706
> commons-collections4-4.5.0-M1-src.zip=51cf6b96a2110d5c0f73bda94d377fb96391bb5b3f2636fb253fc1beaca23a50f6988008d4e824b3a709aecd9df316df0fb8c71925f0d7a970014a33fce7fcde
> commons-collections4-4.5.0-M1-bom.xml=fc7d0a283aaa4e7559705cdf4b69479379a9deda422123222af87f121f70600bc1939c055e6add0ef900abb7c2172af7ecfa53f2bd0f5808db9d4befd9fc4486
> commons-collections4-4.5.0-M1-bom.json=965229073d7f9fd63212ad65fcc943d76ed9569a2e1cbbe7ebd97ff442461914be83a96ac957095d478dbfdb9c805b30325fd3f5e3118d50ce50c91d06ec7e3b
> commons-collections4-4.5.0-M1-bin.zip=a016e7cde33c7ffcf03b9f899582babff802d98f22d9a292ce204dc0867b050c83cc8815f2cfc66d7ba721c7792cf81963405bdbe9f4cde1eaf376be3db6fd4c
> commons-collections4-4.5.0-M1-tests.jar=02f4d82750827b4c322a03ea52de1d4ae9c28168480ee49c20e790bb8fe9cf6df41f00cb4d44d90486e9eb17c7df1ed38e000aafea247109b92970f48db64611
> commons-collections4-4.5.0-M1-bin.tar.gz=fe8ddd1a9ca34e43753a41718e56e408ff7f9a1ca1c9e2fb0a457ebb07e4debed2ed95a214e78e07e03609048b92076dedfda1065f69cba7ef82d1b615554e8e
> commons-collections4-4.5.0-M1-sources.jar=f041903fcf3702f15f0a042d96880c1f84aed249d05a6c791cb0b099d711bda43b0d3ca7d1fbac14b1ab3780f6032eafe5045c559b68308a692634d9475535f3
> commons-collections4-4.5.0-M1-src.tar.gz=0aefd67c7f027ebfa90ec975f9088d17326d2599c56d3d2f926597f69247290bdda5fc601f740997315514b8e3bfae9511afda61680e90d0b466df17220854a9
> 
> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
> jacoco -P japicmp clean package site deploy' using:
> 
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.10, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
> 
> Details of changes since 4.4 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/site/index.html
>(note some *relative* links are broken and the 4.5.0-M1
> directories are not yet created - these will be OK once the site is
> deployed.)
> 
> JApiCmp Report (compared to 4.4):
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/collections/4.5.0-M1-RC1/site/rat-report.html
> 
> KEYS:
>https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons Imaging 1.0.0-alpha4 based on RC1

2024-04-01 Thread Rob Tompkins
+1


> On Mar 30, 2024, at 6:01 PM, Tomas Lanik  wrote:
> 
> +1  for 1.0.0-alpha4
> 
> On Sat, Mar 30, 2024 at 3:14 PM Gary Gregory  wrote:
> 
>> We have fixed a few bugs and added enhancements since Apache Commons
>> Imaging 1.0-alpha3 was released, so I would like to release Apache
>> Commons Imaging 1.0.0-alpha4.
>> 
>> Apache Commons Imaging 1.0.0-alpha4 RC1 is available for review here:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha4-RC1
>> (svn revision 68205)
>> 
>> The Git tag commons-imaging-1.0.0-alpha4-RC1 commit for this RC is
>> 728c798cf747ec7de559a80cc54e39e88cc3a4e0 which you can browse here:
>> 
>> https://gitbox.apache.org/repos/asf?p=commons-imaging.git;a=commit;h=728c798cf747ec7de559a80cc54e39e88cc3a4e0
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-imaging.git
>> --branch 
>> commons-imaging-1.0.0-alpha4-RC1
>> commons-imaging-1.0.0-alpha4-RC1
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1710/org/apache/commons/commons-imaging/1.0.0-alpha4/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sat Mar 30 13:51:49 UTC 2024
>> 
>> commons-imaging-1.0.0-alpha4-tests.jar=97dea4f77e55d93397eda51f9b0716a59996355e6f03135c076e6c3c927d4f6ad42e09bf43046c235b3cf01de896357a8dc3c640354e34fd70c4ab09d8bc6dca
>> 
>> commons-imaging-1.0.0-alpha4-bom.xml=c54a0c2f58c931ec77df713b1649cefb43f2d297ef23b778d97c56ef0c4e73c79b62431bf8c80cb0c6b67c9cdc603e421c4fb46ade3b928f05b236cb23cf
>> 
>> commons-imaging-1.0.0-alpha4-bin.zip=72306aa7cd554826dd11203f7d84a3d39bbbd64bfb31785f7c8464d8b5e3f9aba45cf8bc7143c639707355df73c42d907c8588a83f33545273ba550c62a629b1
>> 
>> commons-imaging-1.0.0-alpha4-test-sources.jar=40f44d7987756b90713314a647c582a6ced6122e149cc60d69972d783860519ed6f46f787c98795cfab26ac255be4cf3c75679457b680bb0dcfed476b6addb19
>> 
>> commons-imaging-1.0.0-alpha4-src.tar.gz=908b7cd56d7bcc9832e60fbf3bba289286c6878941cd246d92abc1017d924dec8aded9abb1300fb0242549616506d9a9ccf0d159b5e86b5936ace6f4d2c365e3
>> 
>> commons-imaging-1.0.0-alpha4-sources.jar=7e02544b312d3ba496a7c9e874a785dc75a5869584101ec7d86072a9da13adb8ff357729534c4ba70a1d5348cdfd50a72ac4e702ddc842add9eb30064b7b030d
>> 
>> commons-imaging-1.0.0-alpha4-bom.json=62de378483ec6e6a67c3eb6dc57230028d3fbdb36f38dd9cb403e23df3c9f123beb4f38ba2666a301ca29729e51ecc1b4201c0eba1c98f4edf3f610d42f20b87
>> 
>> org.apache.commons_commons-imaging-1.0.0-alpha4.spdx.json=a180644d6b9424685c2ad612bb60def14117e58cabc602fd3c3d4d588ac484609781a87c83a307dce51d3639f6ac8cee2842d93bc49f381e9fe563cbfc268ce7
>> 
>> commons-imaging-1.0.0-alpha4-javadoc.jar=6144bf7d7456316b25664fdbedcd0241b6e68ab24738c92db239c9aa196e4ba439eb4b7be9f5325cff37a9ab2ac8bf44ac17f4cb6665bb7f505744e13a456641
>> 
>> commons-imaging-1.0.0-alpha4-bin.tar.gz=9500955b498cd3d35a9116d0c46e89d6ea721f697b7270fdab24b06e84b2e387c33f8a46114f7cc85754ac58cca86911b579533d1a9eab2c6715410f535ff8e9
>> 
>> commons-imaging-1.0.0-alpha4-src.zip=4552b5defa39049a8acfb8db0644c60e0ece9b92225203bd9f1a735a67080decae0fcf725dd6f4959ef6fcdc4a33c7c2c63487866626995b4c61fe0f288795dd
>> 
>> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
>> jacoco clean package site deploy' using:
>> 
>> openjdk version "17.0.10" 2024-01-16
>> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
>> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
>> 
>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
>> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
>> Java version: 17.0.10, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
>> 
>> Darwin  23.4.0 Darwin Kernel Version 23.4.0: Fri Mar 15 00:11:05
>> PDT 2024; root:xnu-10063.101.17~1/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 1.0-alpha3 are in the release notes:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha4-RC1/RELEASE-NOTES.txt
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha4-RC1/site/changes-report.html
>> 
>> Site:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha4-RC1/site/index.html
>>(note some *relative* links are broken and the 1.0.0-alpha4
>> directories are not yet created - these will be OK once the site is
>> deployed.)
>> 
>> RAT Report:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/imaging/1.0.0-alpha4-RC1/site/rat-report.html
>> 
>> KEYS:
>>  https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons IO 2.16.0 based on RC1

2024-03-27 Thread Rob Tompkins
+1

> On Mar 25, 2024, at 9:51 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons IO 2.15.1 was released, so I would like to release Apache
> Commons IO 2.16.0.
> 
> Apache Commons IO 2.16.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1 (svn
> revision 68124)
> 
> The Git tag commons-io-2.16.0-RC1 commit for this RC is
> c0d44bcc782372980c9e6881537c801e6d84219f which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=c0d44bcc782372980c9e6881537c801e6d84219f
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-io.git
> --branch commons-io-2.16.0-RC1 commons-io-2.16.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1708/commons-io/commons-io/2.16.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Mon Mar 25 13:40:18 UTC 2024
> commons-io-2.16.0-src.tar.gz=a97c6467f1ea48be8118c85f71360e775991b971b860b7371c3e184418bf14a3ac39a87379e427bab4aa8bd0283c1367882f06ae2f2fae423a0ed48b23335a70
> commons-io-2.16.0-javadoc.jar=87d02e2bcc0d07b7bbf9d84fbade92b3964343c1d73fd931a78731a94edc18f3b2f0b5b726b8914d8d40c713f291b1d7b960079a34b240c183549c296120b48e
> commons-io-2.16.0-test-sources.jar=429106f6a17b81617107691307f3601fe160fd625b277e9983d27b5085e416b9570b6f41919d9d2a915ea0e1f788e43d46f88d9a0ff4468df12aa3b8dbbabc16
> commons-io-2.16.0-bom.json=d29cad554cabb2cc68576bbff94956c0d096b70caca91e74729c749e615bbf40d49e398bb552676708f29a5b710e8d5a4797d72b9b3e1b5790bddba60bccb455
> commons-io-2.16.0-bin.tar.gz=cae78a84809046989be88d8e2205597f14362c6deba5bd87744ed36d097b2395fdb3602ee2bd9017ea382e8772393565ac780eed15ca4c2b9c0e45b1fdb362cc
> commons-io-2.16.0-src.zip=a1e12a4b54ebe1c56359a962174a0d5457f91fcaef15827d84b03618ac876540e5f08551a5d11fe67e5d5c19c6ea5d987687ed5c74d372df08d95eb98e088dfa
> commons-io-2.16.0-bom.xml=75f6682f694432a76c3435c08a6f01c1dc6bec79026f1751c69af5957129ae876f82dfbf5464bfbaa084f9c0cdc5af671900230e76df6a4106d3e5d1ad5260c1
> commons-io_commons-io-2.16.0.spdx.json=a76f8f587a6ee1d869ed789fd73ae13e3984462507a56807302eb8f4dc6ae406ae15b47e3f6c2f01de3252c6108a92c293a8d32f54be18aa77838314bbe878f6
> commons-io-2.16.0-bin.zip=c40c47572f6716814a992c00291032a80a5ec6ac2910850f260450fea883288a7a582e583344a165235457eda4ef116c6e417e9eaeabfd7870e121a477416c62
> commons-io-2.16.0-tests.jar=721cde073c07d2ae145309f9cebd568e1910d5a3809efeb7fc2cb04e789c4012fa45e36074e43d93b7795cf607acb8f3dfcf998aad996657e49c58618607f463
> commons-io-2.16.0-sources.jar=6826bc3886a56e330fec6225d7e5550de640298e1bdd33739276819294e320334ffb81c9e04bea8c0b5138f2e135b6fee197b27f4347d59119c8728783b1841c
> 
> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
> jacoco -P japicmp clean package site deploy' using:
> 
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.10, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 2.15.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/site/index.html
>(note some *relative* links are broken and the 2.16.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.15.1):
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.16.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and 

Re: [VOTE] Release Apache Commons Logging 1.3.1 based on RC2

2024-03-21 Thread Rob Tompkins
+1 site good, signatures good, builds on java 8, 11, 17, 21

-Rob

> On Mar 17, 2024, at 11:44 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Logging 1.3.0 was released, so I would like to release Apache
> Commons Logging 1.3.1.
> 
> (Note that the new release candidate is labeled 1.3.1 and no longer 1.4.0.)
> 
> Apache Commons Logging 1.3.1 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2
> (svn revision 67979)
> 
> The Git tag commons-logging-1.3.1-RC2 commit for this RC is
> 558bb9cdd5fb06e313214d34ed5be7de5f000a5a which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=558bb9cdd5fb06e313214d34ed5be7de5f000a5a
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-logging.git
> --branch commons-logging-1.3.1-RC2 commons-logging-1.3.1-RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1704/commons-logging/commons-logging/1.3.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Mar 17 15:39:38 UTC 2024
> commons-logging-1.3.1-sources.jar=2b80051bc2a6478ac2ba7c0dc3de0ec7b14976b1d2ed62fde050fb40920d9904ce2e1fa168155780f900592152f9d433555c4fdfbb669455abbc132030b7404a
> commons-logging-1.3.1-src.tar.gz=ffda970d086601df4b476caf8bd01d1bdc22dd7f8846a22287036f7f000ce6cf0a757d16621910f041f8d90aa6066819454b3977dd005ca66817bec59e91e91f
> commons-logging-1.3.1-javadoc.jar=da92f1a875c84174ea81e5b61be6d96aebed0460a129484f15552e7ecc14a8f5a886433278524bcca53f07373bf08ffd3c0e66d755ba084e1babddb0d815db99
> commons-logging-1.3.1-test-sources.jar=30ad1e42723bf10bb170f04415af56aad8803f385b278c62b295bd4512874080b63daa71c08f119b5cd25d064eebe018a6cd64fa5a4ecc0cb129225977795f60
> commons-logging-1.3.1-src.zip=ccd55350243b12d9a43385a32fb86ed3e3f8c84b68f3b009598c9f77d2659d34532e100d371810a6bdb31d495223200ea59f1e4ae4b0e9d7ee24b9410de037d6
> commons-logging-1.3.1-adapters.jar=b67193bbad0a161dd79c23cf683553cb7dcfe19f234324c9457991605198002fe4b4e772c7f7463b9d2017a635fd3d22632d4d22408f9fa79586a36a817b
> commons-logging-1.3.1-api.jar=14aaf1d4b5430f590a2f98575143b2b531bcd0527f4cd2c754242a46ab2df80426e731059c9fceea2d78321f849ddb20296250f875100b5899c9321dc0130020
> commons-logging-1.3.1-bom.json=55d7b79e697cf84f9e5e3255dd2e725a1b4c205e4e64043795f91067bc577ba8aaba314972f59def246846c04285fe3c03cf55f2d4612674c36ac015d9fbf061
> commons-logging_commons-logging-1.3.1.spdx.json=4ef75823dab414487f44e2abbf849248e9e123b8b1c7504fe963cc3e668789fa10ed64e0eea360a8342fd614779936853c4bba826832457a0ee234b728ae3079
> commons-logging-1.3.1-bin.tar.gz=d1897232f7734957baf19f1fcc60da64ae36be06985ad63260e6d752a03cbfc23aec7d3865e908436d66fa1ba121dd81ba5e0b79dad4143dfa41c1857d3f6d20
> commons-logging-1.3.1-bom.xml=68db0d81784aac3d5a727c09163d115e52adac317c4657ecf8bd9cfd98321da92593c8615e38f9e79e4af782f71344c03cf7c51008b15af4fdea404692fef446
> commons-logging-1.3.1-bin.zip=751d971db549541b5f41ae16fc9cdebfec319494d3f0ce58757dbeb6f067036e1eabe4962c326e23fcabf2b66d5602ee9fde302865287ef2a48154c1ccb6d6ec
> commons-logging-1.3.1-tests.jar=43da256ca13506bbe3e330847b14c873e627cfa4495c554a5d4f9ca62032816fe06e304f48089c79078d58e9f376e54cbe5e762d9be0a7c60da5f8898bf1d496
> 
> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
> jacoco -P japicmp clean package site deploy' using:
> 
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.10, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.3.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/index.html
>(note some *relative* links are broken and the 1.3.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> *** CLIRR Report (compared to 1.3.0):
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/clirr-report.html
> 
> *** JApiCmp Report (compared to 1.3.0):
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/japicmp.html
> 
>***
>Note that the above report notes several errors.
>These are 

Re: [VOTE] Release Apache Commons Logging 1.3.1 based on RC2

2024-03-20 Thread Rob Tompkins
+1 looks good

> On Mar 17, 2024, at 11:44 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Logging 1.3.0 was released, so I would like to release Apache
> Commons Logging 1.3.1.
> 
> (Note that the new release candidate is labeled 1.3.1 and no longer 1.4.0.)
> 
> Apache Commons Logging 1.3.1 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2
> (svn revision 67979)
> 
> The Git tag commons-logging-1.3.1-RC2 commit for this RC is
> 558bb9cdd5fb06e313214d34ed5be7de5f000a5a which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=558bb9cdd5fb06e313214d34ed5be7de5f000a5a
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-logging.git
> --branch commons-logging-1.3.1-RC2 commons-logging-1.3.1-RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1704/commons-logging/commons-logging/1.3.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Mar 17 15:39:38 UTC 2024
> commons-logging-1.3.1-sources.jar=2b80051bc2a6478ac2ba7c0dc3de0ec7b14976b1d2ed62fde050fb40920d9904ce2e1fa168155780f900592152f9d433555c4fdfbb669455abbc132030b7404a
> commons-logging-1.3.1-src.tar.gz=ffda970d086601df4b476caf8bd01d1bdc22dd7f8846a22287036f7f000ce6cf0a757d16621910f041f8d90aa6066819454b3977dd005ca66817bec59e91e91f
> commons-logging-1.3.1-javadoc.jar=da92f1a875c84174ea81e5b61be6d96aebed0460a129484f15552e7ecc14a8f5a886433278524bcca53f07373bf08ffd3c0e66d755ba084e1babddb0d815db99
> commons-logging-1.3.1-test-sources.jar=30ad1e42723bf10bb170f04415af56aad8803f385b278c62b295bd4512874080b63daa71c08f119b5cd25d064eebe018a6cd64fa5a4ecc0cb129225977795f60
> commons-logging-1.3.1-src.zip=ccd55350243b12d9a43385a32fb86ed3e3f8c84b68f3b009598c9f77d2659d34532e100d371810a6bdb31d495223200ea59f1e4ae4b0e9d7ee24b9410de037d6
> commons-logging-1.3.1-adapters.jar=b67193bbad0a161dd79c23cf683553cb7dcfe19f234324c9457991605198002fe4b4e772c7f7463b9d2017a635fd3d22632d4d22408f9fa79586a36a817b
> commons-logging-1.3.1-api.jar=14aaf1d4b5430f590a2f98575143b2b531bcd0527f4cd2c754242a46ab2df80426e731059c9fceea2d78321f849ddb20296250f875100b5899c9321dc0130020
> commons-logging-1.3.1-bom.json=55d7b79e697cf84f9e5e3255dd2e725a1b4c205e4e64043795f91067bc577ba8aaba314972f59def246846c04285fe3c03cf55f2d4612674c36ac015d9fbf061
> commons-logging_commons-logging-1.3.1.spdx.json=4ef75823dab414487f44e2abbf849248e9e123b8b1c7504fe963cc3e668789fa10ed64e0eea360a8342fd614779936853c4bba826832457a0ee234b728ae3079
> commons-logging-1.3.1-bin.tar.gz=d1897232f7734957baf19f1fcc60da64ae36be06985ad63260e6d752a03cbfc23aec7d3865e908436d66fa1ba121dd81ba5e0b79dad4143dfa41c1857d3f6d20
> commons-logging-1.3.1-bom.xml=68db0d81784aac3d5a727c09163d115e52adac317c4657ecf8bd9cfd98321da92593c8615e38f9e79e4af782f71344c03cf7c51008b15af4fdea404692fef446
> commons-logging-1.3.1-bin.zip=751d971db549541b5f41ae16fc9cdebfec319494d3f0ce58757dbeb6f067036e1eabe4962c326e23fcabf2b66d5602ee9fde302865287ef2a48154c1ccb6d6ec
> commons-logging-1.3.1-tests.jar=43da256ca13506bbe3e330847b14c873e627cfa4495c554a5d4f9ca62032816fe06e304f48089c79078d58e9f376e54cbe5e762d9be0a7c60da5f8898bf1d496
> 
> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
> jacoco -P japicmp clean package site deploy' using:
> 
> openjdk version "17.0.10" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.10, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.3.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/index.html
>(note some *relative* links are broken and the 1.3.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> *** CLIRR Report (compared to 1.3.0):
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/clirr-report.html
> 
> *** JApiCmp Report (compared to 1.3.0):
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.1-RC2/site/japicmp.html
> 
>***
>Note that the above report notes several errors.
>These are considered OK for the reasons stated below.
>These 

Re: [VOTE] Release Apache Commons VFS Project 2.10.0 based on RC1

2024-03-20 Thread Rob Tompkins
+1

> On Mar 10, 2024, at 6:02 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons VFS Project 2.9.0 was released, so I would like to release
> Apache Commons VFS Project 2.10.0.
> 
> Apache Commons VFS Project 2.10.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1 (svn
> revision 67866)
> 
> The Git tag commons-vfs-2.10.0-RC1 commit for this RC is
> 6aec37ad5fdcd4d0f2ca0330f310eb48a1585462 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-vfs.git;a=commit;h=6aec37ad5fdcd4d0f2ca0330f310eb48a1585462
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-vfs.git
> --branch commons-vfs-2.10.0-RC1 commons-vfs-2.10.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1702/org/apache/commons/commons-vfs2-project/2.10.0/
> 
> These are the artifacts and their hashes:
> 
> ${commons.sha512list}
> 
> 
> I have tested this with:
> 
> mvn
> 
> and
> 
> mvn -V -Prelease -Ptest-deploy clean install -DskipTests && \
>  mvn -V -Prelease -Ptest-deploy -P japicmp -P jacoco site deploy
> -DskipTests && \
>  mvn -V -Prelease -Ptest-deploy site:stage
> 
> Details of changes since 2.9.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/index.html
>(note some *relative* links are broken and the 2.10.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.9.0):
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/commons-vfs2/japicmp.html
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/commons-vfs2-ant/japicmp.html
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/commons-vfs2-hdfs/japicmp.html
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/commons-vfs2-jackrabbit1/japicmp.html
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/commons-vfs2-jackrabbit2/japicmp.html
> 
>Note that per the Java Language Specification, "Changes to the
> throws clause of methods or constructors do not break compatibility
> with pre-existing binaries; these clauses are checked only at compile
> time."; see 
> https://docs.oracle.com/javase/specs/jls/se21/html/jls-13.html#jls-13.4.21
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-vfs.git --branch
> commons-vfs-2.10.0-RC1 commons-vfs-2.10.0-RC1
> cd commons-vfs-2.10.0-RC1
> 
> 1b) Download and unpack the source archive from:
> 
> https://dist.apache.org/repos/dist/dev/commons/vfs/2.10.0-RC1/source
> 
> 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
> 
> Note that 

Re: [VOTE] Release Apache Commons Configuration 2.10.1 based on RC1

2024-03-19 Thread Rob Tompkins
+1

> On Mar 18, 2024, at 9:35 AM, Gary Gregory  wrote:
> 
> My +1
> 
> Gary
> 
>> On Sun, Mar 17, 2024 at 4:36 PM Gary Gregory  wrote:
>> 
>> We have fixed a few bugs since Apache Commons Configuration 2.10.0 was
>> released, so I would like to release Apache Commons Configuration
>> 2.10.1.
>> 
>> Apache Commons Configuration 2.10.1 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1
>> (svn revision 67980)
>> 
>> The Git tag commons-configuration-2.10.1-RC1 commit for this RC is
>> 81573fa387435e985cc05356c33c49273fc4a018 which you can browse here:
>>
>> https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=81573fa387435e985cc05356c33c49273fc4a018
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-configuration.git
>> --branch commons-configuration-2.10.1-RC1
>> commons-configuration-2.10.1-RC1
>> 
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1705/org/apache/commons/commons-configuration2/2.10.1/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sun Mar 17 20:27:50 UTC 2024
>> commons-configuration2-2.10.1-bom.json=ed21bbdf1666c55d2204fcb4134cbe34402516033f7b0a502f85c26002b1b603a926c5956fe87a477ef3b781247d253727d130dc616f11d732f2127c4ab14da1
>> commons-configuration2-2.10.1-javadoc.jar=fb986f680f30684b51550c28de4c50ae7b13a5dcb57204c3a73086fa5ea5e904a3e5a96da0950b54f4ea5387c9b95742c13b76baab899fdc27e3f2ea29afddaa
>> commons-configuration2-2.10.1-src.zip=21192c0ee5ffa1af49afbd2556745f4c7183d47ee9abc40deca40800e0790594d17285756dded0b79702117d286d2bb09953c429b1c78037d33f199dcd04ce81
>> commons-configuration2-2.10.1-test-sources.jar=3610ad010fe2702b9c8481d568f0f448cdc8fa8a1b03695ab5991c6348e619766f096da2603062933cd74066034fcbb4310fc03241f15256e7cf69e1a3723161
>> commons-configuration2-2.10.1-src.tar.gz=cccaa29b59467e1bc08a2c62d84a057f342418003e10b5a0c259c67be2059db38c035224bfe520e48e789e55b656f105079f42486590e29624c35a436fcee257
>> commons-configuration2-2.10.1-bin.tar.gz=fc0d92d528c8e48615103c9f3022c36302a161f2b647d8df3cca1b0b9135d1de7bb5c92ea891bdee4a67ed4d98a6b5ed75ba53eba108dc84e518f369763d8950
>> commons-configuration2-2.10.1-sources.jar=aa63579bdaea11e84c5656af588026db4357006ca03dd4ef7405dcd0910f2b55998554e801c45e462587999adc49033c2cc50abc83d2a613cf396125ab28e4ea
>> commons-configuration2-2.10.1-tests.jar=43a9a052f7fc36bbebb25c5850dc31252961388dac630b6608a9394f5c1c23f21c4aee9d04abec614d0a239004f7b47028bd2a229b9d2c5585c7b550706cfaae
>> commons-configuration2-2.10.1-bom.xml=8449699ebf34b5e1e74ca006bfb5a06386e285b9c8fee0e1701300d10561749c21000e71affdfa4a29966ec3f4153f038956cf012a091ac5bd3a7bd78dc21c54
>> commons-configuration2-2.10.1-bin.zip=e1658a0c901b488b65f9373f439045a208547cf75e3cac43a45ab227589166d2a4c5993f76ec56956d0fc9d0d10231d4b909f5042a0d036259b92727e3da4760
>> org.apache.commons_commons-configuration2-2.10.1.spdx.json=351ca7d39367b6ce3a7afb39575c990aab7db2d753588ab83109fc29479d0e84fde2e017c61cfa176f43cf7d573116f1f07523f072ff9dab4df6968969aa1293
>> 
>> I have tested this with 'mvn' and 'mvn -V -Prelease -P jacoco -P
>> japicmp clean package site deploy' using:
>> 
>> openjdk version "17.0.10" 2024-01-16
>> OpenJDK Runtime Environment Homebrew (build 17.0.10+0)
>> OpenJDK 64-Bit Server VM Homebrew (build 17.0.10+0, mixed mode, sharing)
>> 
>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
>> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
>> Java version: 17.0.10, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@17/17.0.10/libexec/openjdk.jdk/Contents/Home
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
>> 
>> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
>> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 2.10.0 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/RELEASE-NOTES.txt
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/site/changes-report.html
>> 
>> Site:
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/site/index.html
>>(note some *relative* links are broken and the 2.10.1 directories
>> are not yet created - these will be OK once the site is deployed.)
>> 
>> JApiCmp Report (compared to 2.10.0):
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/site/japicmp.html
>> 
>> RAT Report:
>>
>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.1-RC1/site/rat-report.html
>> 
>> KEYS:
>>https://downloads.apache.org/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...
>>  

Re: [VOTE] Release Apache Commons Configuration 2.10.0 based on RC1

2024-03-12 Thread Rob Tompkins
+1

> On Mar 11, 2024, at 8:36 AM, Gary Gregory  wrote:
> 
> ping?
> TY!
> Gary
> 
>> On Sat, Mar 9, 2024 at 9:22 AM Gary Gregory  wrote:
>> 
>> My +1
>> 
>> Gary
>> 
>>> On Wed, Mar 6, 2024 at 9:13 AM Gary Gregory  wrote:
>>> 
>>> We have fixed a few bugs and added some enhancements since Apache
>>> Commons Configuration 2.9.0 was released, so I would like to release
>>> Apache Commons Configuration 2.10.0.
>>> 
>>> Apache Commons Configuration 2.10.0 RC1 is available for review here:
>>>https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.0-RC1
>>> (svn revision 67757)
>>> 
>>> The Git tag commons-configuration-2.10.0-RC1 commit for this RC is
>>> 67637998d398d79bf0cc6b830d72fadd8b53a355 which you can browse here:
>>>
>>> https://gitbox.apache.org/repos/asf?p=commons-configuration.git;a=commit;h=67637998d398d79bf0cc6b830d72fadd8b53a355
>>> You may checkout this tag using:
>>>git clone https://gitbox.apache.org/repos/asf/commons-configuration.git
>>> --branch commons-configuration-2.10.0-RC1
>>> commons-configuration-2.10.0-RC1
>>> 
>>> Maven artifacts are here:
>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1701/org/apache/commons/commons-configuration2/2.10.0/
>>> 
>>> These are the artifacts and their hashes:
>>> 
>>> #Release SHA-512s
>>> #Wed Mar 06 14:01:58 UTC 2024
>>> commons-configuration2-2.10.0-bin.tar.gz=4239219274c9e59f897870bf5cbf35210885b2812d74c15c79b1150cb1d0617ebcbc5417c99019addd75a14da67807fb78ca55efe2c8b48b6251584bde051d15
>>> commons-configuration2-2.10.0-bin.zip=36ea60c2dc927ef06c02c6694278dcd799cb5c9a6902314061347c2ac787bf8dbb7c0fa59f6e39c298352e401b1e5dd82c5214a08354639cbf80044220750df5
>>> commons-configuration2-2.10.0-bom.json=02fc0b438d1189035f7049bc010961e5309cab6cead5c37fabf2294556fa5e0a9fd223fe3f4a1564fc83e261500905d0795105906ce3fa71df0613f9b746b37c
>>> commons-configuration2-2.10.0-bom.xml=6bbda2ba6c2f0d7af8fd7fee93c71fb3f29a1fb220598cda8d3bbf2dfe19396364a63a6109b5418390da7b41f5e9a2eeaaae1f2fd4ce707d44bee38b19b23409
>>> commons-configuration2-2.10.0-javadoc.jar=0494fb1bfeabaa246ad7507dc8464c78e76a0223767817123bdf8843aaf56030af512da9feac499fbfee79eaeb4d4cbe6749a28a679a531b0bc6301b711ddf3a
>>> commons-configuration2-2.10.0-sources.jar=bacf3d4538810e095fccdb51479b5739082c97a8fc2572b887b542cc6551583da64cd2104387d9872e990e02af0419e7986b532bb007ae710d118549a046df89
>>> commons-configuration2-2.10.0-src.tar.gz=fa0959160b85a686886275624b9a7b8cb38480bc502cc930669d97c521cccddc4b2371a01bab85ecb2f88dfe6d1c22558b6525eeabc5b8cf9070163d24ff031b
>>> commons-configuration2-2.10.0-src.zip=e61c68feaddbfddf0985ba904ac5f73c4420b7fb7fdd173a83efd320673df7c3b652120ef6e513572a0c7c8bf5935d934187411b2ab124c5d03ba9072ab02ca3
>>> commons-configuration2-2.10.0-test-sources.jar=bff3d3e30e1352c759e148641989b65129c235da70ec85b428c3876981b6bace7a00fd65f8b896ee649ba984869635a03ebe28f03226e62d9771db1373686ae9
>>> commons-configuration2-2.10.0-tests.jar=1fe44c1f1c49e0846836141286d874ac641523bfac4403defc1af2ff8910660189a21c56a255f9e3fc2e4737e644259b23aa22a4bdaffd3296436c6cf1aea44e
>>> org.apache.commons_commons-configuration2-2.10.0.spdx.json=d6329228f13ca56b811ae6f2fae9fb9dd841d4efd6f0c52847728d8fbea44dac67ce1dbad9e766e4a237e06cd99d220cb76c64e3ef4898aa0047a4556411c37b
>>> 
>>> I have tested this with:
>>> 
>>> mvn
>>> 
>>> and
>>> 
>>> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site 
>>> deploy
>>> 
>>> Using:
>>> 
>>> openjdk version "21.0.2" 2024-01-16
>>> OpenJDK Runtime Environment Homebrew (build 21.0.2)
>>> OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
>>> 
>>> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
>>> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
>>> Java version: 21.0.2, vendor: Homebrew, runtime:
>>> /usr/local/Cellar/openjdk/21.0.2/libexec/openjdk.jdk/Contents/Home
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
>>> 
>>> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
>>> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
>>> 
>>> Details of changes since 2.9.0 are in the release notes:
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.0-RC1/RELEASE-NOTES.txt
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.0-RC1/site/changes-report.html
>>> 
>>> Site:
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.0-RC1/site/index.html
>>>(note some *relative* links are broken and the 2.10.0 directories
>>> are not yet created - these will be OK once the site is deployed.)
>>> 
>>> JApiCmp Report (compared to 2.9.0):
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.0-RC1/site/japicmp.html
>>> 
>>> RAT Report:
>>>
>>> https://dist.apache.org/repos/dist/dev/commons/configuration/2.10.0-RC1/site/rat-report.html
>>> 
>>> KEYS:
>>>

Re: [VOTE] Release Apache Commons Compress 1.26.1 based on RC1

2024-03-06 Thread Rob Tompkins
+1 tested builds on java 8 -21, site - reports all look good, RELEASE-NOTES.txt 
good, signatures good.

> On Mar 5, 2024, at 5:40 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Compress 1.26.0 was released, so I would like to release
> Apache Commons Compress 1.26.1.
> 
> Apache Commons Compress 1.26.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/compress/1.26.1-RC1
> (svn revision 67751)
> 
> The Git tag commons-compress-1.26.1-RC1 commit for this RC is
> 81ac94151eedc61c2131239362a051e30c5e9e59 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-compress.git;a=commit;h=81ac94151eedc61c2131239362a051e30c5e9e59
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-compress.git
> --branch commons-compress-1.26.1-RC1 commons-compress-1.26.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1700/org/apache/commons/commons-compress/1.26.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Tue Mar 05 22:24:25 UTC 2024
> Apache\ Commons\
> Compress-1.26.1.spdx.rdf.xml=7dd9d7ad576dea9611f87acd8b047f4b0f9701730a7cdcc62a3800b04f3ef7aa889e80c7df2a1636aa44f8fd58462c5bf3b19dc2c0004490009faef1ac2301b9
> commons-compress-1.26.1-bin.tar.gz=56325ec491bc5e6d8c37742d5f44869a9668f8359d5243cf8628dfb06f223bc3c1133239185295df4a98f8503f32f7609cecdbe24cc0f15fdd34a577bab0d7b9
> commons-compress-1.26.1-bin.zip=217838bad31682bb29b4f5eafad2ec5bf767a0c417fec2f16e84e2a6af7ed8fb44a34ad81c382a88155f0688988c58b85280411cf00a0f7022ccd89e83fbd3b5
> commons-compress-1.26.1-bom.json=9ddb2350681af3e6378e7fa5c35ae2916b07dc429adb25b96a07a72b095fa0db81e59904aaab4b6c48856ab9c77c64dadd414d652b1b0aa8e22494354f3937b7
> commons-compress-1.26.1-bom.xml=0fcaa44fd3393be32cfdf37e8678554a4fb9bfae90a6ab20975ef48493df6a7cab7fc79ac1c821e538daa18ecfe4d29c0f9aa27ccff63dbcfe3d588dd26e5d91
> commons-compress-1.26.1-javadoc.jar=5de00b4eedc3e9f9343c165b11d23e3a0d42c3681890707888af5c3257e15c1d3af35c1bb924c4b86fa8ce5398116b4eb61aeb32fec3181a339857fd305c934d
> commons-compress-1.26.1-sources.jar=65cbf8d1db3c150f76c5c4afec5f874253a18d89df7afff24ad93097507ddb52edaf47829863f4a0f561d547879c52c75a7bd590476e6911b6614000a0eaa58d
> commons-compress-1.26.1-src.tar.gz=096c94344a9bbcd021a3cce0869456cf6d22ca5136b63de017922d7c3de5d94b591961fe550201b654f9dc90b2cd8f32ef9bf1e507fddfb2e2f7c33bddc790c4
> commons-compress-1.26.1-src.zip=69387bd46fe25b5b046819d41804f3b9c867b598a2d408e1131f34ba33ccf3589cce07ef3f360da5c60a5b455e7084aca3a0722ab75de67279babf5fa7c65280
> commons-compress-1.26.1-test-sources.jar=08d2729412759a5e2c3a07619e807b67ac57dc29bdd69d24114dfc467e1ca2589837150db18195510d19accb1604b8c77987e85bb1787dfec3be441b0980c54c
> commons-compress-1.26.1-tests.jar=d2af16e04a0d5f8c1de0d23c1c4b035ebf20598bb6c9c1f7ea5858605804a35bb7b70b0e8f42bf735303d916f9fe1d2292b36838ca8912e2d70f89ec88261da4
> 
> I have tested this with:
> 
> mvn
> 
> and
> 
> mvn -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> openjdk version "21.0.2" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 21.0.2)
> OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 21.0.2, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.2/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.26.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.1-RC1/site/index.html
>(note some *relative* links are broken and the 1.26.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.26.0):
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.1-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons DBCP 2.12.0 based on RC1

2024-03-02 Thread Rob Tompkins
+1 ran tests, site looks good, signatures look good.

> On Feb 29, 2024, at 5:46 PM, Gary Gregory  wrote:
> 
> Hi All,
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons DBCP 2.11.0 was released, so I would like to release Apache
> Commons DBCP 2.12.0.
> 
> Apache Commons DBCP 2.12.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/dbcp/2.12.0-RC1
> (svn revision 67637)
> 
> The Git tag commons-dbcp-2.12.0-RC1 commit for this RC is
> 49270ef2445b775ed0a6673757d15185d859e6ac which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-dbcp.git;a=commit;h=49270ef2445b775ed0a6673757d15185d859e6ac
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-dbcp.git
> --branch commons-dbcp-2.12.0-RC1 commons-dbcp-2.12.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1693/org/apache/commons/commons-dbcp2/2.12.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Thu Feb 29 22:33:36 UTC 2024
> Apache\ Commons\
> DBCP-2.12.0.spdx.rdf.xml=2a949b0ab04a69ed12d826e29fdd22aa4d92fdccd6188974263364323a9a6ac99a099f851299f6237af5b272e042a28e41de71dbb11934b0d10b27a82cd2d31f
> commons-dbcp2-2.12.0-bin.tar.gz=2202dbb7145e67ed4c99a4ac9a6716a4886110e4d219ac869c4d81bfe75981cf0535664e2d939b3db5ae3515338101dcc29e10aa7e69576155c42789b6ca966b
> commons-dbcp2-2.12.0-bin.zip=d2141744d0a7ad48e456aa0a6254efb706b491f30c6fc0056e2029de9b21f97ac6265508f1513631347e9f72d2da2269815745a0967dc6f3a8d621cb0fb818ce
> commons-dbcp2-2.12.0-bom.json=f128916347a2a72e8dd7705f54049041814e40765f75536c10ef18fa43ca1d7e5a77a74a74aa10f446927be35189f3d092edf6abc9436c616eddce293bfa590a
> commons-dbcp2-2.12.0-bom.xml=3b4e2a3066085d3ea0ecb1e1c8106ed0b817a7939e85df7fd4d6d2cd386206f1d2a774e77998f25e1c39c577d784c02078d470f2b7998f8af175a22de3f7bc89
> commons-dbcp2-2.12.0-javadoc.jar=dac615d144c5e72efb7a46862e4d82ca8726705600731be5e5573ab76061013cdcd9cd301d15e610e5403f223c955040fabdebaa24fe20a17f74cfde02f9
> commons-dbcp2-2.12.0-sources.jar=a35d60fcc5835be64f93049823c17c65bd34ceb6fb4c444de122be5e2ea9039dd1df755ff7dd80c2a82a120a8e4dea1beb2d4f178efd8762e00b42e491c17bdb
> commons-dbcp2-2.12.0-src.tar.gz=2e115574abd2e8582202dcd35c90b093d5a39c24a1bb7abc6930ec6f10c9eee1c90f00061adcf9e3249a175e4de4eb71374dbf94c81e39bf395dbb360749b01a
> commons-dbcp2-2.12.0-src.zip=c2597d665fbc2bfc1adac2a7120295d3a1d72a6fd36d5c02de07cc6735bfb375abb920eba8b78b0d2d562e31207acb1d330cfc558c0769d6d0a0580c85cc796a
> commons-dbcp2-2.12.0-test-sources.jar=2262f12da577c7458ef7e12c57ecea399be2837b6a0a675355859e78c337aa961e9a0f99225ad0d15e64ca25b321fb6aaea1aa4ec8e65350c9ace7eeb15eee22
> commons-dbcp2-2.12.0-tests.jar=c1fbe0ef2655f32ec8c04ce853d5418176d16bf84f7af94193d8e37c465ef9e26c150e35c9ef0e35fdabfb366f9a49596212c01280f3524198323eaeb00980fe
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> openjdk version "21.0.2" 2024-01-16
> OpenJDK Runtime Environment Homebrew (build 21.0.2)
> OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 21.0.2, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.2/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 2.11.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.12.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.12.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.12.0-RC1/site/index.html
>(note some *relative* links are broken and the 2.12.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.11.0):
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.12.0-RC1/site/japicmp.html
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.12.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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: 

Re: [VOTE] Release Apache Commons BCEL 6.8.2 based on RC1

2024-02-24 Thread Rob Tompkins
+1

> On Feb 21, 2024, at 7:18 PM, Gary D. Gregory  wrote:
> 
> We have fixed a few bugs since Apache Commons BCEL 6.8.1 was released, so I 
> would like to release Apache Commons BCEL 6.8.2.
> 
> Apache Commons BCEL 6.8.2 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.2-RC1 (svn 
> revision 67482)
> 
> The Git tag commons-bcel-6.8.2-RC1 commit for this RC is 
> 749d99c14180afb991dca2d02c1ad75fd97f417f which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=749d99c14180afb991dca2d02c1ad75fd97f417f
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git --branch 
> commons-bcel-6.8.2-RC1 commons-bcel-6.8.2-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1691/org/apache/bcel/bcel/6.8.2/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Wed Feb 21 17:43:58 EST 2024
> bcel-6.8.2-tests.jar=9e4643c904b2187791b1b419e6fd0cc8b75471487c505993f7ebb48f366b21889dac14af01b4a21bd798b16b2f5754bb70e9484a1b2bb096f7a56f83c73706c1
> bcel-6.8.2-src.zip=9d362d26cb1c52514636c993e3d13f3424ff1aaf5dd897c1ef8d9f7745b069e7ff29d0924261ab1b071d0f11c73baa1052fd780a55d5995e50b3acc49d42f252
> bcel-6.8.2-javadoc.jar=98ea3681c849e8a2515c111db9360d50d1ed7c0fe0f8257f3536baadbfb2de131c3110ecb1823ea073185cfbc01360d523d5fdfe580511f1efe3456a7e63fcd7
> bcel-6.8.2-bin.tar.gz=f8ea95821f983be06988f8008c4e402dd48b702547b1d58251b91d544735f8f7370cdda78353c84d7b5932323c1113205fa1e3e9b6235d6dcf2f8e10f3671742
> bcel-6.8.2-src.tar.gz=17e18323651274bd54c8fc631b27e9460bb7389b3736aac6645da52a6a1ca1d4d5a48b9c987065356bdcd62ddf20f7ec4e563424e3ad504e46495237e254cef6
> org.apache.bcel_bcel-6.8.2.spdx.json=a2bc9d6da822bc5ec607bf98b26b42f04e663bfd707eb863166052a21f517c0309f25658aded35638219846204385dd37a84eb4fb4f4e21ac6bfed1ddbb484c8
> bcel-6.8.2-bom.json=65980e4ae082b66c51dd1d774e6d2337a2c6c661c826c4180c1ca948e11feb25b1e9f1707520a555acdb04cd68caede65bf3fc7d8e9628948b862656e0d89d50
> bcel-6.8.2-bom.xml=8d712f1220bcde65ade4362de1f3a6bb7e66cf8423c83951070bc151ba07c50013dab86fd855b4598dc957458f1c498ac2715758202261f857ce26429563e205
> bcel-6.8.2-sources.jar=df2ce9772ff98f53b5d00c7ed650a16deb45b573262e2692f91cf34071ad791f126b54706b4ab94385e2fa5deaac81910205668750b304249e119ca7efe7
> bcel-6.8.2-test-sources.jar=441a271c831da3c73d6dfa6b7fa041ed6c8253528d8ab43ed1fbb9ba88945519ce12dc9b84a38e8b04f869dc37c5f7f5098d5ce0586497eea6b366d67166e054
> bcel-6.8.2-bin.zip=69a04f10a5e69cea2d6cd54488f0dbe73ed1b46b214cb4e06a9acc7901845a3cd0e89f12d1034b2670ab442eae9957775c61d8fb7a0d7fb77574223deb89468f
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: C:\java\apache-maven-3.9.6
> Java version: 17.0.8, vendor: Eclipse Adoptium, runtime: C:\Program 
> Files\Eclipse Adoptium\jdk-17.0.8.7-hotspot
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
> 
> Microsoft Windows [Version 10.0.19045.3930]
> 
> Details of changes since 6.8.1 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.2-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.2-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.2-RC1/site/index.html
>(note some *relative* links are broken and the 6.8.2 directories are not 
> yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 6.8.1):
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.2-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.2-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-bcel.git --branch 
> commons-bcel-6.8.2-RC1 commons-bcel-6.8.2-RC1
> cd commons-bcel-6.8.2-RC1
> 
> 1b) Download and unpack the source archive from:
> 
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.2-RC1/source
> 
> 2) Check Apache licenses
> 
> This step is not 

Re: [VOTE] Release Apache Commons Compress 1.26.0 based on RC1

2024-02-18 Thread Rob Tompkins
+1 - all looks good

> On Feb 17, 2024, at 7:14 PM, Gary Gregory  wrote:
> 
> [VOTE] Release Apache Commons Compress 1.26.0 based on RC1
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Compress 1.25.0 was released, so I would like to release
> Apache Commons Compress 1.26.0.
> 
> Apache Commons Compress 1.26.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/compress/1.26.0-RC1
> (svn revision 67401)
> 
> The Git tag commons-compress-1.26.0-RC1 commit for this RC is
> acaf5642b1e16d872870a4dc4618e46ccd349493 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-compress.git;a=commit;h=acaf5642b1e16d872870a4dc4618e46ccd349493
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-compress.git
> --branch commons-compress-1.26.0-RC1 commons-compress-1.26.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1689/org/apache/commons/commons-compress/1.26.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Feb 17 23:50:41 UTC 2024
> commons-compress-1.26.0-bom.xml=30154dabf68fe1d9dfcfb02a9e4d80a4aadd182817c310900178ebae8df06fce23a30b269f63c37fc3a69c59fd57e0d9a9cdc86cddb38ca4d53617f6f6c0da7e
> commons-compress-1.26.0-javadoc.jar=b08f5b9433e8f7a67b40920a35188cf47a7cc1dfb52e4e9ad196cd445cf2a0737fd8c7d292f6dfb5e4e37f88b44bd902e0180918201eefa8acce27788a295864
> commons-compress-1.26.0-src.tar.gz=9348e2792d67fe977cbfcede80ab95de96e582c3f7239e16e99360decac4e7703f57d4cfec9535cd4a0f884319df851eb5e44214ba8c3dd321cc6ea67f9d1abb
> commons-compress-1.26.0-bin.zip=ced62b0302521ccabee920dba677a3a4b5cec671e89e36b35e7f3045a9d252a0cf1fbc336cec5bf956dfcbf41db6393e849c6cb4caa09d8984c9e1d3a53a0981
> commons-compress-1.26.0-src.zip=5e2ac6fa35328074625896cb1c8d8a92a248a73f1c0a3f753403042b22c2e9dd9a923d164f5708529d81c2d469414124b163c23ad3a430547a5053cce37292fa
> commons-compress-1.26.0-test-sources.jar=2bebd5e5a8747709d89ac2ff8db07611bed2bdb7304703a9563d4e422c4bfd15ecf636c8324c8d8e17e9e5dedcb91e146b3501fd35eb07450de654f7b5880c2e
> commons-compress-1.26.0-sources.jar=579484734f9ade3ddafe263e9b9926159bf3620af8d7cc02ff07588859a27ad38816e26135be038b5ee11c77df2a680d16801d5b8de439fe23924c32122772d4
> commons-compress-1.26.0-bom.json=133c986aaeccc1a6eec23a8b225bd0766f11ea7a7321a3df7eedc6d2a7c37c5f0ecd20d32c7b2e1b57dc0960830c20eb92392d32f2e8cd585ea682a88ad281b4
> Apache\ Commons\
> Compress-1.26.0.spdx.rdf.xml=b8fced57be4030feaea4e2f7a4602c6c3ecd24272d4590fb932e12f8a08889ff31a247fb346ea9fba7c331fcda11966407a9bdd8eaa4f3d07ea2ebee34f08db2
> commons-compress-1.26.0-bin.tar.gz=4854f83b210ad79b3d410c7b232fa82da7ad22a94b5d5e8ecd06abc004b2c96be178a2f43a620fe5e80e76f51ca605063ebf64f47ecf5ca6306ddef704a91c19
> commons-compress-1.26.0-tests.jar=dcafafc5e1345640ec9bd9f7f72cb14643ddd30996814a0d25e58bead667120543cee51452e9d4f21488cf1dcab4cffec3089eea38c78f69c6daa1575279bc3e
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> openjdk version "17.0.9" 2023-10-17
> OpenJDK Runtime Environment Homebrew (build 17.0.9+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.9+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.9, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.9/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.3.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.25.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.26.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.25.0):
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.26.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 

Re: [VOTE] Release Apache Commons Codec 1.16.1 based on RC1

2024-02-06 Thread Rob Tompkins
+1 all looks good.

Keep up the good work Gary!!!

Cheers,
-Rob

> On Feb 4, 2024, at 10:40 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Codec 1.16.0 was released, so I would like to release Apache
> Commons Codec 1.16.1.
> 
> Apache Commons Codec 1.16.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1
> (svn revision 67174)
> 
> The Git tag commons-codec-1.16.1-RC1 commit for this RC is
> e59fc76531141cb4a36f3031457b9d5f07e5e43f which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=commit;h=e59fc76531141cb4a36f3031457b9d5f07e5e43f
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-codec.git
> --branch commons-codec-1.16.1-RC1 commons-codec-1.16.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1688/commons-codec/commons-codec/1.16.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Feb 04 15:31:03 UTC 2024
> commons-codec-1.16.1-bin.tar.gz=b9088ca7bd63cfe56c06c855af809948cae730b2be5c4c02619cf9a5cea2fab5c2226a3bec60d4f638dcd9af13700bb4e9f27fa1fac74d9249fae45042cb2a2a
> commons-codec-1.16.1-bin.zip=81e87157533219e0162e5a2218ed891dbe5310729c8fe0f7208da5f1dc8f058ddb46990b3d8cdace2984a37043d1d6a0648e8c2d04e78831e1beb8b1d58ae130
> commons-codec-1.16.1-bom.json=ccd6aadad4bd4ec67651eddff31fbb0c9568701bcc6a952e32929dc24c393d0b84a2f45e229eaf6f7b996dedf30524aaed25a359be49e85dedd6430219b8a1c3
> commons-codec-1.16.1-bom.xml=958dff0d9be2ac855bace9976903a5e289fe65b10a797006a962151c2f15516d5b0a3eb46f441f76ded49fea46581e7b07baa42912a9da583c385d6b9f5c849b
> commons-codec-1.16.1-javadoc.jar=027e85f4fe8adb2914e0b6bb80139081985e64097155f5f58f7c4141defc43a51d22da398c1cde1ac2ec18c6014c760e12bcfc40f48209bcb937a08249bff487
> commons-codec-1.16.1-sources.jar=434725ec624f3e60a0bb174f1d505e0aeb10d2255035d3ecc215248e3336fae0cee08374604a989c4c09458c772830342908ebcc269a232569b1d780f2dba04e
> commons-codec-1.16.1-src.tar.gz=8e2d40ae625c04e61b0dd7473dea0b32fdd13a6d3aad47b8b052952ca46f57d3df4917133f523ea147305a1c7ed9267cce7c4fa34d901496e36e9d5de9856e61
> commons-codec-1.16.1-src.zip=c2f5a26959c33c43c71df7eebfddf7c1a255a19faa8dd0324c19cfa902f9a4d3876689deffb99cf68456785b8960705b0a2b62e567c83b0ce674f26ef6db2eea
> commons-codec-1.16.1-test-sources.jar=1619f6d6dec4c4c0a26cb278cf53dffac2fb137d0c1f684156f19ef5db3a64ce2554dab29dc19a44247bf56d9bd3685c8c6d30234d15bd8cada28a12d35b47c4
> commons-codec-1.16.1-tests.jar=3e5496a79bc29558369cc356d3a2f8f0b2116fe8ae0c0ca2e3033988f47afd6b7ad1bbf8d3dabfda558b8912d4f77c40a67617237a8ddd70fe738e5c76e895e2
> commons-codec_commons-codec-1.16.1.spdx.json=a306898741d0fc70d9d773bc6ca88236c6d03bbce239d409c697ee516c1ff258c617599852dfdaa0cc80125e97fd555d2c9e1457f1adb43f863af88c9cd11bda
> 
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> openjdk version "17.0.9" 2023-10-17
> OpenJDK Runtime Environment Homebrew (build 17.0.9+0)
> OpenJDK 64-Bit Server VM Homebrew (build 17.0.9+0, mixed mode, sharing)
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.9, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.9/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.3", arch: "x86_64", family: "mac"
> 
> Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
> PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.16.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/site/index.html
>(note some *relative* links are broken and the 1.16.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.16.0):
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.1-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.

Re: [LAZY][VOTE] Release Apache Commons Parent 66 based on RC1

2024-02-01 Thread Rob Tompkins
+1

> On Jan 31, 2024, at 10:22 PM, Gary Gregory  wrote:
> 
> This lazy vote passes with one binding +1 vote from Gary Gregory.
> 
> Gary
> 
>> On Wed, Jan 31, 2024 at 10:22 PM Gary Gregory  wrote:
>> 
>> My +1
>> 
>> Gary
>> 
>>> On Mon, Jan 29, 2024 at 8:31 AM Gary Gregory  wrote:
>>> 
>>> I forgot the [LAZY] prefix in the email subject.
>>> 
>>> Gary
>>> 
>>> 
>>> On Mon, Jan 29, 2024 at 8:30 AM Gary Gregory  wrote:
 
 We have fixed a few bugs and added some enhancements since Apache
 Commons Parent 65 was released, so I would like to release Apache
 Commons Parent 66.
 
 Apache Commons Parent 66 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/parent/66-RC1 (svn
 revision 66916)
 
 The Git tag commons-parent-66-RC1 commit for this RC is
 918efa6b38828e6dbb93dd22043420117b64e82a which you can browse here:

 https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=918efa6b38828e6dbb93dd22043420117b64e82a
 You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-parent.git
 --branch commons-parent-66-RC1 commons-parent-66-RC1
 
 Maven artifacts are here:

 https://repository.apache.org/content/repositories/orgapachecommons-1686/org/apache/commons/commons-parent/66/
 
 These are the artifacts and their hashes:
 
 #Release SHA-512s
 #Mon Jan 29 13:21:38 UTC 2024
 commons-parent-66-bom.json=4f11cc49e4e5970445ed6557892cc7a42167afbc046b2f9a1078d921a416abf3ee37ae6e0072faf47a91ac9821e9060ccc1bc2e69ff6d6ac3326a1a82f5a6f04
 commons-parent-66-bom.xml=832c6c4b5d39a3320ee145a61262c18e2835e2db70aa675341253b0def7e50849a543030fb530b9e1d47e4e26d69ebbb31b765544b6b8a2b219d4faed0eda449
 commons-parent-66-site.xml=5f045989b2c281c567467548678fe8685efabf5c13104299eea87b6ab6b6a75c9e98b590d7b288b8ec3a06934061709d0851a6dd9d9b45100ee2950908ec2d6c
 commons-parent-66-src.tar.gz=8d3cb6a642586bbe0d6c310d4b5acc1674b0ffd6eae7c22bec0e41ecd9d04f837d333548e69485e9e9563706736fd1c4685d6097948b203659cf17bdf09858d8
 commons-parent-66-src.zip=107337796f4bf018c8b0c4603cdebd935d84134ff2092dae9fabb4d41209b705c25dec44a7af84ab451bc2077e5655377e94da6104feb17932da21dd84df24d9
 org.apache.commons_commons-parent-66.spdx.json=e0ae5d3e5bff1e827e1094780fed9d5f4d3fc21e6d910705b56b36ab25a2b4752cfb38b5564ff538ccd44290859cfdccc814e583481e0c761994497a0c700e2d
 
 I have tested this with:
 mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site 
 deploy
 
 Using:
 
 openjdk version "21.0.2" 2024-01-16
 OpenJDK Runtime Environment Homebrew (build 21.0.2)
 OpenJDK 64-Bit Server VM Homebrew (build 21.0.2, mixed mode, sharing)
 
 Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
 Maven home: /usr/local/Cellar/maven/3.9.6/libexec
 Java version: 21.0.2, vendor: Homebrew, runtime:
 /usr/local/Cellar/openjdk/21.0.2/libexec/openjdk.jdk/Contents/Home
 Default locale: en_US, platform encoding: UTF-8
 OS name: "mac os x", version: "14.3", arch: "x86_64", family: "mac"
 
 Darwin  23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58
 PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64
 
 Details of changes since 65 are in the release notes:

 https://dist.apache.org/repos/dist/dev/commons/parent/66-RC1/RELEASE-NOTES.txt

 https://dist.apache.org/repos/dist/dev/commons/parent/66-RC1/site/changes-report.html
 
 Site:

 https://dist.apache.org/repos/dist/dev/commons/parent/66-RC1/site/index.html
(note some *relative* links are broken and the 66 directories are
 not yet created - these will be OK once the site is deployed.)
 
 RAT Report:

 https://dist.apache.org/repos/dist/dev/commons/parent/66-RC1/site/rat-report.html
 
 KEYS:
  https://downloads.apache.org/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.
 
 1a) Clone and checkout the RC tag
 
 git clone https://gitbox.apache.org/repos/asf/commons-parent.git
 --branch commons-parent-66-RC1 commons-parent-66-RC1
 cd commons-parent-66-RC1
 
 1b) Download and unpack the source archive from:
 
 

Re: [IO-842] Deprecate more or undeprecate non-Charset methods

2024-01-25 Thread Rob Tompkins
I think we should remove the deprecations and add more explicit Javadocs that 
spell out that there are oddities with the defaultCharset() depending upon the 
operating system. Note this problem has been in existence since Java 1.4, and 
we did nothing about it for a considerable amount of time. Plus in Java 18 
forward we simply don’t need it, as Gary said.

Cheers,
-Rob

> On Jan 24, 2024, at 1:45 PM, Gary D. Gregory  wrote:
> 
> Hi All,
> 
> In the context of https://issues.apache.org/jira/browse/IO-842 and in light 
> of UTF-8 being the default Charset for Java 18 and up on all platforms -- 
> https://openjdk.org/jeps/400 --, we need to figure out whether to:
> 
> - Deprecate all non-Charset methods in favor of their Charset versions, or
> - Un-deprecate existing deprecated non-Charset methods.
> 
> See the ticket, please reply there or here as convenient.
> 
> Gary
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons BCEL 6.8.1 based on RC1

2024-01-10 Thread Rob Tompkins
+1 all looks good

> On Jan 7, 2024, at 3:20 PM, Gary Gregory  wrote:
> 
> We have fixed BCEL-370 for SpotBugs and added some enhancements since
> Apache Commons BCEL 6.8.0 was released, so I would like to release
> Apache Commons BCEL 6.8.1.
> 
> Apache Commons BCEL 6.8.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1 (svn
> revision 66459)
> 
> The Git tag commons-bcel-6.8.1-RC1 commit for this RC is
> 6785009095d66a4a2bc01e64d25de987847eb114 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=6785009095d66a4a2bc01e64d25de987847eb114
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> --branch commons-bcel-6.8.1-RC1 commons-bcel-6.8.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1685/org/apache/bcel/bcel/6.8.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jan 07 20:05:28 UTC 2024
> bcel-6.8.1-bin.tar.gz=137eefdeb8921bd2b82f24d560fe73aeaea7af77eb2db0b84b321159cc737490fbca709402094d8f54ca4921944608b1e54cfe3caa72c96ced8d65ffa23eb10d
> bcel-6.8.1-bin.zip=418ad7bd2f1f0d7176b0f4e9d64964ed7e3d486599db55b3ffa112948ace111e1372a5d406df5746f384f54edba58df9fd1022eb522c845ab64c7eae5551b9f8
> bcel-6.8.1-bom.json=679d5be5ab9aafc51bac9ac72f86d17c39c9a62237fd3fcebc25cda40001d753dd98db2578df8c992f4a156c6ebd514bf686a5a32a6da55034f9ebbca5cccd8e
> bcel-6.8.1-bom.xml=9a6d1d5eb3debd0cd23a4d8a46885ef55f4b16ea86042a3d3c4f6d19ea83e5039a1c94a27dcb1ae23091a0bff4e5ede652b8701d4cca9d6cfa925a0073ad6c60
> bcel-6.8.1-javadoc.jar=eee243d6898d3ddd78c0edafef2d3e120886aae2b1f60bc8e825e8f39c3008f4184563349e6f354b04bd3198ada34e66bacd793f1fd2b987a880497dad7566f1
> bcel-6.8.1-sources.jar=7af00081e0180f84d70c732b6099cefe2fd3f07bd13a697e471a9d7f7af29f31580d3f1271645b8e58d583bf5c13587fcfe9f2df81334a20c90314c1bd876a35
> bcel-6.8.1-src.tar.gz=1a38f4603bfe8692e4fc71a911fbb37ddc30ee5afa270d4b36f0325879a555df2cab34e2abf38645a3c7b780e30dec516a0eac21a0d7e18ff412a5762282360e
> bcel-6.8.1-src.zip=f6d4c953cf64995fc96c7c34c08e15ad1daad410c97db5efdf7acc1e70fa00f9c7c560aa9006fb10f46975268250663534fc45e635d25f090b2f4d3531a1c2a8
> bcel-6.8.1-test-sources.jar=3114e0cbaee9ba42ba57c860a91574f3f36ceb018e71a24003443353b59763bb885160c75c886ffb2e703933b8dfa27e33a694bca39db7f51150f263964593da
> bcel-6.8.1-tests.jar=1588bb81b339bc8f645335630ab31bf8df23776fd5757e4d608477e914feff15876bf3e2446c1ae28fb62cb71249da3c667298b543619e456468682dad14c938
> org.apache.bcel_bcel-6.8.1.spdx.json=7df4647adfb7a15ca9c58ac5c852898e0513cd3b8701686e1ed29b2bf2edd1c6da44a3ee6e8f69b398861b05c2e0ad60fb6960d99e1e309cbe3fd142c922cb1b
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 17.0.9, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.9/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.2.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10
> PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64
> 
> Details of changes since 6.8.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/site/index.html
>(note some *relative* links are broken and the 6.8.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 6.8.0):
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.1-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> --branch commons-bcel-6.8.1-RC1 commons-bcel-6.8.1-RC1
> cd commons-bcel-6.8.1-RC1
> 
> 1b) Download and unpack the source 

Re: [VOTE] Release Apache Commons Exec 1.4.0 based on RC1

2024-01-03 Thread Rob Tompkins
+1 signatures good, builds on java 8, 11, 17, and 21, reports all good, 
RELEASE-NOTES.txt good. Nit, the coverage is a touch low, but this is a very 
minor nit.

Send it!!!

Cheers,
-Rob

> On Jan 1, 2024, at 7:29 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Exec 1.3 was released, so I would like to release Apache
> Commons Exec 1.4.0.
> 
> Apache Commons Exec 1.4.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/exec/1.4.0-RC1 (svn
> revision 66375)
> 
> The Git tag commons-exec-1.4.0-RC1 commit for this RC is
> 00307444cc1274f631c0e0931472b3d01cf4b4dd which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-exec.git;a=commit;h=00307444cc1274f631c0e0931472b3d01cf4b4dd
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-exec.git
> --branch commons-exec-1.4.0-RC1 commons-exec-1.4.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1683/org/apache/commons/commons-exec/1.4.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Mon Jan 01 12:15:41 UTC 2024
> commons-exec-1.4.0-bin.tar.gz=4835da440d9f88bba7253b544647272fa4a6a298afcd99e4e83e58d1a9d16d18f05ee58a251719033e2f6b321d08cc0db6d23230b79a5cf451aea5e1a7041e04
> commons-exec-1.4.0-bin.zip=35b806102a714ea8a269b74eb126a6c04968fa2ea61d8e88ffdef5f71583859675d60caef7752c6db63f37e1c8056143f0ad657a5022fc1263e13274c01427ca
> commons-exec-1.4.0-bom.json=eee53518c448730d2a4d21c674399098f49ae8123a079cd03b68fc614cc5b8a1ad8aea62b81d0f347629b75644623c2ef1e44d69890b31c2ede51d0ca55d4db9
> commons-exec-1.4.0-bom.xml=dbbda1effcaa4a66c9d3842f21030a3cc0645168534fcf7745e59b9ae08661f31a2389c2cd8651fede38f06d3b5688e7dae381785854f51dd4369d54a7b03cb3
> commons-exec-1.4.0-javadoc.jar=a8084e90c4941000c93185d89d60752a1652b1fb7d5d372bb5292921a7927bfd0a9fab59039d914df46e224e60a20ed1c68d7f55d518474f06d8ee9891270bc6
> commons-exec-1.4.0-sources.jar=d09a1275677b71ea86f2536baf28290c06b069ea57001b7ab86a18edad5decc794a811bfc8d6ad194ee514ab0155e5742d7348c47a72b63dfdd6605b3a6f633d
> commons-exec-1.4.0-src.tar.gz=18ec2f138100e7d029425b805093a40f9ae86362c2ce82bc828716c7c4eda6df64b17a4798afe05925d2730488b9d7cef1425d0ef5229345c77a00ffa250de9f
> commons-exec-1.4.0-src.zip=26fa7c3707a9cfddf4c197844a8f216e3c02fc846ea7d68611807e4eabcfab909d26b9ec67dc0c1a1f6438006728a05a5610227559fa8b8ae05f5bea901d0c51
> commons-exec-1.4.0-test-sources.jar=971236b9a856d93f3cd38f29e48cdb5f890c205d28c1b810bc199283b3bee244535c5e9da22c3def1d76e8e8523385a2feedab73159eca9aa9fd28121cbe71c4
> commons-exec-1.4.0-tests.jar=06f1eda8d81c74b15a8eb8fc6009ff00bed943df6edcdbf6a106d93d98372ea7f214bfbd44ec46d998b64ff51d858d1363a5ff1c2da40236fcf608871f9f67a1
> org.apache.commons_commons-exec-1.4.0.spdx.json=cf16ce26bb47d078a2578cce0cd11e333d7428406d7537b952ff3a7e8ff3c61747415007abe394654a44e8c1080444bf21d15638c6285223bcebea855f288360
> 
> I have tested this with:
> 
> export TZ=UTC
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> mvn clean package artifact:compare -Dreference.repo=apache.snapshots
> -DskipTests -Dcommons.spdx.version=0.7.1 -Dspdx.skip
> 
> using:
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 21.0.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.2.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.2.0 Darwin Kernel Version 23.2.0: Wed Nov 15 21:54:10
> PST 2023; root:xnu-10002.61.3~2/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.3 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/exec/1.4.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/exec/1.4.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/exec/1.4.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.4.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.3):
>
> https://dist.apache.org/repos/dist/dev/commons/exec/1.4.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/exec/1.4.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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
> ==

Re: [all, site] Logo Update?

2023-12-26 Thread Rob Tompkins
Cool…I’ll have to work on the sizing but I think we’re ready.

Cheers,
-Rob

> On Dec 26, 2023, at 12:42 PM, Gary Gregory  wrote:
> 
> Go for it IMO.
> 
> Gary
> 
> On Tue, Dec 26, 2023, 11:11 AM Rob Tompkins  wrote:
> 
>> Thoughts?
>> 
>> -Rob
>> 
>> 
>> 
>>> On Dec 26, 2023, at 10:54 AM, Rob Tompkins  wrote:
>>> 
>>> I have Adobe Creative Suite.
>>> 
>>> -Rob
>>> 
>>>> On Dec 26, 2023, at 10:50 AM, Gilles Sadowski 
>> wrote:
>>>> 
>>>> It's a quick change to update the main page with the current
>>>> "graphical identity" of the ASF (new feather).  [I.e. just use the
>>>> logo which the ASF main site is using.]
>>>> Not so much to modify (using Gimp) each component's logo.
>>>> And something that will need redoing in a few months from
>>>> now...
>>>> 
>>>> Le mar. 26 déc. 2023 à 16:42, Gary Gregory  a
>> écrit :
>>>>> 
>>>>> Tip: copy and edit the SVG, probably using... Gimp?
>>>>> 
>>>>> Gary
>>>>> 
>>>>>>> [...]
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>> 
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [all, site] Logo Update?

2023-12-26 Thread Rob Tompkins
Thoughts?

-Rob



> On Dec 26, 2023, at 10:54 AM, Rob Tompkins  wrote:
> 
> I have Adobe Creative Suite.
> 
> -Rob
> 
>> On Dec 26, 2023, at 10:50 AM, Gilles Sadowski  wrote:
>> 
>> It's a quick change to update the main page with the current
>> "graphical identity" of the ASF (new feather).  [I.e. just use the
>> logo which the ASF main site is using.]
>> Not so much to modify (using Gimp) each component's logo.
>> And something that will need redoing in a few months from
>> now...
>> 
>> Le mar. 26 déc. 2023 à 16:42, Gary Gregory  a écrit :
>>> 
>>> Tip: copy and edit the SVG, probably using... Gimp?
>>> 
>>> Gary
>>> 
>>>>> [...]
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [all, site] Logo Update?

2023-12-26 Thread Rob Tompkins
I have Adobe Creative Suite.

-Rob

> On Dec 26, 2023, at 10:50 AM, Gilles Sadowski  wrote:
> 
> It's a quick change to update the main page with the current
> "graphical identity" of the ASF (new feather).  [I.e. just use the
> logo which the ASF main site is using.]
> Not so much to modify (using Gimp) each component's logo.
> And something that will need redoing in a few months from
> now...
> 
> Le mar. 26 déc. 2023 à 16:42, Gary Gregory  a écrit :
>> 
>> Tip: copy and edit the SVG, probably using... Gimp?
>> 
>> Gary
>> 
 [...]
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [all, site] Logo Update?

2023-12-26 Thread Rob Tompkins
If that’s indeed the case, then wouldn’t the easiest thing be to simply 
incorporate the feather into the current logo design as a quick update while we 
wait for the new branding?

-Rob

> On Dec 26, 2023, at 10:32 AM, Gilles Sadowski  wrote:
> 
> Le mar. 26 déc. 2023 à 16:12, Rob Tompkins  a écrit :
>> 
>> Good call. I’m going to add one to the list and then put the logos up for a 
>> [VOTE] to the community to choose which (by ordering them most preferred to 
>> least).
> 
> Well, a good logo is not just a question of preference; e.g. there may be
> some design guidelines which not everyone is aware of, or pay attention
> to, or otherwise finds appealing.
> 
> More importantly the ASF board has decided (AFAIK) to again change
> the "graphical identity" of the foundation; so this probably not the right
> time for reviving such discussion.
> 
> Regards,
> Gilles
> 
>> [...]
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [all, site] Logo Update?

2023-12-26 Thread Rob Tompkins
Good call. I’m going to add one to the list and then put the logos up for a 
[VOTE] to the community to choose which (by ordering them most preferred to 
least).

Cheers,
-Rob

> On Dec 26, 2023, at 7:51 AM, Gary Gregory  wrote:
> 
> It would be even nicer if the two feather styles matched 
> 
> Gary
> 
> On Tue, Dec 26, 2023, 7:14 AM Gilles Sadowski  wrote:
> 
>> Hello.
>> 
>> Le mar. 26 déc. 2023 à 03:52, Rob Tompkins  a écrit :
>>> 
>>> Hey all,
>>> 
>>> Should we use the more modern feather with the same logo (-1, -0, +0,
>> +1)? Happy to give a shot at creating the same logo with the new feather.
>> 
>> A logo with the "new" ASF graphics has been there for years:
>>  https://apache.org/logos/#commons
>> 
>> When the discussion occurred (IIRC there was a ML thread too),
>> very few provided an opinion:
>>  https://issues.apache.org/jira/browse/COMMONSSITE-86
>> Hence, the main "Commons" page was not updated.
>> 
>> Logo was updated for some components:
>>  https://commons.apache.org/proper/commons-math
>>  https://commons.apache.org/proper/commons-rng
>>  https://commons.apache.org/proper/commons-numbers
>>  https://commons.apache.org/proper/commons-geometry
>>  https://commons.apache.org/proper/commons-statistics
>> 
>> Regards,
>> Gilles
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons FileUpload 2.0.0-M2 based on RC1

2023-12-25 Thread Rob Tompkins
+1

Builds on java 11, 17, and 21.

All looks good, signatures, reports, site and RELEASE-NOTES.txt

Happy Holidays,
-Rob

> On Dec 24, 2023, at 2:53 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons FileUpload 2.0.0-M1 was released, so I would like to release
> Apache Commons FileUpload 2.0.0-M2.
> 
> Apache Commons FileUpload 2.0.0-M2 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M2-RC1
> (svn revision 66302)
> 
> The Git tag commons-fileupload-2.0.0-M2-RC1 commit for this RC is
> bcb3e82c164f8b9998b22e58e32463f634eaca8d which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-fileupload.git;a=commit;h=bcb3e82c164f8b9998b22e58e32463f634eaca8d
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-fileupload.git
> --branch commons-fileupload-2.0.0-M2-RC1
> commons-fileupload-2.0.0-M2-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1680/org/apache/commons/
> 
> These are the artifacts and their hashes:
> 
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2.pom.asc
> (SHA1: 258c9ed9ef03bd8b3940bef3474ee063000d6f66)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-cyclonedx.xml
> (SHA1: 34767391bcf98faeaa3d4ca908f51917280f2123)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-cyclonedx.xml.asc
> (SHA1: 4143882997bb100801cd7c02fc5d7f8743cab8d2)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-tests.jar.asc
> (SHA1: 2f25ba9d9ef3cf100881120b9130779bc9c94aca)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-sources.jar
> (SHA1: 3aa55c3cec9e157ca38ce0bfbf24b5060761b683)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-cyclonedx.json
> (SHA1: d272f0e16c423c50df971d228bad45af4cf63ca0)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2.spdx.json
> (SHA1: e212a1ba5d2dfce66bce92cebe8e4e377e709810)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-tests.jar
> (SHA1: 875f2a22082047a0fce201e7708b724e8bde43a6)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2.pom
> (SHA1: f2e32d4fc9a3cb453e8d69de52308c3288cd09e2)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-sources.jar.asc
> (SHA1: 9ff27e5bd440e4012d837b009d236444a7465a4f)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2.spdx.json.asc
> (SHA1: 5031a87ce30b63eee234f9795c8df60f44213008)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-test-sources.jar
> (SHA1: f716da74d7423c3b53b03cba19da37844059c635)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2.jar
> (SHA1: 5b16aec91c2e0b0e6052bff9795045c2704f6ca7)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-test-sources.jar.asc
> (SHA1: d4b140f77ee1343bea719425f3f49588af0eec31)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2.jar.asc
> (SHA1: eaf800b19705e63785ac2b41265bc0b60123ebcb)
> /org/apache/commons/commons-fileupload2-core/2.0.0-M2/commons-fileupload2-core-2.0.0-M2-cyclonedx.json.asc
> (SHA1: ff69cd09e2d1eb6ba71fc79b7234c228d9d57420)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2-sources.jar
> (SHA1: b580e7dc63f4a8aec6ca701875019f2c3fb1eb7c)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2-cyclonedx.json.asc
> (SHA1: af1d1f12e0bf69177bd0cf049353f3057f817164)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2.jar.asc
> (SHA1: 5a9d4bfb5999c1b25963913c31d6148f54661209)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2.spdx.json
> (SHA1: 4b838d7cfec302b7d8d200b291c416b1c56a89f8)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2-cyclonedx.json
> (SHA1: 5180ff1f0ef93b0e57bb9cf52cec3a0476c08002)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2-test-sources.jar
> (SHA1: 213612100d46cbd5afb3e2e229bb361ba8f1a1b9)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2-tests.jar
> (SHA1: 7c7130d99924077fc358d7cd57437948dcb38ef3)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2.spdx.json.asc
> (SHA1: 676568384ebbcd2c71de5191c6558fb59921dadc)
> /org/apache/commons/commons-fileupload2-javax/2.0.0-M2/commons-fileupload2-javax-2.0.0-M2-sources.jar.asc
> (SHA1: 

[all, site] Logo Update?

2023-12-25 Thread Rob Tompkins
Hey all,

Should we use the more modern feather with the same logo (-1, -0, +0, +1)? 
Happy to give a shot at creating the same logo with the new feather.

Cheers and happy holidays,
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons BCEL 6.8.0 based on RC1

2023-12-06 Thread Rob Tompkins
+1 everything looks good. Nits, coverage a tad low, cpd, pmd, todo’s

Send it

-Rob

> On Dec 3, 2023, at 11:33 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons BCEL 6.7.0 was released, so I would like to release Apache
> Commons BCEL 6.8.0.
> 
> Apache Commons BCEL 6.8.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.0-RC1 (svn
> revision 65804)
> 
> The Git tag commons-bcel-6.8.0-RC1 commit for this RC is
> cf6f7e710abf4eda2e0aa9aa914aa17878999583 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-bcel.git;a=commit;h=cf6f7e710abf4eda2e0aa9aa914aa17878999583
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-bcel.git
> --branch commons-bcel-6.8.0-RC1 commons-bcel-6.8.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1678/org/apache/bcel/bcel/6.8.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Dec 03 11:17:12 EST 2023
> bcel-6.8.0-bin.tar.gz=955d66a5a34d25c90c71273467a2f876f3b3fb3437fc533f7a7583ea0390474817aefbb9a9b4190973011ad053e145c9c0bac42832f8198b562e693a25b2803f
> bcel-6.8.0-bin.zip=04e5fe2830127add83108de8df61aab185e38a5117dddfa348533260b5d355da1fb0db56b0b5361e680308d2feea6a3b04acc99d6a93b9ad2dfdb943893cb583
> bcel-6.8.0-bom.json=1555e608b267a74adc10938377f8eb60f1b2fa477c1834582ded805530d3cf676ac14d6f1966bdd5d9ccef4cc9f2a32ff1ce6d9b6963fc1d288f8263585b639f
> bcel-6.8.0-bom.xml=e1bb499766046147619dd1f1443089b043ee11bf09234c19f14b15261ae54e186c51bd2f7f9f622a71dac1d6a6712bef4c504bd21e975550bef6cfe886c607ba
> bcel-6.8.0-javadoc.jar=5fdaa3d79e57a6fcff8e3dfd9295e4681d3f7b35ae6f248b6bee292e46f0f7cff6b80a88f198c6eed6a966be1e59d272e68f3d8dd39cee0b48ce8920e4ef7495
> bcel-6.8.0-sources.jar=a55973bc87409c525860709ff94055808cb46ce13f236f5a119e763ee4a024b9c0c3ac78c80c6e8489f6fc9c535aff8468f09a796889d5dc5c4f9dd593bb337e
> bcel-6.8.0-src.tar.gz=fcec4920f841b9b22b7fe05190ed09a31e2edd32dbc9bc6217981af34fecab0725249bbaf0e5810e0c7ef8a347dbe07fa1dfc1a80a7b651368ad4ea852f54f6e
> bcel-6.8.0-src.zip=4d7c00f9400b206db48823a77cb09bbb2b25074108e8980c84c701d6b73f77290cf3bed56e392d270c8e084d7c2306ac3fb9b4a4f7f1e6cb883b683f7b3d972e
> bcel-6.8.0-test-sources.jar=8924279acde0fc8d101cc27b9e69b514b98a69793c990cadaae193da0fe5913630b99ebfd10568a3baa5e79bd4d93f8020202accf12a6a0e14ef07deb31736db
> bcel-6.8.0-tests.jar=4d7715acb6d38d50f8a9e4cbef232190fd3d7efaf54ade772d677e129c89af69a528a1bff6dae6300058f2e1c1393acf18a554c85ac0a6f6d95f0aad4680426c
> org.apache.bcel_bcel-6.8.0.spdx.json=dc47d97c197e3e0ce124b7f3a03e74552b6764e46195058d47daca19a597fb49469119115a58e7f3dc951cb851c031e60840e09d94632c4687332049dc305c10
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 21.0.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:27
> PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 6.7.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.0-RC1/site/index.html
>(note some *relative* links are broken and the 6.8.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 6.7.0):
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.0-RC1/site/japicmp.html
> 
>Note that the above report notes one issue:
>MODIFIED (Serializable incompatible(!): field changed from
> nontransient to transient) public class
> org.apache.bcel.util.ClassVector
>Note that a java.util.List of org.apache.bcel.classfile.JavaClass
> is not serializable in the first place because JavaClass is not
> serializable.
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/bcel/6.8.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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
> 

Re: [VOTE] Release Apache Commons Validator 1.8.0 based on RC1

2023-12-06 Thread Rob Tompkins
+1 all looks good

> On Dec 2, 2023, at 10:26 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Validator 1.7 was released, so I would like to release Apache
> Commons Validator 1.8.0.
> 
> Apache Commons Validator 1.8.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/validator/1.8.0-RC1
> (svn revision 65799)
> 
> The Git tag commons-validator-1.8.0-RC1 commit for this RC is
> c4b1afc87797f7826b84ae7f024f3d8959781ddd which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-validator.git;a=commit;h=c4b1afc87797f7826b84ae7f024f3d8959781ddd
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-validator.git
> --branch commons-validator-1.8.0-RC1 commons-validator-1.8.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1677/commons-validator/commons-validator/1.8.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Dec 02 10:19:35 EST 2023
> commons-validator-1.8.0-bin.tar.gz=32128ff8ec1d992a1654e1cab0451152e844dd3076c25c80122b331dd4d3546a60b0325476ae079b83a4b8d852dc8dd48fbde64f04d19e22013e99b95b98978e
> commons-validator-1.8.0-bin.zip=436aa1b614144b35c644dc7f1725a72b16ba276ef2d66ceafb9964e2a2484cd3438f1d76bf82c8fdd9d6c4da47a34c8bad6897bad77528a7e1531f6c8eedf67a
> commons-validator-1.8.0-bom.json=111c721363c61cd2a85a8f6b881b2d0fbaa0b2ac12401458e65e4e39ebc4a68ec339bf21d11d424ef0034ab0ad1239458011444a99843152b5a0c35f8922975a
> commons-validator-1.8.0-bom.xml=1ecb419c19dce8d596cbe43e6c1690d8ce121fd1a9907b6e3a85a497517fedc0fa0ffc26acb3f7124672590a48b401e5a149c6d6fae3ee5067de8aabd7233ca7
> commons-validator-1.8.0-javadoc.jar=7a0b2ef23f2feb5f52269c47216f69137c62eec80a64bdd0e7ee7e413fd0d05c5c8b4c054f83a25dae8f0b3e3f4ef46663a05d9e67745196f870d4ce4a6e1b9e
> commons-validator-1.8.0-sources.jar=fe6a7039615a53638df01b1100d25a6f38451b58cd5be88027e3bc0f86b40dfa440a8a466b7097054a1133c71089958e5f8a5bf6fad67e6c7bacc9210d04e97a
> commons-validator-1.8.0-src.tar.gz=f0c2662e5db0bbc6ee9d05d5508caa02bf45b7c7ada92f4a97a867848f3d704b35552d47859a46567705194248e7b88cd8df8f082939012ab60b6aed446e36b2
> commons-validator-1.8.0-src.zip=530063f04d300c0322ef5c53960bd6dd2ea9879169efe64d28234ac9877b5638876e8ed020a16eb67198d528405d9656f6e94f08ffb7cdfaa0d9e916c77aa32f
> commons-validator-1.8.0-test-sources.jar=f111abe654dbc2241d81dbf5b7742c33a1dd304ba1f2ffe902546b1e8b97a7d8940cffd1692e7787124fd08f54a235f92a19ade41fd88a136e5135ea10db4222
> commons-validator-1.8.0-tests.jar=bc5440747c3192574b75378fceb535ab7f988403d24fb1fb9ca74de30a5d7790fb9ed953bda3c727b5552778cdcf03e7e85500fadb3350a888c8adaf86da957d
> commons-validator_commons-validator-1.8.0.spdx.json=36d397ce0e251258ec7a6a90f54a1d76585762e9ee680160b79979f73f4c31e506e8b6bc6e07186db83bc0e34a9996ccbefc069569f69753ef4fea2cdd40bb8b
> 
> I have tested this with
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
> Maven home: /usr/local/Cellar/maven/3.9.6/libexec
> Java version: 21.0.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:27
> PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.7 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/validator/1.8.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/validator/1.8.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/validator/1.8.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.8.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.7):
>
> https://dist.apache.org/repos/dist/dev/commons/validator/1.8.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/validator/1.8.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout 

Re: [VOTE] Release Apache Commons Logging 1.3.0 based on RC1

2023-11-26 Thread Rob Tompkins
+1 signatures; reports; site; release-notes; builds java: 8, 11, 17, and 21 all 
good. 

Thanks Gary!!

Happy thanksgiving

Cheers,
-Rob

> On Nov 26, 2023, at 4:46 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Logging 1.2 was released, so I would like to release Apache
> Commons Logging 1.3.0.
> 
> Apache Commons Logging 1.3.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1
> (svn revision 65553)
> 
> The Git tag commons-logging-1.3.0-RC1 commit for this RC is
> e0255a5845814802586b91c889ab3e9fc4bf9d68 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-logging.git;a=commit;h=e0255a5845814802586b91c889ab3e9fc4bf9d68
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-logging.git
> --branch commons-logging-1.3.0-RC1 commons-logging-1.3.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1676/commons-logging/commons-logging/1.3.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Nov 26 16:38:45 EST 2023
> commons-logging-1.3.0-adapters.jar=0b67e5fbca807b3d00ab5569cfac9fd14e268302ef514dee52eb1272762b35211d602045aefa71731108b900f6e0b7c78c3df39a989f3b86736e95a471b342c6
> commons-logging-1.3.0-api.jar=d801af15997767abfbf0168651b19a55b8958e3b8c0106e054bdfd0098fdcb198c8dad0c123bd91448d0cb7b81851d4606319e43fed102c976b47143e481f371
> commons-logging-1.3.0-bin.tar.gz=1fb9e4537fc59b75baf83b72a8e484604e6124ff7969b6f82955b29beeb5b86d9d115a494a6687e9a89a0b274f1ae9c226f289a7531334cc0451a3d4d5c2e3dc
> commons-logging-1.3.0-bin.zip=43291b189957da5882eaf753792a041cd25f599b7fb6d960a16799ae450ae3cde59197fe4a664d59243a44c0cdd067eb9979ef2a225b762b0f56264a871c325c
> commons-logging-1.3.0-bom.json=07580d9d52d4f93bf2a79e41388549a4f6f814cfcc5d6e05832036e480d0364e0bce212b79cc4e921d55587a00e0d1d1a1bcf8b3195fe9765e94f38294b60170
> commons-logging-1.3.0-bom.xml=48a60112f79f6809a515a525837094b16e0ebff7daeeb561f20b639f18d47b3585f8e21595c469229caca9a0f2287649dbd8ce70105baa7d36bd621b68f42af7
> commons-logging-1.3.0-javadoc.jar=73abbcf238b831d33fdb5c62406b6066183e3dce603535203b6fb0abc34c6aad9605eec2a5ca11981a2544b81447f8580f27a26f66e564f308c35152391c2cd7
> commons-logging-1.3.0-sources.jar=ca39a42b2380c2c85800368546d8903b72e13f62bec665dd52db16f21dc214ecf81ff8a51f4739b5393b1d31326668e4ad5d0402eb4570728ad2a4321aeb6aa1
> commons-logging-1.3.0-src.tar.gz=20cc40c7d7848da618801a86333f3984151d3089f806e5d7a1e92c83c1f90d330f1c7ded5d0ae70e48dd9de684f2e5da32de24fa2c406f6b419f77704c0e74f8
> commons-logging-1.3.0-src.zip=516db2b8854846cf4c2bf5f4f3f4b7fc132183a7003eed0cff291f53f7f0a35d0dc4cc7eb362cd99ad5bf619620f16f7079e3015a7e01bda9e8802eca04a3fa3
> commons-logging-1.3.0-test-sources.jar=159ec27c4343f926fe1cdc8977138b5200ef6f1284a3361ae3cd19520d3e7b117e418272a4534b768859f1229e8ff7cd3555bed4f292c27e583a92fe9f2f
> commons-logging-1.3.0-tests.jar=fb1d052e16ec83f9c6002a44ef79b84c08ad04b9ac3d378060e6adcf6d98860f4411c114837cca872427b1e5c663060a77f7157aabadf81fac1979ea34b44055
> commons-logging_commons-logging-1.3.0.spdx.json=a416b9ae6d632f0638eb1c90184ecbe85bb91ce641b5ccea6ed64a144a6af80b20decaeb5d369aabb5e1cedd266d966fec5bc7517465414ab68036c526f9cb21
> 
> I have tested this with
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: /usr/local/Cellar/maven/3.9.5/libexec
> Java version: 21.0.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:27
> PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.2 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.3.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.2):
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/site/japicmp.html
>Note that this report contains false-positives regarding generics:
> Generics are erased at compile-time, so can't be binary incompatible.
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/logging/1.3.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now.
> 
>  [ 

Re: [VOTE] Release Apache Commons IO 2.15.1 based on RC1

2023-11-26 Thread Rob Tompkins
+1

Struggled a little with the SPDX stuff, but all in all it looks good.

Reports all look correct (RAT included),  all tests run appropriately across 
java 8, 11, 17, and 21

Signatures all check out.

Send it!

> On Nov 24, 2023, at 11:38 AM, Gary Gregory  wrote:
> 
> We have fixed quite one important bug and added some enhancements
> since Apache Commons IO 2.15.0 was released, so I would like to
> release Apache Commons IO 2.15.1.
> 
> Apache Commons IO 2.15.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/io/2.15.1-RC1 (svn
> revision 65522)
> 
> The Git tag commons-io-2.15.1-RC1 commit for this RC is
> dc51644d5adbb0c461efb58380ec51fbca10005d which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=dc51644d5adbb0c461efb58380ec51fbca10005d
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-io.git
> --branch commons-io-2.15.1-RC1 commons-io-2.15.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1675/commons-io/commons-io/2.15.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Fri Nov 24 11:28:20 EST 2023
> commons-io-2.15.1-bin.tar.gz=c00b9cbd8e213311137e10e3425cf19af60c737103b3ed968c33fdc5f803892f364f4e754a7d3a222a579ee6a58a1e8731ef51835d516d2a6aab8fd2f0845e35
> commons-io-2.15.1-bin.zip=944d0e2e750895d8371c7ecbed5e0593bceec404b7a0c6c9f1c2e77986ccabb2280b84485dcf34ae4339256ae164b8e04d4b95101bbfaf28de24aea711fed4bd
> commons-io-2.15.1-bom.json=7186ba77d019082653b32b08f91ed64d9de7ed567d9978a7888acc87ee9c8af1b0b4344a4ffd7f01b2cb5393b5fb74c368e2769527a5242372c124ba2625db19
> commons-io-2.15.1-bom.xml=afc61569e85d1a4d4c6c49a91caae3479cd79c6ba9623d2f662a22ee0129111e42d668414560b16fce9606f602a2cca2127f9de57e524332316ba871ffe90e31
> commons-io-2.15.1-javadoc.jar=f275a97668465fe467bd3a690d60da4d842957b94fe22247bbeff43afa4ad008d7fed4e194f8f42ac55b3979a4015dc907f02259e2fe679288f63e469e31366c
> commons-io-2.15.1-sources.jar=3ee4e22de8a3e04ff8651873b596a23bd517152f3ede3d14af1e5b6b52eb878f360a2ac672453cf67efb948fea4e969019f9023dd7d1d1b064fb164cc17154a2
> commons-io-2.15.1-src.tar.gz=809c7aa66354f2e35fd23f295c4e2f325596ee7f842b7f63f6acc3bd9377c17d4dd276ce62c477fff8d51d0d660e9addbc068270a876097cbecfe3e64f57f385
> commons-io-2.15.1-src.zip=f98e754fe68827390960f5ca08d8b3ae4eed54243e164c9e347f6f8f40519d096f6bfff4e2696d79870576be36a7140a6cea600381c3c8739361e72a6b392375
> commons-io-2.15.1-test-sources.jar=6a1a70ef392183ad0217e8f517ddcce0fb840c1b6076f9a3407a240e3738da94ce24639422fcda232cd96526360a85284765bef60c127b2dd2be8e47ee6fe96c
> commons-io-2.15.1-tests.jar=2bfeac593dfa23cc0da62e4a2c3470ef63ee54ca6987ac2176cb437d0c3ca867f0d92b62d166244da94d9154362cf58486904ef35c3c95645dcd8074bb4d6674
> commons-io_commons-io-2.15.1.spdx.json=eada6a6c341abad84bad3d3fd6e9a00326bf7646110bcc46c6db997bc9d28eed372daa622371abbaad5abf58f47bd4870c7af9f0662d5769e6cb71565987be15
> 
> I have tested this with
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: /usr/local/Cellar/maven/3.9.5/libexec
> Java version: 21.0.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1.1", arch: "x86_64", family: "mac"
> 
> Darwin  23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:27
> PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 2.15.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.15.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.15.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.15.1-RC1/site/index.html
>(note some *relative* links are broken and the 2.15.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.15.0):
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.15.1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.15.1-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons Lang 3.14.0 based on RC1

2023-11-19 Thread Rob Tompkins
Looking over the release there are some japicmp curiosities that I think are 
k, and the CPD report has a few nits in it.
Otherwise all looks good.

+1

-Rob

Thank you for the good work!!!

> On Nov 18, 2023, at 10:15 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Lang 3.13.0 was released, so I would like to release Apache
> Commons Lang 3.14.0.
> 
> Apache Commons Lang 3.14.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.14.0-RC1
> (svn revision 65412)
> 
> The Git tag commons-lang-3.14.0-RC1 commit for this RC is
> c8774fa74adbbbcd4e5f915ab6bc3aa10d877419 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=c8774fa74adbbbcd4e5f915ab6bc3aa10d877419
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-lang.git
> --branch commons-lang-3.14.0-RC1 commons-lang-3.14.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1674/org/apache/commons/commons-lang3/3.14.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Nov 18 10:03:24 EST 2023
> Apache\ Commons\
> Lang-3.14.0.spdx.rdf.xml=497cb8e231b7c3421f4ed27063f889c1ff9815d5cc76aa992d7c1f166ffe0ced0313e3a8daf17d0f2eb412ee4ce8923fb87b7abd6e897a6180005d9ce2c97b15
> commons-lang3-3.14.0-bin.tar.gz=8e7e62418a49ba810512c13a640a8bf35f878fcd54af32fdaabe37817f58b21b475980ba663fba4887e45ef8d88af8ff17796f20d202e929e8e2574546dc
> commons-lang3-3.14.0-bin.zip=444ef65dfe130fdb50450778c757a23ccb16fdf4ac7afe655934ae5b0d3faf7b2001ba951383d9e69baeb1fdc879c81e4542f8ceb47c7044fb5266cdddbc0db6
> commons-lang3-3.14.0-bom.json=cce914a85f156c5757df5e6c28b9964f0be04f92035557491dd37dbef28efa812c4e975c391c38e2bfe807a530585ab666e40b544f76cc7ad9fb8a04c6012fbd
> commons-lang3-3.14.0-bom.xml=51a55d0d1bcd2f093cb2f0b84870b2381ab9da740582cba04ae02ea6e50a97e0656bd2bc2871a8d6a7fc313f033ab70544134845dec193552ef9ecc8db3a0ecb
> commons-lang3-3.14.0-javadoc.jar=40b1d2b1fe6a621d715d1290096942107f1d1bbb41a51096c70292be0803d5a6f9214fd8b5810ad154848d20bb498871ae9d2f8ad11649f0affaaa00f7c8e25c
> commons-lang3-3.14.0-sources.jar=16363e06b52908ecbec9a62f4b1e0a39cf3de9c646504f0cee5bbe845739cbfb99f01438808bab2c407fc72d4adf212487886422415d9972614c5ee96273deab
> commons-lang3-3.14.0-src.tar.gz=1ee4176c3588c11594a79f416a1f34b063cddb10c2124a37640fee48e5d8135091573002b6bf1eda5a60a324c1125665dadc93f9bfda32c9270c35113b6e1bea
> commons-lang3-3.14.0-src.zip=8c1cc37e2be29e71cfb80775c4887b2c6cd466ef05bb59a4afc11bc5fbe9b253dc57bda5e29b05ca6f1e9b497d84c56a5573c1e64b659a43bedcbe5bc3105b11
> commons-lang3-3.14.0-test-sources.jar=dd8d9670cf91b4504804f855c74c75109060c86e87eeb5c56f31ff9241ffde272855fac21ce456303dac1578e5c58238cb59e0e628854ae9d4f1451e15f969b8
> commons-lang3-3.14.0-tests.jar=e5cc518ba310db0a20361502a0bb8896f05f0c0552b8170a37485922030e15a1221e9e027753ad522202af2326664cb2f0c14d409bac6bfe44b9065fc07bbc02
> 
> I have tested this with 'mvn -V -Prelease -Ptest-deploy -P jacoco -P
> japicmp clean package site deploy'
> 
> using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: /usr/local/Cellar/maven/3.9.5/libexec
> Java version: 21.0.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1.1", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct
> 9 21:27:27 PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 3.13.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.14.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.14.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.14.0-RC1/site/index.html
>(note some *relative* links are broken and the 3.14.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.13.0):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.14.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.14.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons Compress 1.25.0 based on RC1

2023-11-15 Thread Rob Tompkins
+1 Signatures, Reports, Site, Release-Notes, all good. Builds on java 8, 11, 
and 17 properly

some nits in the CPD, PMD space, but nothing of note.

Hopefully the saying holds true luck favours the well prepared …. generally 
needing it :-)

> On Nov 12, 2023, at 5:47 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Compress 1.24.0 was released, so I would like to release
> Apache Commons Compress 1.25.0.
> 
> Apache Commons Compress 1.25.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/compress/1.25.0-RC1
> (svn revision 65236)
> 
> The Git tag commons-compress-1.25.0-RC1 commit for this RC is
> 38dec7fb4690c023ef0af9661e0e1ae4f254a769 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-compress.git;a=commit;h=38dec7fb4690c023ef0af9661e0e1ae4f254a769
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-compress.git
> --branch commons-compress-1.25.0-RC1 commons-compress-1.25.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1672/org/apache/commons/commons-compress/1.25.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Nov 12 17:15:57 EST 2023
> commons-compress-1.25.0-bin.tar.gz=1088e4f8c46a5b9d95cdecfe2425d359464cab354035842689a0487328ab06796a69b96bb1cbeff096397782904b1ecc708eebd7f6aa7e6008bcb9fa0c6eccbb
> commons-compress-1.25.0-bin.zip=4b648a450f00bb338a8a0d3ef5873fb2e29280e080253a5af91423b904cb7cf3ecb80db3f6d55d65a46759f4554a0cabc8b766fd5fc3fbb97cb58f1e8414a744
> commons-compress-1.25.0-bom.json=44f3c53d5f6435465e422c774ac759301180520d4a94da5b100cc58149d73171bdda72e50c5643cd8372e4787827bc46a028eae3e0b6167113606d80acd0aa1b
> commons-compress-1.25.0-bom.xml=b7e6ade9bd71d63f906070520d6665fb9bf51363c9a5c5a45093c0082ae732aff7c1167328be3701ef7ab575f2b899f65763cb6369c037ee83bba25f993630c5
> commons-compress-1.25.0-javadoc.jar=6689ff023d9a272c068c2a2ceb2fe8a48efb051e0d3a59f42ae3892b158986c6171b6c53e32e93ab5206a38786a9c1fe5d03c5a24b04acc45c530e73dd299684
> commons-compress-1.25.0-sources.jar=a6451a8998e673add1e747f9963e967a8d1945a1cf967841f036030218f8185b14d1b5246ec79f08ac57a814b8bf48ef2eb96475281a9c21d6bf29f3de0f4ed4
> commons-compress-1.25.0-src.tar.gz=58d9ed8160af2842fe4338ae265d591b9f96293f8997c420721e86f8c8ffce5b3a5dbc83b87b813ea68505b56cbddd02332540f0a4e01bdc7f7f36e357ba2b7a
> commons-compress-1.25.0-src.zip=a94f5ece521f6d7403e64016e52ffc2be64cfdaf918a4c10d7db594a59e62c4184bbe7cd90af14d8d9e9d7412f6f25f1dd9b19c3b13698925134f2acafa2c0b9
> commons-compress-1.25.0-test-sources.jar=da493ac16464ff5ff69e054e13bbba15220df3b35d5fd0b9022b012c506fda5be403c334b60e818a9fffb4b21c453dd6eb8e8196578bb939bb2eb8c5dd4c22ac
> commons-compress-1.25.0-tests.jar=c9bcdd1aab8fdb98c93c917c53263a5e4eae90b44caa07e156b41228bb956c8457498877ef8b6317c73664ba319719e6f22c7098889c5d22d1aa0519a55d8543
> org.apache.commons_commons-compress-1.25.0.spdx.json=d56e3df78317b44957905b58f4d7a7db4d98a7333c58d3ae3e15a3d0af3b6cd6e857f0f4c2b358ebfeb0ffe220afa285f8db4ac6475ae2984c588f1e6a77dd2d
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: /usr/local/Cellar/maven/3.9.5/libexec
> Java version: 21.0.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21.0.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.1", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct
> 9 21:27:27 PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.24.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.25.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.25.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.25.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.25.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.24.0):
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.25.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/compress/1.25.0-RC1/site/rat-report.html
> 
> KEYS:
>https://downloads.apache.org/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.
> 
> 

Re: [VOTE] Release Apache Commons DBCP 2.11.0 based on RC1

2023-10-28 Thread Rob Tompkins
+1

> On Oct 27, 2023, at 11:13 AM, Gary Gregory  wrote:
> 
> My +1
> 
> Gary
> 
>> On Wed, Oct 25, 2023 at 6:26 AM Bruno Kinoshita  
>> wrote:
>> 
>>   [x] +1 Release these artifacts
>> 
>> Site reports OK, building fine on
>> 
>> Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
>> Maven home: /opt/apache-maven-3.8.5
>> Java version: 17.0.8.1, vendor: Private Build, runtime:
>> /usr/lib/jvm/java-17-openjdk-amd64
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "5.15.0-87-generic", arch: "amd64", family:
>> "unix"
>> 
>>> On Mon, 23 Oct 2023 at 19:55, Gary Gregory  wrote:
>>> 
>>> We have fixed a few bugs and added some enhancements since Apache
>>> Commons DBCP 2.9.0 was released, so I would like to release Apache
>>> Commons DBCP 2.11.0.
>>> 
>>> Apache Commons DBCP 2.11.0 RC1 is available for review here:
>>>https://dist.apache.org/repos/dist/dev/commons/dbcp/2.11.0-RC1
>>> (svn revision 64680)
>>> 
>>> The Git tag commons-dbcp-2.11.0-RC1 commit for this RC is
>>> e57ce3cf019ffa9534b88735c454c54afbe9849f which you can browse here:
>>> 
>>> https://gitbox.apache.org/repos/asf?p=commons-dbcp.git;a=commit;h=e57ce3cf019ffa9534b88735c454c54afbe9849f
>>> You may checkout this tag using:
>>>git clone https://gitbox.apache.org/repos/asf/commons-dbcp.git
>>> --branch 
>>> commons-dbcp-2.11.0-RC1 commons-dbcp-2.11.0-RC1
>>> 
>>> Maven artifacts are here:
>>> 
>>> https://repository.apache.org/content/repositories/orgapachecommons-1668/org/apache/commons/commons-dbcp2/2.11.0/
>>> 
>>> These are the artifacts and their hashes:
>>> 
>>> #Release SHA-512s
>>> #Mon Oct 23 13:37:23 EDT 2023
>>> Apache\ Commons\
>>> 
>>> DBCP-2.11.0.spdx.rdf.xml=3d02a79fc5cfcb453195efe4a045f7b37ded7ba0fb0eadb301f7800e86019e3d7d9824e47f3db04ce530936cb770ad0c39cff2801070d9171c862085a79416c3
>>> 
>>> commons-dbcp2-2.11.0-bin.tar.gz=34432889d6d973c6ff662c1189713fb48fdb431433a969b11186501fab338b6fe1ec3c402454dfebb7a16f8fb5e8e7c67633868a1a796faafb322d7a8215a527
>>> 
>>> commons-dbcp2-2.11.0-bin.zip=b82e9e8e2c9df52424e59a0fbb2b1bd1cacd9f37686a237392d0801ab4bf69c7d0fe8b886442cc1a0613e04bb96039bf77e093bb0cd861d809ba9761d3a74359
>>> 
>>> commons-dbcp2-2.11.0-bom.json=2c338fc5cea7e3210c4c489316b30c4313ae20139593b29e5d3970b01f17e094f2880e13230c83ac02373b8b8e30c162835bbcf85502084eab40f87b94bf4560
>>> 
>>> commons-dbcp2-2.11.0-bom.xml=93a1d28bfa6e2f3d99452be23e02aae107b32a9cf7bdd5547c76f3bcb93a7f536a7a2f71231975e794e096c335618e14c43c52e53fd34bc12c626d10e6efb72b
>>> 
>>> commons-dbcp2-2.11.0-javadoc.jar=bb4235fb91a74934ef408439019091a2f9938d3297fa932aa58f104532aab02911be77a674c945ea62b1d7dc1713466c375bedd87d0395db44f3a9aa3cf47870
>>> 
>>> commons-dbcp2-2.11.0-sources.jar=a4f5f86a281853191a526d53dc05551cb7a72a83078d521c6e7a06e92a607db3a7627af4d819d90bbc168c20228f4e2e55a1763c77a4c7e085171964b692810b
>>> 
>>> commons-dbcp2-2.11.0-src.tar.gz=2f73c4637a098925f7cf56fc49ee390a471f1f3faa50e8ee1595c762644437ea85683fa1c3ee44bf89b2f821716f6ee344ea09839cda6dee173b59dc49ba524b
>>> 
>>> commons-dbcp2-2.11.0-src.zip=212e84f4a31a7b192ae4d534292b4d5c6dd48f3650c1caf844dad34b97c498d027266f5d3fae220efee1bbdb75df95adc9d6f58f35bb445b653dbbee3c485de2
>>> 
>>> commons-dbcp2-2.11.0-test-sources.jar=78107b2437aa4b7232522f8c9791085da2f8421056208f7df220e327d7b45efb222da0eb2d1add99aa3d0d4c15e934d3a81f9cc6a5aa13bbd2f96370ca4d3365
>>> 
>>> commons-dbcp2-2.11.0-tests.jar=553de32da56551a221fd7f974a6b704fc82a130546469ccb9de857504be4e4db3a8fde0911602270ca2c66b8dd61f5066c72ea935f39c1555ae5b7adc7b2af15
>>> 
>>> I have tested this with:
>>> 
>>> mvn -V -Ptest-deploy -P jacoco -P japicmp clean package site deploy
>>> 
>>> Using:
>>> 
>>> pache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
>>> Maven home: /usr/local/Cellar/maven/3.9.5/libexec
>>> Java version: 21, vendor: Homebrew, runtime:
>>> /usr/local/Cellar/openjdk/21/libexec/openjdk.jdk/Contents/Home
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
>>> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
>>> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
>>> 
>>> Details of changes since 2.9.0 are in the release notes:
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.11.0-RC1/RELEASE-NOTES.txt
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.11.0-RC1/site/changes-report.html
>>> 
>>> Site:
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.11.0-RC1/site/index.html
>>>(note some *relative* links are broken and the 2.11.0 directories
>>> are not yet created - these will be OK once the site is deployed.)
>>> 
>>> JApiCmp Report (compared to 2.9.0):
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.11.0-RC1/site/japicmp.html
>>> 
>>> RAT Report:
>>> 
>>> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.11.0-RC1/site/rat-report.html
>>> 
>>> 

Potential Security Issues (was: Re: [VOTE] Release Apache Commons Text 1.11.0 based on RC1)

2023-10-27 Thread Rob Tompkins
I would bring this up in secur...@commons.apache.org if you have something 
noteworthy. Though a lot of people don’t understand that text manipulation is 
an extremely general toolkit making security concerns something that would 
occur at a higher lever with regards to the system using commons-text. Granted, 
I don’t know your specific situation, thus I would suggest emailing the 
security list and having a conversation there as security conversations in the 
open yield the public knowing about defects before they can be remediated.

Cheers,
-Rob

> On Oct 24, 2023, at 11:46 AM, Elliotte Rusty Harold  
> wrote:
> 
> It's worth triaging the bug tracker sometime. At a quick glance I saw
> several other issues that are arguably security related, mostly around
> character escaping and unescaping.
> 
> On Tue, Oct 24, 2023 at 11:43 AM Gary Gregory  wrote:
>> 
>> The issue is a year old with zero comments, I downgraded it to "Major".
>> 
>> What's worse is that if it were a real security issue, it should have gone
>> through our security protocol and not a Jira (initially at least).
>> 
>> Gary
>> 
>> On Tue, Oct 24, 2023, 10:32 AM Elliotte Rusty Harold 
>> wrote:
>> 
>>> 
>>> https://issues.apache.org/jira/projects/TEXT/issues/TEXT-220?filter=allopenissues
>>> is prirotized as a blocker. I haven't analyzed it in detail so I'm not
>>> sure, but it is security related. If it is a blocker it should be
>>> resolved before 1.11.0. If it is not a blocker, then the priority
>>> should be downgraded.
>>> 
>>> On Tue, Oct 24, 2023 at 9:47 AM Gary Gregory 
>>> wrote:
 
 We have fixed quite a few bugs and added some significant enhancements
 since Apache Commons Text 1.10.0 was released, so I would like to
 release Apache Commons Text 1.11.0.
 
 Apache Commons Text 1.11.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/text/1.11.0-RC1
 (svn revision 64797)
 
 The Git tag commons-text-1.11.0-RC1 commit for this RC is
 6e2be58f54bb8e376fbb5188ad964cde2ff6f362 which you can browse here:
 
>>> https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=6e2be58f54bb8e376fbb5188ad964cde2ff6f362
 You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-text.git
 --branch commons-text-1.11.0-RC1 commons-text-1.11.0-RC1
 
 Maven artifacts are here:
 
>>> https://repository.apache.org/content/repositories/orgapachecommons-1670/org/apache/commons/commons-text/1.11.0/
 
 These are the artifacts and their hashes:
 
 #Release SHA-512s
 #Tue Oct 24 09:39:25 EDT 2023
 
>>> commons-text-1.11.0-bin.tar.gz=2e94877000dd270b69e2e8cbf49f258a90b4c628b6b6b0814e300a2f0e9c391f0816dceb0707e596ae3b7c9532f93e7a4917df47c77f44b3a810e14042ce5f3f
 
>>> commons-text-1.11.0-bin.zip=f2480ffc6e9d1d678233830602da1c525814cfb8e951872dc4725d3a8e1957dcef8291309dc6ad20789003f04d61e21901eeb606d8f7a946e41c599dd0f35141
 
>>> commons-text-1.11.0-bom.json=1acd3a1a3b297f7460b8eb13d0e156644076186de422eaefd74af38e35885190c87e1ff4179222b6d96537a06069df2d03eb77b1bb24ccce8f854bb491e78334
 
>>> commons-text-1.11.0-bom.xml=e17bdf02c8704b62b5a3e27d500675704ffba3dd6d934b5f0877261feebac52037faa6f85eea3823422d5dcdcbc35314ec874c189c0cd20a82093a8598bfa7b9
 
>>> commons-text-1.11.0-javadoc.jar=63eb0a2c9004854d43ed3ea6e113af07aa2d11632af5beb17a3b1da8f65ef0cecb74e10ac2b496f67e4760cdeaf6925647d4b1fccd40dd6ce66dc076009c42d8
 
>>> commons-text-1.11.0-sources.jar=d937fe2eb28fa28a7b345338cc05b5101f3303baa501f8f6ad4a0efb604375b90997292bcccbdc994889415c3ea709b8b18497a04f83f050661db92a7f5ccaae
 
>>> commons-text-1.11.0-src.tar.gz=3a97b58eae3e8a51fe46c3296021622bfe912869b2d9666c745f345d574bbc86307acfb39b329c6a544728b35d200487c6b752de1909a209692a2f00fb260460
 
>>> commons-text-1.11.0-src.zip=72d75261812df2f004aa680d6fbe5c71b77558f89ff03d117363f77811dfbda891c5f489dbae40132063ab1db1d5d30ca81da0674c79c817e9527b260d7a8560
 
>>> commons-text-1.11.0-test-sources.jar=44191a4135b572397131517eac9394564fef0129693110ced2e0d1c8585857b6eedebec8f653bb70f79d74e0334dcc7cc1f663a9101c262651e6e973251e875a
 
>>> commons-text-1.11.0-tests.jar=e7d8c3d6e8c056fe793864d8cac4aa84e49789609fc7ea73270a3ba9829451300d4b6663641a013e3fc25d0ae97f57fc1258b303d89f6ed23c44116b22c0989c
 
>>> org.apache.commons_commons-text-1.11.0.spdx.json=64b008e082a13db858015e8680183a83d4a29be73dba66b5eb49b6ea77e11b676f1f8b997ab4fce49f0778423b97612516139679af1cb552b3adf65f296cccb7
 
 I have tested this with:
 
 mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
>>> deploy
 
 Using:
 
 Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
 Maven home: /usr/local/Cellar/maven/3.9.5/libexec
 Java version: 21, vendor: Homebrew, runtime:
 /usr/local/Cellar/openjdk/21/libexec/openjdk.jdk/Contents/Home
 Default locale: en_US, platform encoding: UTF-8
 OS name: "mac 

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

2023-10-26 Thread Rob Tompkins
+1 - signatures good, rat good, reports good, builds good, site good, release 
note good.

Keep crushing it Gary!

Cheers,
-Rob

> On Oct 24, 2023, at 9:47 AM, Gary Gregory  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Text 1.10.0 was released, so I would like to
> release Apache Commons Text 1.11.0.
> 
> Apache Commons Text 1.11.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/text/1.11.0-RC1
> (svn revision 64797)
> 
> The Git tag commons-text-1.11.0-RC1 commit for this RC is
> 6e2be58f54bb8e376fbb5188ad964cde2ff6f362 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-text.git;a=commit;h=6e2be58f54bb8e376fbb5188ad964cde2ff6f362
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-text.git
> --branch commons-text-1.11.0-RC1 commons-text-1.11.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1670/org/apache/commons/commons-text/1.11.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Tue Oct 24 09:39:25 EDT 2023
> commons-text-1.11.0-bin.tar.gz=2e94877000dd270b69e2e8cbf49f258a90b4c628b6b6b0814e300a2f0e9c391f0816dceb0707e596ae3b7c9532f93e7a4917df47c77f44b3a810e14042ce5f3f
> commons-text-1.11.0-bin.zip=f2480ffc6e9d1d678233830602da1c525814cfb8e951872dc4725d3a8e1957dcef8291309dc6ad20789003f04d61e21901eeb606d8f7a946e41c599dd0f35141
> commons-text-1.11.0-bom.json=1acd3a1a3b297f7460b8eb13d0e156644076186de422eaefd74af38e35885190c87e1ff4179222b6d96537a06069df2d03eb77b1bb24ccce8f854bb491e78334
> commons-text-1.11.0-bom.xml=e17bdf02c8704b62b5a3e27d500675704ffba3dd6d934b5f0877261feebac52037faa6f85eea3823422d5dcdcbc35314ec874c189c0cd20a82093a8598bfa7b9
> commons-text-1.11.0-javadoc.jar=63eb0a2c9004854d43ed3ea6e113af07aa2d11632af5beb17a3b1da8f65ef0cecb74e10ac2b496f67e4760cdeaf6925647d4b1fccd40dd6ce66dc076009c42d8
> commons-text-1.11.0-sources.jar=d937fe2eb28fa28a7b345338cc05b5101f3303baa501f8f6ad4a0efb604375b90997292bcccbdc994889415c3ea709b8b18497a04f83f050661db92a7f5ccaae
> commons-text-1.11.0-src.tar.gz=3a97b58eae3e8a51fe46c3296021622bfe912869b2d9666c745f345d574bbc86307acfb39b329c6a544728b35d200487c6b752de1909a209692a2f00fb260460
> commons-text-1.11.0-src.zip=72d75261812df2f004aa680d6fbe5c71b77558f89ff03d117363f77811dfbda891c5f489dbae40132063ab1db1d5d30ca81da0674c79c817e9527b260d7a8560
> commons-text-1.11.0-test-sources.jar=44191a4135b572397131517eac9394564fef0129693110ced2e0d1c8585857b6eedebec8f653bb70f79d74e0334dcc7cc1f663a9101c262651e6e973251e875a
> commons-text-1.11.0-tests.jar=e7d8c3d6e8c056fe793864d8cac4aa84e49789609fc7ea73270a3ba9829451300d4b6663641a013e3fc25d0ae97f57fc1258b303d89f6ed23c44116b22c0989c
> org.apache.commons_commons-text-1.11.0.spdx.json=64b008e082a13db858015e8680183a83d4a29be73dba66b5eb49b6ea77e11b676f1f8b997ab4fce49f0778423b97612516139679af1cb552b3adf65f296cccb7
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: /usr/local/Cellar/maven/3.9.5/libexec
> Java version: 21, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.10.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.11.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.11.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.11.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.11.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.10.0):
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.11.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/text/1.11.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons CLI 1.6.0 based on RC1

2023-10-25 Thread Rob Tompkins
+1, signatures, site, builds, and release notes all good

Send it!

> On Oct 23, 2023, at 1:07 PM, Gary Gregory  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons CLI 1.5.0 was released, so I would like to
> release Apache Commons CLI 1.6.0.
> 
> Apache Commons CLI 1.6.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1 (svn
> revision 64679)
> 
> The Git tag commons-cli-1.6.0-RC1 commit for this RC is
> 0d29a55998aa52be8832497527e266630f97c371 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=0d29a55998aa52be8832497527e266630f97c371
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-cli.git
> --branch commons-cli-1.6.0-RC1 commons-cli-1.6.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1667/commons-cli/commons-cli/1.6.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Mon Oct 23 12:59:22 EDT 2023
> commons-cli-1.6.0-bin.tar.gz=26487b81809d7bb79c21423d5a1556bcd0945db59a5096793fa14699b8b5001018707c72a3475a48a5071777f2c3c6a5d91936e1b7dcbd675ece855f1b929a82
> commons-cli-1.6.0-bin.zip=9e7b89b2b32363acf9c4a773559697eb832c1fe1236859cbbd5e254bed5d205e95f46ef1cce563ca4612d672fc22a7239adcc3ba573b0fa23d80b967efe9b8bf
> commons-cli-1.6.0-bom.json=532c4312167b76e2003f706e2bb7c45eec0782fe6d9977a0a5533f56961808c7e8d0c8b705acb11f5537fe5aabe0b6143c02184c666919d77a1fa7b4fed196ee
> commons-cli-1.6.0-bom.xml=eb4ca6cc32dcb9f122fe86fffaea411cb768826566961582e618d1480341490a72503f225b7150ef21631f50ef3edfbbb5fed25d2b2b7d113e0b3e86ef8786e7
> commons-cli-1.6.0-javadoc.jar=830e0c0ffb4b5d369dbd72af278897cbd2c3396ddb64d8b3ba53360073be5af4f96af988e8fe56f8bf85f661e15b709fdc7034522adefb2e8200e836d1fc193a
> commons-cli-1.6.0-sources.jar=8ed0a9ce0e0064c3da1027b4615c918ad81d440fcea87e41e6461d178bed43bbdd2908876d004ffdb393df6fd0d4bfc12a5a8b3e0fdf48b47d9c96571d11895b
> commons-cli-1.6.0-src.tar.gz=029088e7c51b657a0be5478685e1f689d6d39357957b3b8813ef6b315b4676ba4bd17b739dc15e09a30f8abfbe22e169c1c629f662477821adf0aa66474e1812
> commons-cli-1.6.0-src.zip=c98b917e89bc4023e36f2bb8585f4c62b01a82f2937167a34c12d40b65a0870269a38109e896e4eefef58cdc3f3e821def8ef524a0c267051c67da84975d
> commons-cli-1.6.0-test-sources.jar=09b72e7050592e8d34caf7d08679011421f4bc90a9d8fc9f83d0e7629e4e7fb730f765cba8bae9bf048e9f3be806f9fa3a74423ff8982caa08048d71861dd410
> commons-cli-1.6.0-tests.jar=89b2211fdfa912db46814ed0df7c39a88a6a2a233009684dfb0344ea16b5a28b5fcf13342fbe2ea3a802050f4b591e05f25f7b96bbbfebb16d2ab038cf2f713a
> commons-cli_commons-cli-1.6.0.spdx.json=9abdae007fa94496c92deb2bcc203f0814692f1de741f5961c5fe3015d6274ea51a508f26ea79913d8fed4746c0eda1a6dfc1405e8056544847177b5ffa74c4f
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: /usr/local/Cellar/maven/3.9.5/libexec
> Java version: 21, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk/21/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.5.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.6.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.5.0):
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.6.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-cli.git --branch
> 

Re: [VOTE] Release Apache Commons IO 2.15.0 based on RC1

2023-10-25 Thread Rob Tompkins
+1 - all looks appropriate, signatures, site, builds, RELEASE-NOTES.txt,

Thank you again Gary and team for all the hard work!

> On Oct 25, 2023, at 5:45 AM, Gary Gregory  wrote:
> 
> My +1. More reviews please 
> 
> Gary
> 
> On Sat, Oct 21, 2023, 7:34 PM Bruno Kinoshita 
> wrote:
> 
>> [x] +1 Release these artifacts
>> 
>> Site reports look OK, checked some files in dist area, building fine on
>> Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
>> Maven home: /opt/apache-maven-3.8.5
>> Java version: 17.0.8.1, vendor: Private Build, runtime:
>> /usr/lib/jvm/java-17-openjdk-amd64
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "5.15.0-86-generic", arch: "amd64", family:
>> "unix"
>> 
>> Thanks
>> 
>> On Sun, 22 Oct 2023 at 00:17, Gary Gregory  wrote:
>> 
>>> Yeah, I saw that on the site and simplified it, but I missed the release
>>> notes, we can pretty up the text post release. Certainly not a blocker
>> IMO.
>>> 
>>> Gary
>>> 
>>> On Sat, Oct 21, 2023, 4:43 PM Elliotte Rusty Harold 
>>> wrote:
>>> 
 One nit. In the release notes I see this:
 
 Commons IO 2.9.0 requires Java 8.
 Commons IO 2.8.0 requires Java 8.
 Commons IO 2.7 requires Java 8.
 Commons IO 2.6 requires Java 7.
 Commons IO 2.5 requires Java 6.
 Commons IO 2.4 requires Java 6.
 Commons IO 2.3 requires Java 6.
 Commons IO 2.2 requires Java 5.
 Commons IO 1.4 requires Java 1.3.
 
 I'm not sure why this is there at all, but if it should be it perhaps
 needs 2.10 through 2.14 as well. Or perhaps just remove this section
 completely.
 
 
 On Sat, Oct 21, 2023 at 7:12 PM Gary Gregory 
 wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons IO 2.14.0 was released, so I would like to release Apache
> Commons IO 2.15.0.
> 
> Apache Commons IO 2.15.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/io/2.15.0-RC1
>> (svn
> revision 64652)
> 
> The Git tag commons-io-2.15.0-RC1 commit for this RC is
> 6bb8020d40f1a4b947ff26949843def5d60292d0 which you can browse here:
> 
 
>>> 
>> https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=6bb8020d40f1a4b947ff26949843def5d60292d0
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-io.git
> --branch commons-io-2.15.0-RC1 commons-io-2.15.0-RC1
> 
> Maven artifacts are here:
> 
 
>>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1666/commons-io/commons-io/2.15.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Oct 21 14:59:24 EDT 2023
> 
 
>>> 
>> commons-io-2.15.0-bin.tar.gz=026dc2e2ba6edea920813dff5d8e09a5d4e2af5c91b79096159375731bebfefa38be6c1394e57f0f9cef6969c906472ca25f1fa67a1ca84e8a50e2e33763d683
> 
 
>>> 
>> commons-io-2.15.0-bin.zip=74d3db69f9cd015ae5c0a8fffe4eb2bb08a7bd1091db8d75bb7cda1e520fd690045c05e73cca5792e9589f17f3f98eab0add765d4d5cdc90f1ae6e1ace0fd4ce
> 
 
>>> 
>> commons-io-2.15.0-bom.json=ed58acb14027e9abd66676e0acbfbc3e38d832ba12e97d89479d7b9f1a931b326995e0994c66ced7ed10c890d0e5f0630b09b5814b755e6f059babe254677ab5
> 
 
>>> 
>> commons-io-2.15.0-bom.xml=2ac587fc41277f159aa2f70dc8cfd41889dc8e2cdd570540918c186b7b71be1187eae2f034352888015beea5a5058917743921e71374e9a564e29c9cc66b1b73
> 
 
>>> 
>> commons-io-2.15.0-javadoc.jar=3f214472b9d579827a23b498de30d21afe577c59bbfae668d4f42fd9419c2d341499e66bd38cbba074be72f79671dbcb30f2b151d397e90489c4a98b456cc049
> 
 
>>> 
>> commons-io-2.15.0-sources.jar=89a37db267284ba002c6cf2d570b76359f684c354e5b605c94d602f4e3f510264fb05ff2e890362ac13211164933cc640f051c9e49475156e22a833212ec505c
> 
 
>>> 
>> commons-io-2.15.0-src.tar.gz=a8df05b8da8f39408473588a8f4672dee8f4215e50e1001c0132f9bd046b32f5816f2939db471d21578e6748a5f8a998337e3adbc6dbada798d64c39ff1370d0
> 
 
>>> 
>> commons-io-2.15.0-src.zip=4d600f130dbcee703620b7916b6a34ebb36d4ec71ae00da1a1339976cec9bdcea936386b31ac7dcf2e225ac6e0ae1a13bbad0f0ea78bac4dbe4a68a73d347c8b
> 
 
>>> 
>> commons-io-2.15.0-test-sources.jar=5fab0e764cfba8165d4e608e89cee40702cd43739b23f9a5f6c86ecd78fde98f403755e362de2cdefb5ce3ab24ee4f9e049200b76bc365228bd1d5c6d850ab11
> 
 
>>> 
>> commons-io-2.15.0-tests.jar=3e402eeed7ef3093bd75deda30a41cd1a811bf2a95f974a37c4fde114234966298b69b0503ce260e25f66560828668449f7a0d0e2c885e4e5134dcac6492c37e
> 
 
>>> 
>> commons-io_commons-io-2.15.0.spdx.json=606503b5c9d7a9d865ebfea7edf9e4420c580254f47e69cf012089bf934b39bf6e99c74904693c566e0cec994d487cc0bc06d5114f5fa13eb1f38bd0e66f11d2
> 
> I have tested this with
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package
>> site
 deploy
> 
> Using:
> 
> Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> Maven home: 

Re: [DISCUSS] - Move commons-chain to dormant?

2023-10-22 Thread Rob Tompkins
+1

> On Oct 21, 2023, at 7:46 PM, Gary Gregory  wrote:
> 
> Seems reasonable to me.
> 
> Gary
> 
> On Sat, Oct 21, 2023, 6:49 PM sebb  wrote:
> 
>> Reviving this thread.
>> 
>> I think we should now change chain to dormant.
>> 
>> Sebb
>> 
>> On Sun, 8 Oct 2017 at 16:10, Pascal Schumacher 
>> wrote:
>>> 
>>> Looks like Apache Tiles 3 does not use commons-chain.
>>> 
>>> The only mention of commons-chain I could find in
>>> https://github.com/apache/tiles/tree/trunk was an exclusion a of
>>> transitive commons-chain dependency.
>>> 
>>> https://tiles.apache.org/framework/tiles-compat/dependencies.html also
>>> does not list commons-chain.
>>> 
>>> Looks like the most popular project depending on commons-chain was
>>> Struts (but only till 1.3.x (last released in 2008)).
>>> 
>>> According to
>>> 
>> https://mvnrepository.com/artifact/commons-chain/commons-chain/1.2/usages
>>> "Magnolia" and "eXo JCR" are the most popular projects using
>> commons-chain.
>>> 
>>> -Pascal
>>> 
>>> Am 08.10.2017 um 16:48 schrieb Rob Tompkins:
>>>> What’s the largest project that depends upon it? Apache “Tiles” seems
>> to.
>>>> 
>>>> -Rob
>>>> 
>>>>> On Oct 8, 2017, at 9:44 AM, Benedikt Ritter 
>> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> Am 07.10.2017 um 12:35 schrieb Pascal Schumacher <
>> pascalschumac...@gmx.net>:
>>>>>> 
>>>>>> Hello everybody,
>>>>>> 
>>>>>> the last commons-chain release is from 2008.
>>>>>> 
>>>>>> The last bugfix/feature commits are from 2013.
>>>>>> 
>>>>>> Since 2013 only one bugfix/feature released issue was created in
>> JIRA.
>>>>>> 
>>>>>> Maybe it is time to move the component to dormant?
>>>>>> 
>>>>>> What do you think?
>>>>> We had somebody asking for the component a few weeks ago, but that is
>> everything that has happened in ages. So +1
>>>>> 
>>>>>> -Pascal
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> -
>>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>>> 
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>> 
>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE][LAZY] Release Apache Commons Parent 63 based on RC1

2023-10-01 Thread Rob Tompkins
If gary cancel’s the vote I can do that work. Will try to sort it out this week.

-Rob

> On Oct 1, 2023, at 9:20 AM, sebb  wrote:
> 
> Ideally we want to release a version with the updated site.xml...
> 
> On Sat, 30 Sept 2023 at 18:44, Gary Gregory  wrote:
>> 
>> We have added some enhancements since Apache Commons Parent 62 was
>> released, so I would like to release Apache Commons Parent 63.
>> 
>> Apache Commons Parent 63 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1
>> (svn revision 64275)
>> 
>> The Git tag commons-parent-63-RC1 commit for this RC is
>> 0fd27a2962b49dce17e6825d3d0a3f9d506164cd which you can browse here:
>>
>> https://gitbox.apache.org/repos/asf?p=commons-parent.git;a=commit;h=0fd27a2962b49dce17e6825d3d0a3f9d506164cd
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-parent.git
>> --branch commons-parent-63-RC1 commons-parent-63-RC1
>> 
>> Maven artifacts are here:
>>
>> https://repository.apache.org/content/repositories/orgapachecommons-1660/org/apache/commons/commons-parent/63/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sat Sep 30 13:31:17 EDT 2023
>> commons-parent-63-src.tar.gz=849823362a097cae5c3d6dd3be6a0369145da6a7a9a9ffaaac67bc0f4dd68c547a0b060055e5056e138d92aa029d84a0730c709797ac4392902fa5933059febb
>> org.apache.commons_commons-parent-63.spdx.json=7dd6414048549199d30dae095c65d1c42f783e622561451544453f8dae08a61121549edc4049019c475b2192e36b5377e81f89df9d9d6fc70bb43130c6c377d9
>> commons-parent-63-site.xml=c6aea4f2c03920366bee23b08b046dacc09710e92c78ccd83f47cd92f89bc53abc3b8bbc7f44017ee94a2cb022ce763fe3f7d8c9aa42d571350269ba6568ca07
>> commons-parent-63-src.zip=c074bfa5526f5d0eaa8f631fa8e04798d97dcb07336d3f094f70b87d4917181f540c47145f77acfe6e78d32317312b90358984226f7a21b4255846180acb9011
>> commons-parent-63-bom.json=d08fbea2168dcd027d6c2928c3604f22b081d4d88fd480f1f2b282c3ac32a15f312e47e72ad0d0f525680e931d311fe51472e9b6450e2bde5ee1a3f4632aaad2
>> commons-parent-63-bom.xml=36d3cb1aed436d44fbb97ef16e1e603196598dea68cc113ebfe630c7044a214132c6e7444f32f4e90ba8bf5d47f357d3426afa37b4ea6a8e735ddd666e8d0744
>> 
>> I have tested this with
>> 
>> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
>> 
>> using:
>> 
>> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
>> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
>> Java version: 17.0.8.1, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "14.0", arch: "x86_64", family: "mac"
>> Darwin gdg-mac-mini.local 23.0.0 Darwin Kernel Version 23.0.0: Fri Sep
>> 15 14:42:42 PDT 2023; root:xnu-10002.1.13~1/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 62 are in the release notes:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/RELEASE-NOTES.txt
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/changes-report.html
>> 
>> Site:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/index.html
>>(note some *relative* links are broken and the 63 directories are
>> not yet created - these will be OK once the site is deployed.)
>> 
>> RAT Report:
>>
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/site/rat-report.html
>> 
>> KEYS:
>>  https://downloads.apache.org/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,
>> 
>> garydgregory,
>> Release Manager (using key DEADBEEF)
>> 
>> 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.
>> 
>> 1a) Clone and checkout the RC tag
>> 
>> git clone https://gitbox.apache.org/repos/asf/commons-parent.git
>> --branch commons-parent-63-RC1 commons-parent-63-RC1
>> cd commons-parent-63-RC1
>> 
>> 1b) Download and unpack the source archive from:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/commons-parent/63-RC1/source
>> 
>> 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 

Re: [site] [all] broken links

2023-10-01 Thread Rob Tompkins
Will look at this and write jira for it.
-Rob

> On Oct 1, 2023, at 4:52 AM, sebb  wrote:
> 
> As to the other sites, there should be no need to regenerate them: one
> can just update the production sites in SVN.
> I should be able to do that a bit later.
> 
>> On Sun, 1 Oct 2023 at 09:41, sebb  wrote:
>> 
>> Looks like the site-relative links in
>> https://github.com/apache/commons-parent/blob/master/src/site/site.xml
>> are not working.
>> 
>> Try changing the links to absolute ones.
>> 
>>> On Sun, 1 Oct 2023 at 01:40, Phil Steitz  wrote:
>>> 
>>> I am not sure what is causing this, but somehow the links generated for
>>> component sites with the current parent and plugins are messed up in the
>>> General Information section (which appears on some sites and not others).
>>> In verifying the updated [pool] site, I see that for some reason the links
>>> for "site publication" and the "commons release plugin" are broken.  I
>>> notice that io, dbcp and lang all have the same problem.  At first, I
>>> thought it was due to the use of relative links in the main site nav
>>> entries, but others in the same block work correctly.  Any ideas on how to
>>> fix this?
>>> 
>>> Phil
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [ANNOUNCEMENT] Apache Commons IO 2.14.0

2023-09-30 Thread Rob Tompkins
Thank you for your work!

-Rob

> On Sep 30, 2023, at 10:31 AM, Gary Gregory  wrote:
> 
> The Apache Commons team is pleased to announce the release of Apache
> Commons IO 2.14.0.
> 
> Commons IO is a package of Java utility classes like java.io. Classes
> in this package are considered to be so standard and of such high
> reuse as to justify existence in java.io.
> 
> The Apache Commons IO library contains utility classes, stream
> implementations, file filters, file comparators, endian transformation
> classes, and much more.
> 
> Java 8 is required.
> 
> Historical list of changes:
> https://commons.apache.org/proper/commons-io/changes-report.html
> 
> For complete information on Apache Commons IO, including instructions
> on how to submit bug reports, patches, or suggestions for improvement,
> see the Apache Commons IO website:
> 
> https://commons.apache.org/proper/commons-io/
> 
> Download page: https://commons.apache.org/proper/commons-io/download_io.cgi
> 
> Have fun!
> Gary Gregory
> - Apache Commons Team
> 
> -
> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
> For additional commands, e-mail: user-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons Pool 2.12.0 based on RC5

2023-09-27 Thread Rob Tompkins
+1 - looks good to me



> On Sep 27, 2023, at 7:03 AM, Bruno Kinoshita  wrote:
> 
>   [X] +1 Release these artifacts
> 
> The website change page date needs to be updated for the latest release,
> but that can be done after the release.
> 
> On Tue, 26 Sept 2023 at 21:51, Phil Steitz  wrote:
> 
>> We have fixed quite a few bugs and added some significant enhancements
>> since Apache Commons Pool 2.11.1 was released, so I would like to release
>> Apache Commons Pool 2.12.0.
>> 
>> Apache Commons Pool 2.12.0 RC5 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC5 (svn
>> revision 64211)
>> 
>> The Git tag commons-pool-2.12.0-RC5 commit for this RC is
>> commons-pool-1.12.0-RC5 which you can browse here:
>> 
>> https://github.com/apache/commons-pool/releases/tag/commons-pool-2.12.0-RC5
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-pool.git
>> --branch
>> commons-pool-2.12.0-RC5 commons-pool-2.12.0-RC5
>> 
>> Maven artifacts are here:
>> 
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1659/org/apache/commons/commons-pool2/2.12.0/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Tue Sep 26 11:50:36 MST 2023
>> 
>> commons-pool2-2.12.0-bom.xml=46f6d5da5c530b482bf3d23d53c337f28507d9d27b5f4ef56dc3523fe27c24833de0e05d20460a1c0b77dd5569f1d1207e9d95bbf5332ae103503abf00a0bdfb
>> 
>> commons-pool2-2.12.0-bin.zip=08ea2579002276e6e5ff576bd3cfc1b4b29e1ecd471c6a38b263f57c9a887a158eee62a6ff3093e6017cb947409194dd1d7a9d681ae32588eb241404da3796e0
>> 
>> commons-pool2-2.12.0-tests.jar=697ac4c33eca5067dedfbc6b7f656aa230ba71908aed6450ca49a0419aad0f588bd0a238c9e7198999265b79c7fab2e760f3575bdad7ff13109ef2aaf72c36a4
>> 
>> commons-pool2-2.12.0-sources.jar=470d45652b9c63e92feb26c517edfd324878214a87faeee79e70772fd6ead1553aaa362b209dc1cb950cc144004223b186e142810a72be0caa839e87446999b6
>> 
>> commons-pool2-2.12.0-src.zip=c09424e2a6209adf0e1660de421c35c3b80c395a5d4ef30e6ff58c499b5768cde15e508f858dffc0dfde1c9a3d18d5d7681d67ca5c796d99e5922c712889e195
>> 
>> commons-pool2-2.12.0-bom.json=f2ac923db32811d691c304ab8425fff757ebe3102cbacafad7244dc3f5d742e1376ba7fb906b177a626dd766f49baa2da977efb260e3d66aa8dd8b3034954276
>> 
>> org.apache.commons_commons-pool2-2.12.0.spdx.json=2e8e3f1f2aa69abc7c49b0487960159cf6690e5de4ad74706c47e00f55479490b7ed31a478b82f6b51c94ef23501fc8850432d00d7364180bba5486d63cd33bc
>> 
>> commons-pool2-2.12.0-src.tar.gz=fefb22459519b92712a9e5178099d19cc7fc8a5b07f633387c11f5b30d86ae8f73e237728be08a2705cf56f986be5a51c11a084b01224e5a0c9ccf7b34dc6258
>> 
>> commons-pool2-2.12.0-javadoc.jar=a4b3df904311892327d210f0c507b4c9cba1e2289071a87d873ea72f60052a5658728f6412715c6e1cb0528f8df15cd9c74fe20d173b17cc887120048334a119
>> 
>> commons-pool2-2.12.0-test-sources.jar=b93d6529527029f26aa51bf451e2c0250e5e20c7c884b51d2c1377d3e58c218679ba56f87e10bd1062fbc87bb8db3a2bfe98c5b54910566a57260ab77f530482
>> 
>> commons-pool2-2.12.0-bin.tar.gz=3d75b997287df339acfd76662cf6e4b645b10fff825bffc58dd2238dbaaccf7b81c61aa59ada6f667a3f29d9db0730e34b25526f7d309db36361e4d1e8c6ec70
>> 
>> I have tested the build of this release candidate with
>> 
>> mvn clean package site
>> under
>> openjdk version "17.0.8.1" 2023-08-24
>> OpenJDK Runtime Environment (build 17.0.8.1+1-Ubuntu-0ubuntu120.04)
>> OpenJDK 64-Bit Server VM (build 17.0.8.1+1-Ubuntu-0ubuntu120.04, mixed
>> mode, sharing)
>> 
>> openjdk version "11.0.20.1" 2023-08-24
>> OpenJDK Runtime Environment (build 11.0.20.1+1-post-Ubuntu-0ubuntu120.04)
>> OpenJDK 64-Bit Server VM (build 11.0.20.1+1-post-Ubuntu-0ubuntu120.04,
>> mixed mode, sharing)
>> 
>> openjdk version "1.8.0_382"
>> OpenJDK Runtime Environment (build 1.8.0_382-8u382-ga-1~20.04.1-b05)
>> OpenJDK 64-Bit Server VM (build 25.382-b05, mixed mode)
>> 
>> Using
>> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
>> Linux 5.15.0-83-generic #92~20.04.1-Ubuntu SMP
>> 
>> And
>> openjdk version "20.0.1" 2023-04-18
>> OpenJDK Runtime Environment Homebrew (build 20.0.1)
>> OpenJDK 64-Bit Server VM Homebrew (build 20.0.1, mixed mode, sharing)
>> Darwin Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023;
>> root:xnu-8796.141.3~6/RELEASE_X86_64
>> 
>> I have also tested the compiled jar against DBCP 2.10 and run soak and
>> performance tests using Commons Performance.  Performance was not
>> significantly different from earlier 2.x versions for the tested workloads.
>> 
>> Details of changes since 2.11.1 are in the release notes:
>> 
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC5/RELEASE-NOTES.txt
>> 
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC5/site/changes-report.html
>> 
>> Site:
>> 
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.12.0-RC5/site/index.html
>>(note some *relative* links are broken and the 2.12.0 directories are
>> not yet created - these will be OK once the site is deployed.)
>> 
>> JApiCmp Report 

Re: [VOTE] Release Apache Commons IO 2.14.0 based on RC1

2023-09-26 Thread Rob Tompkins
+1

Builds successfully on all LTE java versions
Reports look good,
Rat Looks good,
Signatures all check out.

Cheers,
-ROb :-p

> On Sep 26, 2023, at 12:37 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons IO 2.13.0 was released, so I would like to release Apache
> Commons IO 2.14.0.
> 
> Apache Commons IO 2.14.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/io/2.14.0-RC1 (svn
> revision 64208)
> 
> The Git tag commons-io-2.14.0-RC1 commit for this RC is
> 82250a879112e9b58c58d289e166d66942d77341 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=82250a879112e9b58c58d289e166d66942d77341
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-io.git
> --branch commons-io-2.14.0-RC1 commons-io-2.14.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1657/commons-io/commons-io/2.14.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Mon Sep 25 06:51:48 EDT 2023
> commons-io-2.14.0-sources.jar=cb32b6c6b6c875633103e248c7998c8a0082c0c4d476688897a16549573b4d53e63fec4255f100521f265bf58b16cb4f4b7e09f4ce4b2f086eb13a15b9cce539
> commons-io-2.14.0-bin.zip=f80efb25e30d89fe9ea26fc85baa3666c1c69c3bcdda6d566e9e95d1c627c52a16582ed48f13a06bf4d89e49e14dc1f19608f32e6dbaecd66725acc2d58d720d
> commons-io-2.14.0-src.tar.gz=f96568e55dec789661c02a1f9455bf30eece5b621f99258385112d39aded37b1ec3dea93275d3ccaed9590e9cf95ae4958ef9d028db4275900180e269c9db970
> commons-io-2.14.0-src.zip=d6a469218279bb9be92caa43eaf49478ecc5d90056677c504c2d16f2f44677baf0929c01c2c096d18b99158d641ef5a6dcba44b88076db0f062746afa684ca5d
> commons-io-2.14.0-bom.json=9eb19600b17cfaa68d0e52f1986f09802f8bfea7a031eff536249fcca18e47bc25144b60187158ef0e8f80adeae4ae8c9b10925b6995b1e0191aa76ecf550e7a
> commons-io-2.14.0-tests.jar=4692a6fc8b11b8c0f60b0896cdc1a3a8bb5f0710e8a47c4589aa0bffe683b31fb512743af03ac699f639c2bb55342bd6c833c5dac52dcf6b0f68a8e3e9ff1d21
> commons-io-2.14.0-test-sources.jar=ccefebb9113638343d15e05f1e25442e4cbc201ae8c6b07bc52c1ba3cdb069fda98418aa6f2731895012b76cc0fa21eb4599220dd6c9d4f9386c8b1fc27e99d3
> commons-io_commons-io-2.14.0.spdx.json=1e509681b8e883ed500ba2c349fed3d3527e6a69101fa0f7b305e5b2f4b12bcbe67869dbefc5e26d66875b6161fab8a2747a87c553e40da1902e9ed1b6e306e8
> commons-io-2.14.0-bin.tar.gz=a15eb43dede3c82895fe0411963ce2ba7b75716378dd93aa02f68f909f8777fdba8d738d7f895e7c4d6931bf0bba18fd409b5f6c7e0f02452047ac71f8dba313
> commons-io-2.14.0-javadoc.jar=24ed778593714a8eb200d2daa235ca755f9c8cf06d8b1c0b164df72049b1706d3827bf9ba772297334aa3ff1833f6257249c1bcdb66e4e9e3f6874cd58a1e212
> commons-io-2.14.0-bom.xml=256580d4b1ef0d6fce4d9379e87d62a05ca1f954abd6864406023800b5679067f50c33d8139dd830a55b016abffa6d8cba97d4f7bb06bae1f4a0307c0fec046a
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> Java version: 17.0.8.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.5.2", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul
> 5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 2.13.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.14.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.14.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.14.0-RC1/site/index.html
>(note some *relative* links are broken and the 2.14.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/io/2.14.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
> commons-io-2.14.0-RC1 commons-io-2.14.0-RC1
> cd commons-io-2.14.0-RC1
> 
> 

Re: No sign of releases for Functor or OGNL - move to dormant?

2023-09-20 Thread Rob Tompkins



> On Sep 20, 2023, at 10:55 AM, Bruno Kinoshita  wrote:
> 
> +1 for functor to be made dormant. Never got enough time to work on it,
> and we can move it out later if I need to.
> 

+1 for functor to be made dormant too.

Cheers,
-Rob

> Not sure about OGNL.
> 
> Cheers
> 
> Bruno
> 
> On Wed, 20 Sept 2023, 11:52 sebb,  wrote:
> 
>> I cannot find any releases for Functor or OGNL, yet they are listed on
>> the commons home page, and the releases page.
>> 
>> Seems to me they should be moved to dormant?
>> 
>> Sebb
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons JCS 3.2 based on rc1 (2nd round with fixed links)

2023-09-16 Thread Rob Tompkins
+1
Signatures validate properly
Build works appropriately on java 8, 11, and 17
Reports all look appropriate, RAT (licenses), japicmp (backwards 
compatibility), and soptbugs
Nit (major, non-blocking). No site built for commons-jcs: Apache Commons 
Distribution or for JCache, OpenJPA

Thanks for all the hard work!!!, pardon that I havent rolled a release 
candidate for a while.
-Rob

> On Sep 3, 2023, at 11:51 AM, Thomas Vandahl  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons JCS 3.1 was released, so I would like to release Apache 
> Commons JCS 3.2.
> 
> Apache Commons JCS 3.2 rc1 is available for review here:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1 (svn revision 
> 63581)
> 
> The Git tag commons-jcs3-3.2-rc1 commit for this RC is 
> 6ff84134fa295b608531f9655f075ea58635cd57 which you can browse here:
>  
> https://gitbox.apache.org/repos/asf?p=commons-jcs.git;a=commit;h=6ff84134fa295b608531f9655f075ea58635cd57
> 
> You may checkout this tag using:
>   git clone https://gitbox.apache.org/repos/asf/commons-jcs.git --branch 
> commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
> 
> Maven artifacts are here:
>   
> https://repository.apache.org/content/repositories/orgapachecommons-1650/org/apache/commons/commons-jcs3/3.2/
> 
> These are the release artifacts and their hashes:
> 
> 6fb8c140c49229339ccea583c462e20b5f2abfd13b3615f466e5b7e44abfbfa7f662ce25b54edcf433c2b7010e4b32c2cde09f2da7754d7f697e871b76f61c91
>   commons-jcs3-dist-3.2-bin.tar.gz
> 6d2c47f3e41a6fca3fa94dd423d8e9c4bc76929778d5d44ee094a2d8465f1449feffee24ee1248e80baaec8e2c08051ff3fdcae76610591b451e796904f5dd46
>   commons-jcs3-dist-3.2-bin.zip
> 16c8bb7abe9268a39b80ce03a57adf1ac596191e4aee80756443d1861b850ffe5b67f6fbd9d46f1189d4247b7b928192cb7fb28f45e8bc768317972276acac9a
>   commons-jcs3-dist-3.2-src.tar.gz
> 1f78fdc0be26f0b8b350ef2623191a28e13131b6a98abc51927aada192b7b381d1d7264a2083f23a72bf0906a0e4164e0c2a5aee11c3448408399cc87f0b912e
>   commons-jcs3-dist-3.2-src.zip
> 
> I have tested this with ***'mvn clean install site site:stage'*** using:
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Java version: 1.8.0_311, vendor: Oracle Corporation, runtime: 
> /Library/Java/JavaVirtualMachines/jdk1.8.0_311.jdk/Contents/Home/jre
> Default locale: de_DE, platform encoding: UTF-8
> OS name: "mac os x", version: "10.16", arch: "x86_64", family: "mac"
> 
> Details of changes since 3.1 are in the release notes:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/RELEASE-NOTES.txt
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/changes-report.html
> 
> Site:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/index.html
>   (note some *relative* links are broken and the 3.2 directories are not yet 
> created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.1):
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-rc1/site/commons-jcs3-core/japicmp.html
> 
>   ***
>   Note that the above report notes several errors.
>   These are considered OK for the reasons stated below.
>   These exceptions are also noted in the Changes and Release Notes.
> 
>   Errors reported:
>   - methods added to interface: OK because that does not affect binary 
> compatibility.
>   - annotation @Deprecated added to classes
>   ***
> 
> RAT Report:
>   
> https://dist.apache.org/repos/dist/dev/commons/jcs/3.2-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,
> 
> Thomas Vandahl (tv),
> Release Manager (using key 88817402)
> 
> 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-jcs.git --branch 
> commons-jcs3-3.2-rc1 commons-jcs3-3.2-rc1
> cd commons-jcs3-3.2-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
> 
> 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
> 
> 

Re: JCS vote

2023-09-15 Thread Rob Tompkins
Thank you for that reminder, I will get to it today.

-Rob

> On Sep 15, 2023, at 2:24 AM, Thomas Vandahl  wrote:
> 
> Hi folks,
> 
> Could some kind soul please find some time to vote on the release 3.2 of JCS?
> Perhaps this weekend? 
> 
> We would need one more PMC vote.
> 
> Thank you!
> Bye, Thomas 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons DbUtils 1.8.1 based on RC1

2023-09-09 Thread Rob Tompkins
Builds on java 8,11, 17
signatures good
Rat good
all other reports good.

+1

> On Sep 9, 2023, at 8:46 AM, Gary Gregory  wrote:
> 
> We have fixed one (Java JPMS >= 9) bug since Apache Commons DbUtils
> 1.8.0 was released, so I would like to release Apache Commons DbUtils
> 1.8.1.
> 
> Apache Commons DbUtils 1.8.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.1-RC1
> (svn revision 63886)
> 
> The Git tag commons-dbutils-1.8.1-RC1 commit for this RC is
> 0b30ed1bddfa07bfda44122fc52ccd0e49fb6006 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=commit;h=0b30ed1bddfa07bfda44122fc52ccd0e49fb6006
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-dbutils.git
> --branch commons-dbutils-1.8.1-RC1 commons-dbutils-1.8.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1655/commons-dbutils/commons-dbutils/1.8.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Sep 09 08:40:12 EDT 2023
> commons-dbutils-1.8.1-src.tar.gz=dca3c72a7601d8d97886513c13f7bfb132711b05ecff7c9e17d9e9169da55dc24d87d8d491e08cf210b9580fd73db0213f307ce08a09136d279f4cc39d3f303e
> commons-dbutils-1.8.1-test-sources.jar=c52dd3a7c5fa1757c04244b780f4ce6882ea9d2592956a2902f6e88e5af824fb70e5d0e3cc42e89e4597641beda4b9c8fa558abe3644ddab146d5bd997a2618e
> commons-dbutils-1.8.1-javadoc.jar=1a6ff00095bff09fdba43c50e5a8ae70feaf0a7dc1b8e9a6194596b775b2cd10c55504dfcb330a2004db692efe685bc462caec7372d27df23608ce71fe477d78
> commons-dbutils-1.8.1-tests.jar=dabaac62f735cbc9c4ae4d72bd7ffcc435a5f9e01baf4cbf2b4f639d0fcbd3892fceb8e0974605bb8d700ae764c77c16fb198f10cedd405b05169a2957066083
> commons-dbutils-1.8.1-src.zip=ff5eea293a6c8db1350d2ac24cad68c77f8bfcc2e2f5ddabd42a46167bb8f9e7d2917f8449207bb049fe2035324531029ec5ed9895b9587b3a1da1039bd6
> commons-dbutils-1.8.1-bom.json=d23f12585120e122476a70e3163c8034b87e8a2e3e3bfbb8294bc9d5a0f7512c394cc30c07053cb86a1bc6844d4548fb6d967898bc58c6e86eb73018726c8bc1
> commons-dbutils-1.8.1-bin.tar.gz=458dbca14ef7dbb034dcc01ed806bb4fa6fbf772b3bec7edfb1c530c0239cac9662a9733208ab68e4d3e436efd06bf9b97344595476c855637db2fae22992813
> commons-dbutils-1.8.1-bin.zip=91a6bb68ae6601759b01848430ae0a9e1b8343980eeef5e2cf94e51c91aedbd90a4efd3aa898525fe6cec97ec10d8b315d1be32be51e11ea897d83a14458a2d7
> commons-dbutils_commons-dbutils-1.8.1.spdx.json=c03b89c24e6e34a23b78fd651714292ef6efd6ad76a483aaeeae66aa362e9dcf5f1d22bc4f36b4c5acf09a6fe0ebd9fa6deceac28baba8aaa4a407daff50d0c4
> commons-dbutils-1.8.1-sources.jar=6b383531b6b4dd71b5871d39eaa975bb28e65b0f4d0def0e7ffdea4a6b0b7420381145a8ae29206ab56353c1014ab48f94051038224dcf9750e51c4a630e2fab
> commons-dbutils-1.8.1-bom.xml=f3d472aeadf54d85d42271c1d7ade15a5b4bcc4acfa3b3facecbf2d42f002105ff8d2eac73121d52e3e97f603082162676f7a9a258b46baa8749c4283b680cb7
> 
> 
> I have tested this with 'mvn' using:
> 
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> Java version: 17.0.8.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@17/17.0.8.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.5.1", arch: "x86_64", family: "mac"
> Darwin  22.6.0 Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56
> PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.8.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.1-RC1/site/index.html
>(note some *relative* links are broken and the 1.8.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.8.0):
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.1-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone https://gitbox.apache.org/repos/asf/commons-dbutils.git

Re: [VOTE] Release Apache Commons Compress 1.24.0 based on RC1

2023-09-08 Thread Rob Tompkins
+1
Build works on java 11, 17,
Signatures all check out,
Reports all look good.

Cheers, and thanks a ton for all the good work!
-Rob

> On Sep 4, 2023, at 9:22 AM,Gary Gregory  wrote:
> 
> We have fixed a few bugs and added one enhancement since Apache
> Commons Compress 1.23.0 was released, so I would like to release
> Apache Commons Compress 1.24.0.
> 
> Apache Commons Compress 1.24.0 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/1.24.0-RC1
> (svn revision 63776)
> 
> The Git tag commons-compress-1.24.0-RC1 commit for this RC is
> e52eabe9c0eb47b436e873ad7cb83fe737164dec which you can browse here:
> https://gitbox.apache.org/repos/asf?p=commons-compress.git;a=commit;h=e52eabe9c0eb47b436e873ad7cb83fe737164dec
> You may checkout this tag using:
> git clone https://gitbox.apache.org/repos/asf/commons-compress.git
> --branch commons-compress-1.24.0-RC1 commons-compress-1.24.0-RC1
> 
> Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapachecommons-1654/org/apache/commons/commons-compress/1.24.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Mon Sep 04 08:42:46 EDT 2023
> commons-compress-1.24.0-sources.jar=fb6200ff81f7d5f7a511c3974d741afffb330388c438f453c976a1bcbcf0b5c76b97f6eebc79e8911e2b3dd0330b17f09fa6fd5e9963266dcf8b606cba0c8dce
> commons-compress-1.24.0-src.tar.gz=32770f999edcd598606a1c865db699bbc42711dbd69738fb2cd67faef1dcdd00247d3d5b489bf890e5d8475e31e1b8714823be836fd6a26c561eb9958d3a99dc
> org.apache.commons_commons-compress-1.24.0.spdx.json=bea3c1c1108a602627986ed7ee8d65541668a617515ac930251f67456c11e757f9a629f9882f5767c60bc86e90c5207a08d11e2f54b3b92097a867edc1edf059
> commons-compress-1.24.0-bom.json=476222df412eba639db44a9ba40a0852ec6ff532ed3aff131dae0037259d443f6b453d400bef5cc8f14cbfb961cd031ced96b593c3f86f4b0f14c3f5517cae07
> commons-compress-1.24.0-test-sources.jar=1dbac8e9018fc14fa4bca67a793790b2605a2a12d3d4193160e7129d7b4b77698ac37fe103a3fa1aed6cb1902c1cb63160fd7fc99f093f858a8b8293b777ea5c
> commons-compress-1.24.0-tests.jar=589303cad91f325f6188b9b960a00435564367d48d3181bbfa6b9f308ef9905acd5102a400cf4f4442d647ccf2be606ccd4ef6da4f17e0165283cd30fb71683f
> commons-compress-1.24.0-src.zip=f5d71fd4f74d2cd19d4c2636f984b58bd3eb397597fa6d2adcd3fcb888702f66ba952e617a1f8375b9e7db8a5c77ede98c01a263df65cea9e5565d9c11e65c5f
> commons-compress-1.24.0-bom.xml=b0abb60259a7a28093a981dc5c8da4b405e3c501307a64ea4878d42cbdbe377fd5a5aa965ec405aabd7c256609abb2802c05767470ca9290adc91166696b2677
> commons-compress-1.24.0-bin.tar.gz=dfd9faf6f1d2606cb7f2c870b88800d87435af6a442603aecbd4910b4f66424aabfdbcbac7440a5a5ea1178871dcc22cdee08bd6da83fe012a47f1f20a96bf99
> commons-compress-1.24.0-bin.zip=9504860208d9ffdd45387ccbdc6804115de57676e1cc3313b2ea72186c1e5c90a6c32c0a9fe160436bb87fbec8b6085790a4f18b9d4327600e0cfaf065ffbdc3
> commons-compress-1.24.0-javadoc.jar=dd320dca23f2352d0a08b7c771ca96b874b2a1669c15aed1d00568d27c5d597329d82e3b23b9f449c5ee584c76492d95a4d8f61fb0ccaf19761b292486328335
> 
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> Java version: 11.0.20.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.20.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.5.1", arch: "x86_64", family: "mac"
> Darwin  22.6.0 Darwin Kernel Version 22.6.0: Wed Jul 5 22:21:56
> PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.23.0 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/compress/1.24.0-RC1/RELEASE-NOTES.txt
> https://dist.apache.org/repos/dist/dev/commons/compress/1.24.0-RC1/site/changes-report.html
> 
> Site:
> https://dist.apache.org/repos/dist/dev/commons/compress/1.24.0-RC1/site/index.html
> (note some *relative* links are broken and the 1.24.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.23.0):
> https://dist.apache.org/repos/dist/dev/commons/compress/1.24.0-RC1/site/japicmp.html
> 
> RAT Report:
> https://dist.apache.org/repos/dist/dev/commons/compress/1.24.0-RC1/site/rat-report.html
> 
> KEYS:
> https://downloads.apache.org/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 

Re: [VOTE] Release Apache Commons DBCP 2.10.0 based on RC1

2023-09-02 Thread Rob Tompkins
+1 signatures good, reports good

mvn clean test package install works

nit mvn site doesn’t work for me on my machine


> On Aug 28, 2023, at 9:34 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons DBCP 2.9.0 was released, so I would like to release Apache
> Commons DBCP 2.10.0.
> 
> Apache Commons DBCP 2.10.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/dbcp/2.10.0-RC1
> (svn revision 63672)
> 
> The Git tag commons-dbcp-2.10.0-RC1 commit for this RC is
> f612e2f0830f459fc5d2a2fa6004e7c8d2ebf03f which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-dbcp.git;a=commit;h=f612e2f0830f459fc5d2a2fa6004e7c8d2ebf03f
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-dbcp.git
> --branch commons-dbcp-2.10.0-RC1 commons-dbcp-2.10.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1652/org/apache/commons/commons-dbcp2/2.10.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Mon Aug 28 09:24:09 EDT 2023
> commons-dbcp2-2.10.0-javadoc.jar=fe6bc24f091f69142a59a414a6a5a9ad10f998cbab4723a108ad84cd5eef392cc838fd172e25d0432aa18fba316f10d8a28eb50e0a60403798529cf760327e56
> commons-dbcp2-2.10.0-test-sources.jar=4a4dffef71d9ff4ad877966ddc6797587f48a87fecbac8d7fda684d26f4c72c3998400df74fabe4cd2143a442c774e6722216e7e0bb00adfd2a3593e0812b3fc
> commons-dbcp2-2.10.0-src.tar.gz=73cc7227b576bb574221509eb6000ebff320a58de4b0efa7360630d0888c7b14eb35b7887310781723417731fedc767c4d011d55eee7bd12810a9cd50296e287
> commons-dbcp2-2.10.0-bom.xml=657ca0014b744ca030c40b4f779752da768c6f4e5075d6505f1c943b0406122a8256582eb08e425302fad58ec411f24353ddd28206e063fbf4ada323985efca2
> commons-dbcp2-2.10.0-bin.tar.gz=e16e9e51eacad44314da770b1f150afab99d887a9c03e37114706aa55ba1b790c5ad0b5de4cc444b777036696c258d102b56b9158907b8e5e21b30edc54cf381
> commons-dbcp2-2.10.0-sources.jar=01f2e5713e3f1c291fc8393639d0ace7e9d7a9ee4784a124a2452fc4fc4ad11ee27f570c0538f484f4038aca893da4e44f9d17bca83b4e7945bb419b31233bb8
> commons-dbcp2-2.10.0-bin.zip=65376d2049bcf0418fc1af456d83c6dd1af738913bb7678f6847a51c84c3aa3630216cef81ce7346f34728a2e54c99c611df3be9dc0994c537d755997c92a177
> commons-dbcp2-2.10.0-tests.jar=e13b9aab48f31e65277afa2c149c9b6f754c2f47b1eca13ab0eb246ce7ef4cb6a267bba4b2a1a2051dd05620f3783cde64a31513b821dfe6276f01f2235b099c
> Apache\ Commons\
> DBCP-2.10.0.spdx.rdf.xml=a8ecf26b2961de5d653a86fe5282772b1bbef41e6c928df3830e34898a10c9afbe444e82fc0950278c8d6889caf909e3d80221994a75eac95c7c44ab6e84decc
> commons-dbcp2-2.10.0-bom.json=9a908537ecebaae63c471a1826bb9d304e36db4a81e8a7d8b9dc4400779a5a0a0282405a593f39018cc79489eac93d323382932209745915f7a0c864cde4883a
> commons-dbcp2-2.10.0-src.zip=631eea5d36f00d2c648b023057bea55edea174418283769310321f4851a49ccafbb101a6a4f835a396b6c3b1d34b6e284f26038dafc3686be3a9dd3690cf41c7
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> pache Maven 3.9.4 (dfbb324ad4a7c8fb0bf182e6d91b0ae20e3d2dd9)
> Maven home: /usr/local/Cellar/maven/3.9.4/libexec
> Java version: 11.0.20.1, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.20.1/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.5.1", arch: "x86_64", family: "mac"
> Darwin  22.6.0 Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56
> PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
> 
> Details of changes since 2.9.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.10.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.10.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.10.0-RC1/site/index.html
>(note some *relative* links are broken and the 2.10.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.9.0):
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.10.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/dbcp/2.10.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) 

Re: [VOTE] Release Apache Commons DBCP 2.10.0 based on RC1

2023-09-01 Thread Rob Tompkins
will look at this, this evening.

-Rob

> On Sep 1, 2023, at 10:59 AM, Henri Biestro  wrote:
> 
> 
> [ +1] Release these artifacts
> 
> Built on:
> 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; 
> root:xnu-8796.121.3~7/RELEASE_ARM64_T6000 arm64
> 
> With:
> openjdk version "1.8.0_352"
> OpenJDK Runtime Environment (Zulu 8.66.0.15-CA-macos-aarch64) (build 
> 1.8.0_352-b08)
> OpenJDK 64-Bit Server VM (Zulu 8.66.0.15-CA-macos-aarch64) (build 25.352-b08, 
> mixed mode)
> 
> Running:
> mvn clean install; mvn site;
> 
> Build and tests ok, site is ok; no warnings of any kind in reports (japicmp, 
> pmd, checkstyle, spotbugs). 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons DbUtils 1.8.0 based on RC1

2023-08-04 Thread Rob Tompkins
All looks approriate
signatures ok
build ok on java 8, 11, 17
reports look good.

Send it!

+1

> On Aug 1, 2023, at 8:40 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons DbUtils 1.7 was released, so I would like to release Apache
> Commons DbUtils 1.8.0.
> 
> Apache Commons DbUtils 1.8.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.0-RC1
> (svn revision 63303)
> 
> The Git tag commons-dbutils-1.8.0-RC1 commit for this RC is
> 675cfcd2f68b03254746c24d76a83a23dcddc6a2 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-dbutils.git;a=commit;h=675cfcd2f68b03254746c24d76a83a23dcddc6a2
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-dbutils.git
> --branch commons-dbutils-1.8.0-RC1 commons-dbutils-1.8.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1648/commons-dbutils/commons-dbutils/1.8.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Tue Aug 01 20:32:34 EDT 2023
> commons-dbutils-1.8.0-src.tar.gz=be1af717639a605d9510e2ac7435c0f06ba37ce8700e93f38e3f71a83ea2758c71821545d7271adc5ae7d9506c1f557386ee9b67a4979f9ab3fe7cb27a08e179
> commons-dbutils_commons-dbutils-1.8.0.spdx.json=295f2decdbf6e68696b5c44939029deec01ae8619dae4093b617f4171968cf8b281bd723815331e124a807fb1c5e74b5c22cf6c146281857874f1be38ef12cde
> commons-dbutils-1.8.0-sources.jar=6ab3192fb57bbdabfeb5f9992e3922cf7e6ef221d3ec5a7d66bd079406f6235058bfb6f115fa3e1ad7c8e02cd65fbb00adebf65c9c8914ba2758b30c24d97e32
> commons-dbutils-1.8.0-bom.json=6f939509e9cf901fab00c5e45e38ca8dcfe81c35069c97a270e0ba89f0d557feddd5f98b1320ed346e401e7be5a560325c021b6d8ba55ea2b0ea0a8652d037cb
> commons-dbutils-1.8.0-test-sources.jar=dac78668a91c6d3eed45f591a8a2c83f3cfc4871bd3a478aa0ed117ad6b315f9e14c43e38aafcf8b6e4f2e4e8076802dc2481d3bc1950f2cb928e74685cee960
> commons-dbutils-1.8.0-src.zip=0af2de984787938c1277cf34a5e54cf50dd1674e962cc7280c47f6129ceeda86f8e18e422056dbf859f774cc65135e786552bb4847869e1f6e4c6f3bb089e9c7
> commons-dbutils-1.8.0-bom.xml=5d7be2ff22c55ce73022230a4f2242b9d43c9fe6dcf1cda552d19c4bcb255222adb78774bdfc57f0159da947ea65509fd63ad568c79f5fed51e4bb3a2ae8142b
> commons-dbutils-1.8.0-bin.zip=76ebf30c465218022210f4e6ffc61756360a949156b5b3100ff9024ae6d782c328624b3bf1149280b0df4c466d3b4687efa92e6f9c483fc800bac47eddb0fbf5
> commons-dbutils-1.8.0-javadoc.jar=453cdd7517bc1f1ab0fb48e57d2795e8d1ded586246640a77b2b71d10c227ee7fae9c952f7cb82746be3df3e6544e097219873c732ba7b70271961666c2512bd
> commons-dbutils-1.8.0-bin.tar.gz=1f3832fd5e7a997d93174b8c08f630522b7ef59b878e48ea1aa1f80924290dec6ce56db9ae003c010eec4384e8aea33d8c4b84e4d232bf7ba13ae42b3618e25f
> commons-dbutils-1.8.0-tests.jar=96291ca4e46c5c426c45d65c4a219aeadb2f9fe1b4e18dd293d1a0529b171403a064a59f675707f2cf773a6a813abf8d1b58f3e46f9652a28eec4193d2421c97
> 
> I have tested this with
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> Using:
> 
> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
> Maven home: /usr/local/Cellar/maven/3.9.3/libexec
> Java version: 11.0.20, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.20/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.5", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul
> 5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64
> 
> Java 11 is used to produce a JPMS module but the target byte code and
> API is enforced as Java 8.
> 
> Details of changes since 1.7 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.8.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.7):
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/dbutils/1.8.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 

Re: [VOTE] Release Apache Commons Lang 3.13.0 based on RC1

2023-07-27 Thread Rob Tompkins
+1

Builds with java 8, 11, and 17 using maven 3.9.2, on mac osx 13.4.1: “mvn clean 
test install site”

Rat report clean

japicmp looks good (I think, there was something about a removal waay down 
in there under something saying “unchanged”) specifically on 
org.apache.commons.lang3.stream.Streams$ArrayCollector…it almost looks like a 
japicmp bug

signatures all check out clean.

Thank you, good work and pardon the slow vallidation. :-)

Cheers,
-Rob


> On Jul 23, 2023, at 3:57 PM, Gary Gregory  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Lang 3.12.0 was released, so I would like to
> release Apache Commons Lang 3.13.0.
> 
> Apache Commons Lang 3.13.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1
> (svn revision 63138)
> 
> The Git tag commons-lang-3.13.0-RC1 commit for this RC is
> bcc10b359318397a4d12dbaef22b101725bc6323 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=bcc10b359318397a4d12dbaef22b101725bc6323
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-lang.git
> --branch commons-lang-3.13.0-RC1 commons-lang-3.13.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1647/org/apache/commons/commons-lang3/3.13.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jul 23 15:44:56 EDT 2023
> Apache\ Commons\
> Lang-3.13.0.spdx.rdf.xml=b01ad1806ba0cc89a17b0972f6e46a5fef1dfb90fcb419e2802b0c18ac1c2d7543c3de469804d86600c0defee506504663c294c7bcfb1361ea3be1a70d955a4c
> commons-lang3-3.13.0-bin.tar.gz=2815fe7db3528c0e049564fccd6fb4f3729e3b786e4b2ad199ad3d3fe951f37ac0a51bba65e1b2645626e9ea9c6fdff319146b51cff094363bfce76bca97b847
> commons-lang3-3.13.0-bin.zip=1fa7b89addb498795fa015a69cca5b3c8b808cf02e680be3d07764c8e40ba7f4e0abf94f5073cae73412e0d36148d73deac0e4485c74ecd5e766232efbd9ac92
> commons-lang3-3.13.0-bom.json=3b79f37a63eeb9c48820e08b343d7a4f1c8a1d3adeecc3f18354ed5c3bc684064becd8f392d4f9afee4d66af7000403bf4287ac311ceeaeb45f7d47a19d698ce
> commons-lang3-3.13.0-bom.xml=592e4f47a28eea1df0cac5851cd623a9b020e5950674eaba6de5d15ac986038a25b24600510d83c787d0e5f40e1bd1eb14817dae5e4f3255cde20fb6a4608b28
> commons-lang3-3.13.0-javadoc.jar=630661fe66da908e5eb2d54aa139e2e0c9772f28b6742973bfd321c17304b2270dec55d33fff9a6ba15f1018d9c4f77236b3b4cfb6aa95890b1e60d299c82565
> commons-lang3-3.13.0-sources.jar=4e237775fdead7ea9507ffaf0e11da3b23b358e874aa9c0ec3e11bb1b2f1f1c70f7a1d07b98601afe51d7ed66d6fee324aa07f3eb3bffb886dbf60b8d11eb237
> commons-lang3-3.13.0-src.tar.gz=6fca0ce86aea84458021360bac3f6775135a1a5c1826194921e2d4ead7c12f6ac560e7c3fc240112f862aaee24be8754c37dd867f45e9449cde4a388018d8691
> commons-lang3-3.13.0-src.zip=d6d90dcff0138b975dd42cef26760a4f35f7592499ef15b761b93854ad115e8fc14bba74d68a4394896d89867a27465f40af2163d40284ac4665ef8b77f81f64
> commons-lang3-3.13.0-test-sources.jar=2e204dcd9e3052343be8708408285ced82c9e84a8779554d8a0c88fddb43642b5f511d838d926d59dd9d0757c6c27ab04ecd85bd9c269775097c7abec9482a2b
> commons-lang3-3.13.0-tests.jar=fc5396b97a6b3256f095232e0bce0441fa57142ce95c54a109cb154a07ba07aff5856ed2b52f8e1ac428e60f9bdda4a31010101accb71a1355632a2bea0f79cb
> 
> I have tested this with
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
> Maven home: /usr/local/Cellar/maven/3.9.3/libexec
> Java version: 1.8.0_372, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+372/libexec/openjdk.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22
> PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 3.12.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/index.html
>(note some *relative* links are broken and the 3.13.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.12.0):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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,
> 
> 

Re: [VOTE] Release Apache Commons Lang 3.13.0 based on RC1

2023-07-27 Thread Rob Tompkins
Working on validating this now.

-Rob

> On Jul 23, 2023, at 3:57 PM, Gary Gregory  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Lang 3.12.0 was released, so I would like to
> release Apache Commons Lang 3.13.0.
> 
> Apache Commons Lang 3.13.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1
> (svn revision 63138)
> 
> The Git tag commons-lang-3.13.0-RC1 commit for this RC is
> bcc10b359318397a4d12dbaef22b101725bc6323 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=bcc10b359318397a4d12dbaef22b101725bc6323
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-lang.git
> --branch commons-lang-3.13.0-RC1 commons-lang-3.13.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1647/org/apache/commons/commons-lang3/3.13.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jul 23 15:44:56 EDT 2023
> Apache\ Commons\
> Lang-3.13.0.spdx.rdf.xml=b01ad1806ba0cc89a17b0972f6e46a5fef1dfb90fcb419e2802b0c18ac1c2d7543c3de469804d86600c0defee506504663c294c7bcfb1361ea3be1a70d955a4c
> commons-lang3-3.13.0-bin.tar.gz=2815fe7db3528c0e049564fccd6fb4f3729e3b786e4b2ad199ad3d3fe951f37ac0a51bba65e1b2645626e9ea9c6fdff319146b51cff094363bfce76bca97b847
> commons-lang3-3.13.0-bin.zip=1fa7b89addb498795fa015a69cca5b3c8b808cf02e680be3d07764c8e40ba7f4e0abf94f5073cae73412e0d36148d73deac0e4485c74ecd5e766232efbd9ac92
> commons-lang3-3.13.0-bom.json=3b79f37a63eeb9c48820e08b343d7a4f1c8a1d3adeecc3f18354ed5c3bc684064becd8f392d4f9afee4d66af7000403bf4287ac311ceeaeb45f7d47a19d698ce
> commons-lang3-3.13.0-bom.xml=592e4f47a28eea1df0cac5851cd623a9b020e5950674eaba6de5d15ac986038a25b24600510d83c787d0e5f40e1bd1eb14817dae5e4f3255cde20fb6a4608b28
> commons-lang3-3.13.0-javadoc.jar=630661fe66da908e5eb2d54aa139e2e0c9772f28b6742973bfd321c17304b2270dec55d33fff9a6ba15f1018d9c4f77236b3b4cfb6aa95890b1e60d299c82565
> commons-lang3-3.13.0-sources.jar=4e237775fdead7ea9507ffaf0e11da3b23b358e874aa9c0ec3e11bb1b2f1f1c70f7a1d07b98601afe51d7ed66d6fee324aa07f3eb3bffb886dbf60b8d11eb237
> commons-lang3-3.13.0-src.tar.gz=6fca0ce86aea84458021360bac3f6775135a1a5c1826194921e2d4ead7c12f6ac560e7c3fc240112f862aaee24be8754c37dd867f45e9449cde4a388018d8691
> commons-lang3-3.13.0-src.zip=d6d90dcff0138b975dd42cef26760a4f35f7592499ef15b761b93854ad115e8fc14bba74d68a4394896d89867a27465f40af2163d40284ac4665ef8b77f81f64
> commons-lang3-3.13.0-test-sources.jar=2e204dcd9e3052343be8708408285ced82c9e84a8779554d8a0c88fddb43642b5f511d838d926d59dd9d0757c6c27ab04ecd85bd9c269775097c7abec9482a2b
> commons-lang3-3.13.0-tests.jar=fc5396b97a6b3256f095232e0bce0441fa57142ce95c54a109cb154a07ba07aff5856ed2b52f8e1ac428e60f9bdda4a31010101accb71a1355632a2bea0f79cb
> 
> I have tested this with
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
> Maven home: /usr/local/Cellar/maven/3.9.3/libexec
> Java version: 1.8.0_372, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+372/libexec/openjdk.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22
> PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 3.12.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/index.html
>(note some *relative* links are broken and the 3.13.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 3.12.0):
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/lang/3.13.0-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone 

Re: [VOTE] Release Apache Commons FileUpload 2.0.0-M1 based on RC1

2023-07-17 Thread Rob Tompkins
+1
Signatures Check Out
Builds, tests, sitte on Java8, Java11, and Java17
All reports look good, (nit) the coverage is a little low 50-65%
Rat reports all clean
Only other Nit is a “NeedsWork" in 
org.apache.commons.fileupload2.javax.JavaxHttpServletRequestFactory likely more 
important than the coverage issues.

Send it! Thanks for all the great work!

Cheers,
-Rob

> On Jul 16, 2023, at 7:57 AM, Gary Gregory  wrote:
> 
> Hi All,
> 
> This is the first milestone release for 2.0.0 which splits FileUpload
> into a multi-module project to support the Jakarta and legacy javax
> namespaces, so I would like to release Apache Commons FileUpload
> 2.0.0-M1.
> 
> The previous release was Apache Commons FileUpload 1.5 (javax only).
> 
> Apache Commons FileUpload 2.0.0-M1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M1-RC1
> (svn revision 63007)
> 
> The Git tag commons-fileupload-2.0.0-M1-RC1 commit for this RC is
> 2107cd3dbb58417ccf1afae055aac3d5f597a665 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-fileupload.git;a=commit;h=2107cd3dbb58417ccf1afae055aac3d5f597a665
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-fileupload.git
> --branch commons-fileupload-2.0.0-M1-RC1
> commons-fileupload-2.0.0-M1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1645/org/apache/commons/commons-fileupload2/2.0.0-M1/
> 
> #Release SHA-512s
> #Sat Jul 15 19:37:24 EDT 2023
> org.apache.commons_commons-fileupload2-distribution-2.0.0-M1.spdx.json=d6062b88aa2a958295a1552f0a1641bc22ccf708e1f868ca8faee822fe42c88bf44fe93ffed39af550c352bc10126d435a066ae7c6a678cb5c907d7837690a10
> commons-fileupload2-distribution-2.0.0-M1-bom.xml=793b199ef275ad28d76c827c8d515be848ae110f4a579030f5a1ca48c6f5b1ec14948d7d5cd428ee5cdfaa0ca9f24f39d1d14b4463763b0063f3b7288079ab6d
> commons-fileupload2-distribution-2.0.0-M1-bom.json=457481013a00ec85a27c9b70267daca8c9ed20e768bbafaff2d334d2023520f3e4f3b9aad62976bc19051bd923303902a6ddfe0eade11819d25eb3ceff9ed87c
> commons-fileupload2-2.0.0-M1-src.zip=e6108527d5beb505a198bd4ecc619f9024fdb9fa9cb771001213fd9b470568bb0f2a0ba2ddff85e6f0a69768544def9a66b0997875c9a7aa7fdbfce6fa91404c
> commons-fileupload2-2.0.0-M1-bin.zip=84067861fca81db81450c7f419f8c5a0bc2232f36277ceaba3771ade80c34297c142d698823885a9d03b646b8edfc7e7866c6c4411580fe20f63cbc237840bd0
> commons-fileupload2-2.0.0-M1-src.tar.gz=44d94a1f449051b82fbfe05782eb85df2299713ed359fbbfd5c9fab085782ad97fb60eb2ef5d05d545dd16682ade3f6ae5f34b87216f0a4e79bbcd7f6c1d7723
> commons-fileupload2-2.0.0-M1-bin.tar.gz=f7727ffd2df00b04ee7960b681eea35a4a320e9e8677f8ed77ac9b5841d6ee59d5df049104e1cea6bea475b4518b2ee2f50ac0b6a92cb1e9e2b142d56869b078
> 
> I have tested this with 'mvn clean install' using:
> 
> Apache Maven 3.9.3 (21122926829f1ead511c958d89bd2f672198ae9f)
> Maven home: /usr/local/Cellar/maven/3.9.3/libexec
> Java version: 11.0.19, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.19/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> Darwin gdg-mac-mini.local 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun
> 8 22:22:22 PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
> 
> Java 11 was used to build with the Java 8 release flag in order to get
> all the little JPMS turds in the right place.
> 
> Details of changes since 1.5 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M1-RC1/site/index.html
>(note some *relative* links are broken and the 2.0.0-M1
> directories are not yet created - these will be OK once the site is
> deployed.)
> 
> There is no binary compatibility report because this is a major
> release in a new Java namespace and new Maven coordinates.
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/fileupload/2.0.0-M1-RC1/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 1a) Clone and checkout the RC tag
> 
> git clone 

Re: [LAZY][VOTE] Release Apache Commons Build Plugin Maven Mojo 1.13 based on RC1

2023-06-26 Thread Rob Tompkins
+1

> On Jun 25, 2023, at 11:30 AM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Build Plugin Maven Mojo 1.12 was released, so I would like to
> release Apache Commons Build Plugin Maven Mojo 1.13.
> 
> Apache Commons Build Plugin Maven Mojo 1.13 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1
> (svn revision 62637)
> 
> The Git tag commons-build-plugin-1.13-RC1 commit for this RC is
> 6c99abd8ae378dcfa4154b0ff1787de6b4bff968 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-build-plugin.git;a=commit;h=6c99abd8ae378dcfa4154b0ff1787de6b4bff968
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-build-plugin.git
> --branch commons-build-plugin-1.13-RC1 commons-build-plugin-1.13-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1641/org/apache/commons/commons-build-plugin/1.13/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jun 25 11:20:14 EDT 2023
> commons-build-plugin-1.13-javadoc.jar=6e9f9b5fed3816149388a325f1adb2fb1596531deb94ab63c306eac3efcda6069328b3718399c7a616e82781bfb01cf24ea33d52a24d6d6497fbe2b5bc07b0ee
> commons-build-plugin-1.13-test-sources.jar=02ebcf44d442fae28042cc5609319813d03cc4cf22dba195c40fd95cb5cc6ea3e5dec077cc809160378a6fe4da8d6ce9bab156f90b1cdcab9d3b3a739d96934e
> commons-build-plugin-1.13-src.tar.gz=b8d91116c8e5994d3b13f59a2b18971132e63b6ced0ff53004f21d45c601c7abd2e7912574f1fd545821f9c2c82ff27eb41417a38795db2448a1621316db44d0
> commons-build-plugin-1.13-bom.xml=91012ce5998e626e71605641020b6a21fdb03c859b423bec40b22d417faf362c315c1c50226fe9be5189cfeca86a9ce618d08b61a8be24b01f08683fd61d9c76
> org.apache.commons_commons-build-plugin-1.13.spdx.json=e967bb2644b460058c5b6d2d9ffa429b6c1f1c3e67cb6d3c06c86ef03054a6401b1d364e737630bf69c2a50174cc40ca4f11d6fb13b5ac7f2a06cd0471ce52b5
> commons-build-plugin-1.13-tests.jar=f6e9d604557354d0da8efe7c1a43f01c636154f280757d009dc7546b75d14653f53379aac8f62225c92f53a4841c0f536be3031b8663efbeb397a9f979ce9411
> commons-build-plugin-1.13-bom.json=90f202a9dc7f6214882f8ae71ac4668b9bacf5e67362bb310b693cefb1fc56b3088e109575ad2decf6bff00f736ec42c7ee10882f48394f824ddbd08709b72df
> commons-build-plugin-1.13-src.zip=e6ef7fe0f581f2d29e8c28dbd272ac52a7f28ea58bd6cfa879fb84650c889dddfb22d1e6f5014b77576b3a96052d37546d616a5f13b5b7517374b215e686e435
> commons-build-plugin-1.13-sources.jar=b94b27a41492ffdfdaf96f182411efcc5ce6ed1582ad76d65b8db7d5fda87421caa148b43ee9f64d464bd05c4b0a18c105453308e500e8d1ce7c373e83bc3790
> 
> I have tested this with:
> 
> mvn -V -Duser.name=$my_apache_id -Prelease -Ptest-deploy -P jacoco -P
> japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
> Maven home: /usr/local/Cellar/maven/3.9.2/libexec
> Java version: 11.0.19, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.19/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> 
> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22
> PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.12 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-RC1/site/index.html
>(note some *relative* links are broken and the 1.13 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/build-plugin/1.13-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-build-plugin.git
> --branch commons-build-plugin-1.13-RC1 commons-build-plugin-1.13-RC1
> cd commons-build-plugin-1.13-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) 

Re: [LAZY][VOTE] Release Apache Commons Release Plugin 1.8.1 based on RC1

2023-06-26 Thread Rob Tompkins
+1

> On Jun 25, 2023, at 3:13 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs since Apache Commons Release Plugin 1.7 was
> released, so I would like to release Apache Commons Release Plugin
> 1.8.1.
> 
> Apache Commons Release Plugin 1.8.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1
> (svn revision 62638)
> 
> The Git tag commons-release-plugin-1.8.1-RC1 commit for this RC is
> 0de47206a633016ff26422063275f5d7de6650c9 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=0de47206a633016ff26422063275f5d7de6650c9
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git
> --branch commons-release-plugin-1.8.1-RC1
> commons-release-plugin-1.8.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1642/org/apache/commons/commons-release-plugin/1.8.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Jun 25 15:02:45 EDT 2023
> commons-release-plugin-1.8.1-bin.tar.gz=6867de0615c5ca4ad8f15052e689fd5548725c6dca342ddfe9168910f5f99a845b56a41716fcdf1bde3a8c90965b76351d46eae7fcd8910c63c9b8d9dcf1118b
> org.apache.commons_commons-release-plugin-1.8.1.spdx.json=4274329e50b9bf2a0b82890fd77fb4f2f37f0649be918c03b8d40d8928804e874ed11ca261c82090abb2234fc4fa55ac5a10a769252be2118fd890c605946b2e
> commons-release-plugin-1.8.1-bin.zip=96ee13f0e0f73e4c1981b5e945a2c69a8f7269ba8a5ddbebe1b45919b20ad4b3774021531ffc1d18582646e5e252a202a3c5c88b12edbd9167a7ab4d728716d5
> commons-release-plugin-1.8.1-tests.jar=ac6cf663046c5104dc73e47985ce97dfd100bf744aa889c3030e346f4ea24096632b83b1d36b169da3af8ded6a14f71a52eb93f0147619b22551085ca5c2807f
> commons-release-plugin-1.8.1-test-sources.jar=e71ad8e23016dc0c5c4624452dda87cc7258ecda04c1b38c00f52249a83f1551c159b2018554505760853573c54e3ebe513a50b2d4c427953acc0cf94882d524
> commons-release-plugin-1.8.1-src.tar.gz=26bf9b9045332446aad04792bc8e6a0d641f5d2aaae71f5a339639ff2018dea02e9d46e0cf0d18abe8520c0c924baa6a4cc97f7850859f4a74a0b188cc51e450
> commons-release-plugin-1.8.1-javadoc.jar=60c7afdc296cfe6afb3a5c36a10ad1ec4b4d3ac7fe370c611babef59681e9aaeb268f3d5755bdde8ec2f7fe6c45c46d5f88e54ceb9e053c95c0335a0359b8f75
> commons-release-plugin-1.8.1-src.zip=bbae4dd7ffd360190734a36359a4ad5cd3922e010482e32f7b5ba5789455cae9adb126a64634a1722d6f280d6ab1adea0d1b74ee409ca7719351da2c15076fe1
> commons-release-plugin-1.8.1-bom.xml=c08a3001b8a98fb4d9faacc97be706df53e97e4150a47f8b1866eacdfd7a4de0e371cf144d6dab2d3aef5c096c2139aafa7bb10c350816d89da04a8b67a80a3a
> commons-release-plugin-1.8.1-bom.json=3754e0997788777b15447cf049ef400073052dccbea6dd28a0ac12dd390e19a8f80411514f6e55c90a1368315d0a6c852c47b753a802833f82653e983814e518
> commons-release-plugin-1.8.1-sources.jar=2080248fccd261dd7b8770fe74c331d75b19290cf6bd58fbfd83d82cbbac7249b63fcc753d9332391cdeab4208b5406b64361997efa91ff212e7f454f4a2fac1
> 
> 
> I have tested this with:
> 
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> 
> Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
> Maven home: /usr/local/Cellar/maven/3.9.2/libexec
> Java version: 11.0.19, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@11/11.0.19/libexec/openjdk.jdk/Contents/Home
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4.1", arch: "x86_64", family: "mac"
> 
> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:22
> PDT 2023; root:xnu-8796.121.3~7/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.7 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/site/index.html
>(note some *relative* links are broken and the 1.8.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.7):
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-RC1/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/release-plugin/1.8.1-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.
> 
> 

Re: [VOTE] Release Apache Commons Codec 1.16.0 based on RC2

2023-06-21 Thread Rob Tompkins
+1

Builds on java8, java11, java17 with maven 3.9.2.,
Reports all look good,
Signatures all look good,
Site looks good…

Cheers,
-Rob

> On Jun 17, 2023, at 8:24 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache
> Commons Codec 1.15 was released, so I would like to release Apache
> Commons Codec 1.16.0.
> 
> Apache Commons Codec 1.16.0 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/codec/1.16.0-RC2
> (svn revision 62466)
> 
> The Git tag commons-codec-1.16.0-RC2 commit for this RC is
> 2614a4ca9d79c2b96a3147d206b4fb27443f8ce8 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=commit;h=2614a4ca9d79c2b96a3147d206b4fb27443f8ce8
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-codec.git
> --branch commons-codec-1.16.0-RC2 commons-codec-1.16.0-RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1639/commons-codec/commons-codec/1.16.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Jun 17 20:15:15 EDT 2023
> commons-codec-1.16.0-bin.tar.gz=99f650d52dd8a5dd1329485e1fb6973e4e78359206216232e2a08a66178ce5f731bd6e411459b0ce9074730ea33600df6b36371faf0cd1d7d46282814c32c552
> commons-codec-1.16.0-bin.zip=309710f01557293229bd6ed40ae6ddafe57fddf98347865e7b2568812a1c2e3df79f7b3a201bebd731f3bbf4ca9f3aeedff9de3a4657fc82cd68d45c20456f67
> commons-codec-1.16.0-bom.json=eff4214c629a646b72a3883a00cf3e4c1af563b5460b0d9890fdc8e1fb7884a934f7c6b66e4a03674c6fa6bfbdb16f5b910d5ba6c7b6f9d95c0d94dc29923af0
> commons-codec-1.16.0-bom.xml=688d852d31696ef044debd2ccec9982e6bc110dfa76acee402194a4c710df08e11ba1b4d02baaac05373d8047a8c792915126c6690037000996d73ea08375ef0
> commons-codec-1.16.0-javadoc.jar=e02515bc74be420f01abd3292a685e5d390d636ce830b5c5744411b606c0c91ccb3e95beea882fb3d7683bd72276e95b95df00fac0ff579a213230d380a1ac60
> commons-codec-1.16.0-sources.jar=620557a9c348515a59da12abf350e72ac6d33a2a63aba5a53e4c88cb5756eb6816f02e5901f9d3dbc705362e90a5683129cb20042cac7a7d0dc68aee2a234b0a
> commons-codec-1.16.0-src.tar.gz=5212beae43a59d5a92c80f87640278913bf07d6527ead573710391a8b5c813af67f8086de5cd80f4b06845752652684d7c28f6236f5a8bd0bd6a8b89dc0d9532
> commons-codec-1.16.0-src.zip=cf6f6299e00bf007320ed9c5d1c81469cb45821368b6aee02deb499c0e3ca8c932dd4564c68bae66d92b0ae0adba41e8a5e9ad7b8fc1469e7182321cea825e5e
> commons-codec-1.16.0-test-sources.jar=220682de6d763b424dd026fbaab035605a74510e86b9a11f91c023c2207490f1c6676752b37e1682e527d1399d51c76652730c61751e3d59d518d395ee4ba75c
> commons-codec-1.16.0-tests.jar=3a112dd6133f7e0cbffb003524f64dbd557d466fdd0e2ad9e2c7fd45181bc51fdcde4d163b2bf74b16609d12de29e1083ed03b9f66f1fa1e84da9deff0d6cf03
> commons-codec_commons-codec-1.16.0.spdx.json=851d7cfad6f240ea517fdf102165aa000823730c91dd8c92b48a2d89c1e56d87767954799f15f00bc16ce1309c0ae8d3aa501e536998bdb8328d80dedf7d29cb
> 
> I have tested this with 'mvn' and 'mvn -V -Prelease -Ptest-deploy -P
> jacoco -P japicmp clean package site deploy'
> 
> using:
> 
> Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
> Maven home: /usr/local/Cellar/maven/3.9.2/libexec
> Java version: 1.8.0_372, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+372/libexec/openjdk.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.4", arch: "x86_64", family: "mac"
> 
> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:51:50
> PDT 2023; root:xnu-8796.121.2~5/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.15 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.0-RC2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.0-RC2/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.0-RC2/site/index.html
>(note some *relative* links are broken and the 1.16.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.15):
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.0-RC2/site/japicmp.html
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/codec/1.16.0-RC2/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 

Re: [VOTE] Release Apache Commons IO 2.13.0 based on RC1

2023-06-07 Thread Rob Tompkins
+1

> On Jun 6, 2023, at 9:19 PM, Gary Gregory  wrote:
> 
> My +1
> 
> Gary
> 
> 
>> On Sat, Jun 3, 2023 at 12:51 PM Gary Gregory  wrote:
>> 
>> We have fixed a few bugs and added some enhancements since Apache Commons
>> IO 2.12.0 was released, so I would like to release Apache Commons IO 2.13.0.
>> 
>> Apache Commons IO 2.13.0 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1 (svn
>> revision 62275)
>> 
>> The Git tag commons-io-2.13.0-RC1 commit for this RC is
>> c2f23c5ae6ebd0acd3e915f75a839b00f5b0984d which you can browse here:
>> 
>> https://gitbox.apache.org/repos/asf?p=commons-io.git;a=commit;h=c2f23c5ae6ebd0acd3e915f75a839b00f5b0984d
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-io.git --branch
>> commons-io-2.13.0-RC1 commons-io-2.13.0-RC1
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1638/commons-io/commons-io/2.13.0/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sat Jun 03 12:39:12 EDT 2023
>> 
>> commons-io-2.13.0-bin.tar.gz=fd6655daf94ee0bdb1bf9c840a6eecfb88a3473caf321e9eb081fe2e2caf59fdb12e9671c7aa82e54266dc15244e46943df91883d78bd3d0d69b5657616e9a0a
>> 
>> commons-io-2.13.0-bin.zip=57f8d9ccf3b78a3bffdf7128e50627828e65556dc0266929bbe1dd80c7dbe11a69f6b7b2e076ad1d14f61076f60759ceeef88c3af38ad515746bfeec581e4ffb
>> 
>> commons-io-2.13.0-bom.json=f2de674c1f45ed35c8dbf66647211ba9f06e4933c0ea9cbf6de2f792c3d9d816b0164f40900023f8b1f481515d161d3fe974243725f2682f5576fceb9625300c
>> 
>> commons-io-2.13.0-bom.xml=e7ef941130dd16e200bb5dab29a7f34a1a9b373b1544ed9bbb2d472cf45ba7ec339d4480063f2ea8d09a470f8f4afab8ab907e5860e437176bc1e46c4047de0a
>> 
>> commons-io-2.13.0-javadoc.jar=b5687a93d230cde63cb1073e7e55c6f1f6d0141e82cfa3b2071b6a4774a10889392285d9e8cc9fed43bbcb748205be1173c5fa23edcc71463ce59d60dce7b8a1
>> 
>> commons-io-2.13.0-sources.jar=e9facd7c29504211b1c21df40d0c4d43db80d203dd18139882eef03eb58cafe3b63765b7ff725f46c4ea10d52ac4a6c7d3857b7b7548c799be5102643fc7ec10
>> 
>> commons-io-2.13.0-src.tar.gz=187df4b73ac20caa28de99381b32f46673ee5a3b519e6804e6cd8ced49412ba89dd6f5cf43e4cfb54c221331cefa1ed20a180d8c9f0e4c361b4b9a2e98b26017
>> 
>> commons-io-2.13.0-src.zip=e92812ceb9e1c31b437d241ed44f11253b9f9e90772062c9f9ed165520e8d8003c50b85e9c5f5ed69ed83ccb77a705188d733e880dcade1fb0ebc655983d0d2b
>> 
>> commons-io-2.13.0-test-sources.jar=9aca47ee983d40228abb3c357de905a0f277e40bd26eed6eda9f71bfbd690bd9759e1a930fdd6f83e3e284844eae9f00bf23e71123e84e11bf7a004632504aa1
>> 
>> commons-io-2.13.0-tests.jar=e9df13feaa6ed0d0ae918568cf78e372887d40368f8676c505a1f9aa5cc10a088b6ca5c964370ba9f95a36a69fa5e07647a686da4477aaa2a28ba5bf1db9f7d6
>> 
>> commons-io_commons-io-2.13.0.spdx.json=94f3ad040d89cac2814df45c3310fc76c259e4762ae525a84f00adc306c05d6647da560a759d70ad5dddee0ac230c925928545ce73af7ae24579c0e3bfa3af63
>> 
>> I have tested this with
>> 
>> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
>> deploy
>> 
>> Using:
>> 
>> Apache Maven 3.9.2 (c9616018c7a021c1c39be70fb2843d6f5f9b8a1c)
>> Maven home: /usr/local/Cellar/maven/3.9.2/libexec
>> Java version: 1.8.0_372, vendor: Homebrew, runtime:
>> /usr/local/Cellar/openjdk@8
>> /1.8.0+372/libexec/openjdk.jdk/Contents/Home/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "mac os x", version: "13.4", arch: "x86_64", family: "mac"
>> 
>> Darwin  22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:51:50 PDT
>> 2023; root:xnu-8796.121.2~5/RELEASE_X86_64 x86_64
>> 
>> Details of changes since 2.12.0 are in the release notes:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/RELEASE-NOTES.txt
>> 
>> https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/site/changes-report.html
>> 
>> Site:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/site/index.html
>>(note some *relative* links are broken and the 2.13.0 directories are
>> not yet created - these will be OK once the site is deployed.)
>> 
>> JApiCmp Report (compared to 2.12.0):
>> 
>> https://dist.apache.org/repos/dist/dev/commons/io/2.13.0-RC1/site/japicmp.html
>> 
>> RAT Report:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/io/2.13.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 

Re: [CANCEL][VOTE] Release Apache Commons IO 2.12.0 based on RC1

2023-05-03 Thread Rob Tompkins
Cool sounds good.

-Rob

> On May 3, 2023, at 9:55 AM, Gary Gregory  wrote:
> 
> Thanks Rob! Make sure you track git master as I am going through Alex's
> comments and pushing updates, I should be done tonight.
> 
> Gary
> 
> On Wed, May 3, 2023, 08:22 Rob Tompkins  wrote:
> 
>> I was reading this release over yesterday. I’m still looking at the code
>> changes generally.
>> 
>> Cheers,
>> -Rob
>> 
>>> On May 2, 2023, at 7:31 PM, Gary Gregory  wrote:
>>> 
>>> Great review Alex, TY, I am canceling this vote and will reply to this
>>> email with details.
>>> 
>>> Gary
>>> 
>>> On Tue, May 2, 2023, 12:14 Alex Herbert 
>> wrote:
>>> 
>>>> Validated signatures and checksums.
>>>> 
>>>> Build from source tar.gz file using 'mvn verify site' with:
>>>> 
>>>> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
>>>> Maven home: /usr/local/apache-maven-3
>>>> Java version: 11.0.18, vendor: Ubuntu, runtime:
>>>> /usr/lib/jvm/java-11-openjdk-amd64
>>>> Default locale: en_GB, platform encoding: UTF-8
>>>> OS name: "linux", version: "5.4.0-148-generic", arch: "amd64", family:
>>>> "unix"
>>>> 
>>>> I do see the checkstyle and spotbugs report.
>>>> 
>>>> Spotbugs has a few mentions of non-serializable fields. This is
>>>> another case where we may not wish to support serialization going
>>>> forward (e.g. as with CSV). I cannot remember the solution for CSV. I
>>>> think it was a formal documentation that serialization will be dropped
>>>> in CSV 2.0. Looking at the error these are not new as the report in
>>>> the live site for 2.11.0 also has these.
>>>> 
>>>> Checked for the @since tag for new items in the japicmp report and
>>>> found no missing tags. I note that some of the new classes in package
>>>> io.build have no javadoc on inner classes with public constructors and
>>>> some static helper protected methods.
>>>> 
>>>> New helper classes with a private constructor should be final:
>>>> 
>>>> CharsetDecoders
>>>> CharsetEncoders
>>>> FilesUncheck
>>>> FileTimes
>>>> 
>>>> Changing public classes to final after a release breaks binary
>>>> compatibility. However other utility classes in the lib do not use
>>>> final for classes so this is not critical. FYI there are 5 others
>>>> which I found using PMD. The rule is
>>>> ClassWithOnlyPrivateConstructorsShouldBeFinal [1]. This is not part of
>>>> the default rules used in the project which is using the default from
>>>> the maven plugin [2]. If you run 'mvn pmd:check' the rules are written
>>>> to target/pmd/rulesets. I took these rules, added the extra rule and
>>>> then used this as the ruleset for PMD.
>>>> 
>>>> The new IOBiFunction has a noop method. This has no equivalent in
>>>> java.util.function.BiFunction. As discussed on a recent PR for Lang
>>>> (adding a noop to TriFunction) it does not make sense to have a noop
>>>> function that returns null as this is an operation. I assume this
>>>> BiFunction class was copied across from Lang bringing the noop with
>>>> it.
>>>> 
>>>> A minor inconsistency: QueueInputStream uses the new
>>>> AbstractStreamBuilder API but existing public constructors are not
>>>> deprecated. However other classes with equally simple constructors
>>>> (MemoryMappedFileInputStream, MessageDigestCalculatingInputStream,
>>>> etc) have deprecated their public constructors in favour of the
>>>> builder.
>>>> 
>>>> Documentation: The new AbstractStreamBuilder API exposes a lot of
>>>> public set methods in the builder. Some of these may not be applicable
>>>> to all use cases. The API allows an object for IO that is typically
>>>> created with either a Reader/Writer or Input/OutputStream, to also be
>>>> created with a Path or File. However creation using a Reader does not
>>>> support InputStream and vice versa. If a Reader is set then the Origin
>>>> will not be valid and a RTE will occur when opening the object which
>>>> tries to access the input stream from the Origin. Using the old API of
>>>> public constructors it was clear what the supported input

Re: [CANCEL][VOTE] Release Apache Commons IO 2.12.0 based on RC1

2023-05-03 Thread Rob Tompkins
I was reading this release over yesterday. I’m still looking at the code 
changes generally.

Cheers,
-Rob

> On May 2, 2023, at 7:31 PM, Gary Gregory  wrote:
> 
> Great review Alex, TY, I am canceling this vote and will reply to this
> email with details.
> 
> Gary
> 
> On Tue, May 2, 2023, 12:14 Alex Herbert  wrote:
> 
>> Validated signatures and checksums.
>> 
>> Build from source tar.gz file using 'mvn verify site' with:
>> 
>> Apache Maven 3.9.0 (9b58d2bad23a66be161c4664ef21ce219c2c8584)
>> Maven home: /usr/local/apache-maven-3
>> Java version: 11.0.18, vendor: Ubuntu, runtime:
>> /usr/lib/jvm/java-11-openjdk-amd64
>> Default locale: en_GB, platform encoding: UTF-8
>> OS name: "linux", version: "5.4.0-148-generic", arch: "amd64", family:
>> "unix"
>> 
>> I do see the checkstyle and spotbugs report.
>> 
>> Spotbugs has a few mentions of non-serializable fields. This is
>> another case where we may not wish to support serialization going
>> forward (e.g. as with CSV). I cannot remember the solution for CSV. I
>> think it was a formal documentation that serialization will be dropped
>> in CSV 2.0. Looking at the error these are not new as the report in
>> the live site for 2.11.0 also has these.
>> 
>> Checked for the @since tag for new items in the japicmp report and
>> found no missing tags. I note that some of the new classes in package
>> io.build have no javadoc on inner classes with public constructors and
>> some static helper protected methods.
>> 
>> New helper classes with a private constructor should be final:
>> 
>> CharsetDecoders
>> CharsetEncoders
>> FilesUncheck
>> FileTimes
>> 
>> Changing public classes to final after a release breaks binary
>> compatibility. However other utility classes in the lib do not use
>> final for classes so this is not critical. FYI there are 5 others
>> which I found using PMD. The rule is
>> ClassWithOnlyPrivateConstructorsShouldBeFinal [1]. This is not part of
>> the default rules used in the project which is using the default from
>> the maven plugin [2]. If you run 'mvn pmd:check' the rules are written
>> to target/pmd/rulesets. I took these rules, added the extra rule and
>> then used this as the ruleset for PMD.
>> 
>> The new IOBiFunction has a noop method. This has no equivalent in
>> java.util.function.BiFunction. As discussed on a recent PR for Lang
>> (adding a noop to TriFunction) it does not make sense to have a noop
>> function that returns null as this is an operation. I assume this
>> BiFunction class was copied across from Lang bringing the noop with
>> it.
>> 
>> A minor inconsistency: QueueInputStream uses the new
>> AbstractStreamBuilder API but existing public constructors are not
>> deprecated. However other classes with equally simple constructors
>> (MemoryMappedFileInputStream, MessageDigestCalculatingInputStream,
>> etc) have deprecated their public constructors in favour of the
>> builder.
>> 
>> Documentation: The new AbstractStreamBuilder API exposes a lot of
>> public set methods in the builder. Some of these may not be applicable
>> to all use cases. The API allows an object for IO that is typically
>> created with either a Reader/Writer or Input/OutputStream, to also be
>> created with a Path or File. However creation using a Reader does not
>> support InputStream and vice versa. If a Reader is set then the Origin
>> will not be valid and a RTE will occur when opening the object which
>> tries to access the input stream from the Origin. Using the old API of
>> public constructors it was clear what the supported input arguments
>> were. All the Deprecated constructors that reference the new builder
>> would benefit from javadoc on the builder of the valid options that
>> can be configured.
>> 
>> The new classes UncheckedBufferedReader, UncheckedFilterInputStream,
>> UncheckedFilterReader, UnsynchronizedBufferedInputStream,
>> UnsynchronizedFilterInputStream, UncheckedFilterOutputStream do not
>> use the AbstractStreamBuilder API and have constructors. I think the
>> API can be applied in these cases, although many of the options would
>> be ignored (e.g. charset, buffer size, etc). However there may be a
>> reason that blocks use of the API that I did not notice (as I did not
>> try to implement it).
>> 
>> NullOutputStream deprecated constructor references deprecated
>> NULL_OUTPUT_STREAM singleton. Should be INSTANCE. Following on from
>> this should the NullPrintStream and NullWriter constructors also be
>> deprecated in favour of the INSTANCE?
>> 
>> New class UncheckedFilterOutputStream has a public constructor but
>> UncheckedFilterWriter is protected. Both have a static 'on' method for
>> construction so this is inconsistent. These could use the
>> AbstractStreamBuilder API although the constructors are very simple.
>> Use of the new API would allow use of Path/File as output.
>> 
>> New class ThreadUtils has a TODO in the javadoc. The javadoc also
>> requires  tags. The TODO can be moved to a method comment rather
>> 

Re: [VOTE] Release Apache Commons FileUpload 1.5 based on RC1

2023-02-14 Thread Rob Tompkins
+1, and thanks for the work here. Much appreciation!

-Rob

> On Feb 9, 2023, at 8:39 AM, Mark Thomas  wrote:
> 
> Ping. One more PMC member vote required.
> 
> Mark
> 
> On 01/02/2023 12:57, Mark Thomas wrote:
>> We have fixed a few bugs and added some small enhancements since FileUpload 
>> 1.4 was released, so I would like to release FileUpload 1.5.
>> FileUpload 1.5 RC1 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1
>> (svn revision 59794)
>> The tag is here:
>> https://gitbox.apache.org/repos/asf?p=commons-fileupload.git;a=tag;h=7a932af807778ffd11ed5e86cc69b405855c11fb
>> Maven artifacts are here:
>> https://repository.apache.org/content/repositories/orgapachecommons-1618/
>> These are the artifacts and their hashes:
>> #Release SHA-512s
>> commons-fileupload-1.5-bin.tar.gz=185699b43afcf1494378ed7efae25fb3630346323c6abadaef2dfce3a01c533341a51e2c14f081f4b90d02dd9364c4a565966bf4358e9a11b71aa3a19adb3097
>> commons-fileupload-1.5-bin.zip=4e99e8ee135d0f331a0f5ffeb3a15d94f31469c57c9ca79a65608665165604be7e20d4571571fdfaf37938db90744dc318ed634c19dd6f31c7d4815b0084c9b1
>> commons-fileupload-1.5-bom.json=864690cd2f9e962dab4a58661a356acc29aebe5958dea1c2161541160d36b3a86f582b8fd9be6502465e7d68480aad9c1777e0b1646ef9ad8c02aa541f78f964
>> commons-fileupload-1.5-bom.xml=ab82f4581eb9056dd2c28ea8656016d02729c3648f140d5b270b470e91df2baa3b0e1d2111b445093fc826834d86a2525d7421dc47ffd4afab8690ce5e865512
>> commons-fileupload-1.5-javadoc.jar=f1c1dbb054e4b1a4ed1616c78b3e00b97b4eb8b05b89971ec87d80a09aef680451d98762fd490b7618b00fe2c33e1e50e153676bb92a3941fb82c21cf5c7ec0a
>> commons-fileupload-1.5-sources.jar=4a62eae065a0f7063c7377e06e499582acfcb2cd3f0a35e2b6893d7bc04406da49b9e60e1b1ec7fb53b9fcfc028e335c4ce812a3085302853a62584e663c0f2c
>> commons-fileupload-1.5-src.tar.gz=6cf4a1deeb8511d29e1543af4b6d3d984f0f2991e6f4550d84e7fb5d1a6df6df71c1fad6d2607d4b5d062c8fff498d30da7bd1a5bfc09f9cabdb0a57dc5c1a16
>> commons-fileupload-1.5-src.zip=b0b6f54e6de2d472033f1bca70b587c99f1b8d649147469e4f315848ed284a9db6b4f200046cb36e99613a4029b5f5b86316bbe26494ce34ca36a670e69492e5
>> commons-fileupload-1.5-test-sources.jar=428d35784b99543d304fc44eb26da9fb76bd5844843bf7f0b027cc511a56a08ea5891c8aacc14099bf2fce0ef9cc90cc3bca01255bdf57d6015b232ecefa7f4c
>> commons-fileupload-1.5-tests.jar=b3b06fe319cbc4b679b8a0ada40772bb943151bc26828c6c4d98a102c5aafab94dcffa6f61570830339d7b0f86c834413660240c6692811d22e1cfc0e051d330
>> commons-fileupload_commons-fileupload-1.5.spdx.json=add8592cb24014c3e732b1eb13f9780904ef28a4439091431b1070a735993ff83c3fdaae60de2be146b4f816c9dee123ff06515cbbd8127d99d13c93d03220fc
>> commons-xyz-1.2-test-sources.jar
>> Details of changes since 1.4 are in the release notes:
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1/RELEASE-NOTES.txt
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1/site/changes-report.html
>> Site:
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1/site/index.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,
>> i.e. sometime after 13:00 UTC 4 Feb 2023
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>> Thanks!
>> Mark
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons FileUpload 1.5 based on RC1

2023-02-09 Thread Rob Tompkins
Will try to get to today.

-Rob

> On Feb 9, 2023, at 8:39 AM, Mark Thomas  wrote:
> 
> Ping. One more PMC member vote required.
> 
> Mark
> 
> On 01/02/2023 12:57, Mark Thomas wrote:
>> We have fixed a few bugs and added some small enhancements since FileUpload 
>> 1.4 was released, so I would like to release FileUpload 1.5.
>> FileUpload 1.5 RC1 is available for review here:
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1
>> (svn revision 59794)
>> The tag is here:
>> https://gitbox.apache.org/repos/asf?p=commons-fileupload.git;a=tag;h=7a932af807778ffd11ed5e86cc69b405855c11fb
>> Maven artifacts are here:
>> https://repository.apache.org/content/repositories/orgapachecommons-1618/
>> These are the artifacts and their hashes:
>> #Release SHA-512s
>> commons-fileupload-1.5-bin.tar.gz=185699b43afcf1494378ed7efae25fb3630346323c6abadaef2dfce3a01c533341a51e2c14f081f4b90d02dd9364c4a565966bf4358e9a11b71aa3a19adb3097
>> commons-fileupload-1.5-bin.zip=4e99e8ee135d0f331a0f5ffeb3a15d94f31469c57c9ca79a65608665165604be7e20d4571571fdfaf37938db90744dc318ed634c19dd6f31c7d4815b0084c9b1
>> commons-fileupload-1.5-bom.json=864690cd2f9e962dab4a58661a356acc29aebe5958dea1c2161541160d36b3a86f582b8fd9be6502465e7d68480aad9c1777e0b1646ef9ad8c02aa541f78f964
>> commons-fileupload-1.5-bom.xml=ab82f4581eb9056dd2c28ea8656016d02729c3648f140d5b270b470e91df2baa3b0e1d2111b445093fc826834d86a2525d7421dc47ffd4afab8690ce5e865512
>> commons-fileupload-1.5-javadoc.jar=f1c1dbb054e4b1a4ed1616c78b3e00b97b4eb8b05b89971ec87d80a09aef680451d98762fd490b7618b00fe2c33e1e50e153676bb92a3941fb82c21cf5c7ec0a
>> commons-fileupload-1.5-sources.jar=4a62eae065a0f7063c7377e06e499582acfcb2cd3f0a35e2b6893d7bc04406da49b9e60e1b1ec7fb53b9fcfc028e335c4ce812a3085302853a62584e663c0f2c
>> commons-fileupload-1.5-src.tar.gz=6cf4a1deeb8511d29e1543af4b6d3d984f0f2991e6f4550d84e7fb5d1a6df6df71c1fad6d2607d4b5d062c8fff498d30da7bd1a5bfc09f9cabdb0a57dc5c1a16
>> commons-fileupload-1.5-src.zip=b0b6f54e6de2d472033f1bca70b587c99f1b8d649147469e4f315848ed284a9db6b4f200046cb36e99613a4029b5f5b86316bbe26494ce34ca36a670e69492e5
>> commons-fileupload-1.5-test-sources.jar=428d35784b99543d304fc44eb26da9fb76bd5844843bf7f0b027cc511a56a08ea5891c8aacc14099bf2fce0ef9cc90cc3bca01255bdf57d6015b232ecefa7f4c
>> commons-fileupload-1.5-tests.jar=b3b06fe319cbc4b679b8a0ada40772bb943151bc26828c6c4d98a102c5aafab94dcffa6f61570830339d7b0f86c834413660240c6692811d22e1cfc0e051d330
>> commons-fileupload_commons-fileupload-1.5.spdx.json=add8592cb24014c3e732b1eb13f9780904ef28a4439091431b1070a735993ff83c3fdaae60de2be146b4f816c9dee123ff06515cbbd8127d99d13c93d03220fc
>> commons-xyz-1.2-test-sources.jar
>> Details of changes since 1.4 are in the release notes:
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1/RELEASE-NOTES.txt
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1/site/changes-report.html
>> Site:
>> https://dist.apache.org/repos/dist/dev/commons/fileupload/1.5-RC1/site/index.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,
>> i.e. sometime after 13:00 UTC 4 Feb 2023
>>   [ ] +1 Release these artifacts
>>   [ ] +0 OK, but...
>>   [ ] -0 OK, but really should fix...
>>   [ ] -1 I oppose this release because...
>> Thanks!
>> Mark
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons CSV 1.10.0 based on RC2

2023-01-29 Thread Rob Tompkins
+1

Checks out on java8, java11, and java17.
Reports site look good
Signatures all correct

> On Jan 28, 2023, at 1:02 PM, Gary Gregory  wrote:
> 
> We have fixed quite a few bugs and added some enhancements since
> Apache Commons CSV 1.9.0 was released, so I would like to release
> Apache Commons CSV 1.10.0.
> 
> Apache Commons CSV 1.10.0 RC2 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/csv/1.10.0-RC2 (svn
> revision 59641)
> 
> The Git tag commons-csv-1.10.0-RC2 commit for this RC is
> 5b99c860986a87f9da664bf47a3a7c0026673123 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-csv.git;a=commit;h=5b99c860986a87f9da664bf47a3a7c0026673123
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-csv.git
> --branch commons-csv-1.10.0-RC2 commons-csv-1.10.0-RC2
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1617/org/apache/commons/commons-csv/1.10.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Jan 28 12:52:21 EST 2023
> commons-csv-1.10.0-bin.tar.gz=889e25045a1491253b02fac788a6357e6ce4e8285d420cf60872ad7fe09fa3b15799d17b1a9c9cff503aaecaa4952490e2bcef581872117d4d1e2347f765ff42
> commons-csv-1.10.0-bin.zip=c179c3efd1f6e5aa562a17d17c26b2662d48823778a7232bce32e17808ae3d33268602349e40ff3578b65b1d74dc7a065d5e8d104a05092c15573f245fcadfef
> commons-csv-1.10.0-bom.json=aeb13ce03a3712f6313b389b25a8d65624679d9d31edf7b9a49618c1462da3170148155b2688e11b8d2df6ea09e68bea47a9635158765ca02c8c33749c9777e8
> commons-csv-1.10.0-bom.xml=8f7f5e75be14bca0e79747f99181dc289e39871863009da90071100ee7ef5dae17e0287e7da5542bce3f98917f605016fabaab4a42908ed7c4118963534cf2fa
> commons-csv-1.10.0-javadoc.jar=e1f238122b92a1bfb2e9845f55ef91c275d8c47624b6c6699d0c57a98db2470ae0a14bd3668972ac8bc11271404fe56799ec1536b3de49db218121d01ddb5f1d
> commons-csv-1.10.0-sources.jar=1d778c86c5c0218180a4dc8a02052cec7c1cba6f71ad8d4bdfa256c0133b5e1c8c06ac775ef914d9baf2278803ba3796646693be49119aac28c4a4457ba03ac0
> commons-csv-1.10.0-src.tar.gz=2674b0cc0806fbfc7013f759ef3c2149a73406809e9f1a84cea1ec12ae66514682ebec4f902d1385f5f6dcdf2b0babbaa289823722ce175804196d3b3b5427fb
> commons-csv-1.10.0-src.zip=0123ed2538214e767a264d4632bb4ab82367d8e4a4b4095722a3c821d646262af0634588a5e1025ef6e2b249a6d5e654cdbdba8d567272abcb7149f7adc5
> commons-csv-1.10.0-test-sources.jar=5f88b40f08923074384fe883214a3be19c42d07a73a753f2afbd99c66e2606aa9a4e619ed878183f0ca1bda4a35448be60d53cd27b3ad24bcac4f83e4b63
> commons-csv-1.10.0-tests.jar=f3475a56cff362167ff592113dff8fbc4792c1601b87a85cb1cb1560bc52bb49b540282b057e1cde21ddb06664dc8c591d87a475b2bf12ef205efd1860dd4048
> org.apache.commons_commons-csv-1.10.0.spdx.json=4609932f7a3bbb0158021d29ea1baaa163b84c06786b36a46eaaa81f096df3d7cbdd28a99b587f6cdf6fbd4bbe1a38e1f1f9eeab89847474a2f4056765b9be6d
> 
> 
> I have tested this with 'mvn -V -Prelease -Ptest-deploy -P jacoco -P
> japicmp clean package site deploy' using:
> 
> Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
> Maven home: /usr/local/Cellar/maven/3.8.7/libexec
> Java version: 1.8.0_362, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+362/libexec/openjdk.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "13.1", arch: "x86_64", family: "mac"
> 
> Darwin  22.2.0 Darwin Kernel Version 22.2.0: Fri Nov 11 02:08:47
> PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.9.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.10.0-RC2/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.10.0-RC2/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.10.0-RC2/site/index.html
>(note some *relative* links are broken and the 1.10.0 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.9.0):
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.10.0-RC2/site/japicmp.html
>Where the following is intentional:
>MODIFIED (Serializable incompatible(!): serialVersionUID modified)
> final public class org.apache.commons.csv.CSVFormat
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/csv/1.10.0-RC2/site/rat-report.html
> 
> KEYS:
>  https://downloads.apache.org/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.
> 
> 

RE: [VOTE] Release Apache Commons Crypto 1.2.0 based on RC1

2023-01-22 Thread Rob Tompkins
+1 Build passes for java8, java11, (nit) java17 on mac M1 is a bit funky 
because they moved homebrew from /usr/local/homebrew -> /opt/homebrew, and 
java17 actually realizes that the M1 is an arm processor. The earlier versions 
of java do not.

Signatures Check out.
Reports Surefire, Rat, JaCoCo, japicmp, Checkstyle, SpotBugs, CPD, and PMD all 
look reasonable

--

We have fixed a few bugs and made some enhancements since Apache
Commons Crypto 1.1.0 was released, so I would like to release Apache
Commons Crypto 1.2.0.

Apache Commons Crypto 1.2.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/crypto/1.2.0-RC1
(svn revision 59345)

The Git tag commons-crypto-1.2.0-RC1 commit for this RC is
d1ca10a92a61257ac225c6c1f8881af0aef91309 which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-crypto.git;a=commit;h=d1ca10a92a61257ac225c6c1f8881af0aef91309
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-crypto.git
--branch commons-crypto-1.2.0-RC1 commons-crypto-1.2.0-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1616/org/apache/commons/commons-crypto/1.2.0/

These are the artifacts and their hashes:

#Release SHA-512s
#Sat Jan 14 17:16:26 EST 2023
commons-crypto-1.2.0-bin.tar.gz=fb9084a5d9adcd4df606c7deb9396fa5693443b6a91be12f5de17e4281d3e7d89b526dc6ebd7991569894bde2f9fb67036eb78504cb4fa26fae9b7a99d082051
commons-crypto-1.2.0-bin.zip=c78d2d2f3343c0402d1e55301d9a85036550b937512024470ee9843f1cbcf6d28a49e2f1e2b2a6856c26898da61eec5739cfefac237abbf2e8735f0f69bb42bf
commons-crypto-1.2.0-bom.json=104a6c100cad2e896836815449c0d74da1ab469e7260f0911ddf2230b6f89392ef4768768493192999b60dd36ffcca48483110508cee4c44e3a924fcbbe59a60
commons-crypto-1.2.0-bom.xml=bf30ab0f46f0356d64ed4b3b39574c1dcc351b14d0f12233e63f1b8e9d04fb5fe223e2625dd118be65013682b9a64382fee29e56713a8bd949501b3f49bfd639
commons-crypto-1.2.0-javadoc.jar=4a1944faca7aa68716bb2c55fafe0e10eff435c9ff10b1f3ad2cc96948c57ea0c7648b1fc6cb3d56a23d67f6f91b9e61d8b1eeb092e3c13335b2adba07e8540f
commons-crypto-1.2.0-sources.jar=234fd31696293390c1e0f02a1b9362079452b5524bdb148fb635734f14c39d61c92a96799e2751d3291e33fee6cc2d469545b8b45d44486d9d5edf2b87ebf4c5
commons-crypto-1.2.0-src.tar.gz=4ebbdc3eddedaeb142c2d4b30fe640b70f95d785d290b96422d7bd64f8179899c573a88e23048bf061e58d52c13f79ae6180fb694c2f86ec584b419847dbb381
commons-crypto-1.2.0-src.zip=2ec1c7510893c6274722f587e6e5a2d3ec3ad4f077727be22fd85b13a18304feab5a93a5c57c82ffe9c8f2f8763b64452256e4053b5e186c68e620bf698ae857
commons-crypto-1.2.0-test-sources.jar=d2a0218e8b60ca0f2f0b7b11d79636ec3d8c0f226b4a405d5f15a12f5128aeed65105b7b81310ada097fad85580276912910757b5672b66c2dacae7520a2506d
commons-crypto-1.2.0-tests.jar=8439dd580eb36ba270da12c59c19c600ae1e2ea375e47b7bcf4855ac13a8baad833ee49d0796f804853a6639895c531318977c9f6b4760d3fc8617893a8d9b3f
org.apache.commons_commons-crypto-1.2.0.spdx.json=31a4fa548308eda4c1798c9a5f6b0fef5c5034cb09586099c93dd93978e95fda81043faa45af237e5289ff9ecdccff8ec0b18af13e7ffc43095a79d3f217cb8b

I have tested this with 'mvn -V -Prelease -Ptest-deploy clean package
site deploy' using:

Apache Maven 3.8.7 (b89d5959fcde851dcb1c8946a785a163f14e1e29)
Maven home: /usr/local/Cellar/maven/3.8.7/libexec
Java version: 1.8.0_352, vendor: Homebrew, runtime:
/usr/local/Cellar/openjdk@8/1.8.0+352/libexec/openjdk.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "13.1", arch: "x86_64", family: "mac"
Darwin gdg-mac-mini.local 22.2.0 Darwin Kernel Version 22.2.0: Fri Nov
11 02:08:47 PST 2022; root:xnu-8792.61.2~4/RELEASE_X86_64 x86_64

Non-macOS native binaries were built on Windows 10 using Docker.

Details of changes since 1.1.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/crypto/1.2.0-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/crypto/1.2.0-RC1/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/crypto/1.2.0-RC1/site/index.html
(note some *relative* links are broken and the 1.2.0 directories
are not yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 1.1.0):

https://dist.apache.org/repos/dist/dev/commons/crypto/1.2.0-RC1/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/crypto/1.2.0-RC1/site/rat-report.html

KEYS:
  https://downloads.apache.org/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 

Re: Math: Yearly patch for commons-math3

2022-12-06 Thread Rob Tompkins



> On Dec 6, 2022, at 12:26 PM, Gary Gregory  wrote:
> 
> "even if its only updating the copyright headers"
> 
> You must be joking, you know we are volunteers here. I can't imagine you'd
> be willing to pay for this from a commercial vendor or consultant which
> makes the request show a lack of respect for our time and resources.

We are volunteers that are treated poorly by our employers!
-Rob

> 
> Gary
> 
>> On Tue, Dec 6, 2022, 09:58 Darrell Merryweather <
>> darrellmerryweat...@gmail.com> wrote:
>> 
>> Hi
>> 
>> As part of our FOSS compliance, we need to ensure that 3rd party libraries
>> are well maintained, to ensure, from a security perspective, we will have
>> no future issues. We are currently using commons-math3 in some of our
>> developments, and we were hoping someone might be able to include a yearly
>> patch of math3, even if its only updating the copyright headers, so that we
>> can ensure an updated version is maintained.
>> 
>> Also, when is math4 being released?
>> 
>> Thanks
>> 
>> Darrell Merryweather
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [ALL] components still using Travis

2022-03-29 Thread Rob Tompkins


> On Mar 29, 2022, at 10:51 AM, sebb  wrote:
> 
> On Tue, 29 Mar 2022 at 15:27, Rob Tompkins  <mailto:chtom...@gmail.com>> wrote:
>> 
>> I wonder if the python script will be effective in doing the migration 
>> properly. I’ll try to carve some time out to help here.
> 
> In the case of Commons, most of the components have very similar
> needs, so one can probably just copy existing workflows from another
> component and adjust slightly.

With youi there….just thinking that it might not be exactly 1-to-1 such that a 
python script automating the migration would work.

-Rob

> 
>> -Rob
>> 
>>> On Mar 29, 2022, at 10:19 AM, sebb  wrote:
>>> 
>>> On Tue, 29 Mar 2022 at 13:57, Matt Juntunen  
>>> wrote:
>>>> 
>>>> Hi Sebb,
>>>> 
>>>> Yep, geometry is still using Travis. I've never used GitHub Actions so
>>>> I'm not sure what it's capable of. Are there any specific features it
>>>> provides that are driving the migration to it? Or is it more a matter
>>>> of community preference? Either way is fine, I'm just curious.
>>> 
>>> It looks like Infra may be intending to migrate projects:
>>> https://cwiki.apache.org/confluence/display/INFRA/Travis+to+GitHub+Actions+Migration
>>> 
>>>> Regards,
>>>> Matt J
>>>> 
>>>> On Tue, Mar 29, 2022 at 7:22 AM sebb  wrote:
>>>>> 
>>>>> It looks like there is a general move to switch from Travis to GitHub 
>>>>> Actions.
>>>>> AFAICT the following components are still using Travis:
>>>>> 
>>>>> geometry
>>>>> jelly
>>>>> jxpath
>>>>> math
>>>>> numbers
>>>>> rng
>>>>> weaver
>>>>> 
>>>>> Do we need to move these as well?
>>>>> 
>>>>> BTW, emails from GHA runs can now be directed to project mailing
>>>>> lists, which is great (*)
>>>>> See: https://s.apache.org/asfyaml-gha
>>>>> 
>>>>> e.g. update .asf.yaml to include:
>>>>> notifications:
>>>>> ...
>>>>> jobs: notificati...@commons.apache.org
>>>>> 
>>>>> Sebb.
>>>>> (*) Travis always had this, but recently switched to a new email
>>>>> system which means all such mails have to be moderated.
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>> 
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>> 
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
>> <mailto:dev-unsubscr...@commons.apache.org>
>> For additional commands, e-mail: dev-h...@commons.apache.org 
>> <mailto:dev-h...@commons.apache.org>
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
> <mailto:dev-unsubscr...@commons.apache.org>
> For additional commands, e-mail: dev-h...@commons.apache.org 
> <mailto:dev-h...@commons.apache.org>


Re: [ALL] components still using Travis

2022-03-29 Thread Rob Tompkins
I wonder if the python script will be effective in doing the migration 
properly. I’ll try to carve some time out to help here.

-Rob 

> On Mar 29, 2022, at 10:19 AM, sebb  wrote:
> 
> On Tue, 29 Mar 2022 at 13:57, Matt Juntunen  wrote:
>> 
>> Hi Sebb,
>> 
>> Yep, geometry is still using Travis. I've never used GitHub Actions so
>> I'm not sure what it's capable of. Are there any specific features it
>> provides that are driving the migration to it? Or is it more a matter
>> of community preference? Either way is fine, I'm just curious.
> 
> It looks like Infra may be intending to migrate projects:
> https://cwiki.apache.org/confluence/display/INFRA/Travis+to+GitHub+Actions+Migration
> 
>> Regards,
>> Matt J
>> 
>> On Tue, Mar 29, 2022 at 7:22 AM sebb  wrote:
>>> 
>>> It looks like there is a general move to switch from Travis to GitHub 
>>> Actions.
>>> AFAICT the following components are still using Travis:
>>> 
>>> geometry
>>> jelly
>>> jxpath
>>> math
>>> numbers
>>> rng
>>> weaver
>>> 
>>> Do we need to move these as well?
>>> 
>>> BTW, emails from GHA runs can now be directed to project mailing
>>> lists, which is great (*)
>>> See: https://s.apache.org/asfyaml-gha
>>> 
>>> e.g. update .asf.yaml to include:
>>> notifications:
>>> ...
>>>  jobs: notificati...@commons.apache.org
>>> 
>>> Sebb.
>>> (*) Travis always had this, but recently switched to a new email
>>> system which means all such mails have to be moderated.
>>> 
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE][LAZY] Release Apache Commons Release Plugin 1.8.0 based on RC1

2022-03-16 Thread Rob Tompkins
Looked it over +1 

Cheers,
-Rob

> On Mar 13, 2022, at 5:00 PM, Gary Gregory  wrote:
> 
> We have fixed a few bugs and added some enhancements since Apache Commons
> Release Plugin 1.7 was released, so I would like to release Apache Commons
> Release Plugin 1.8.0.
> 
> Apache Commons Release Plugin 1.8.0 RC1 is available for review here:
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1
> (svn revision 53018)
> 
> The Git tag commons-release-plugin-1.8.0-RC1 commit for this RC is
> 414f394201ce23262895bb8b83bfa457a5884ab4 which you can browse here:
> 
> https://gitbox.apache.org/repos/asf?p=commons-release-plugin.git;a=commit;h=414f394201ce23262895bb8b83bfa457a5884ab4
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-release-plugin.git
> --branch commons-release-plugin-1.8.0-RC1 commons-release-plugin-1.8.0-RC1
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1582/org/apache/commons/commons-release-plugin/1.8.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sun Mar 13 16:02:54 EDT 2022
> commons-release-plugin-1.8.0-bin.tar.gz=34b50dff28dcb17ce209654a1fe310e02cfa860ce86b68e3fecc948da7bcdff395acbe6bd150588485b2e1a3418d154acbe02720c519e6a934ff69a1d65f063b
> commons-release-plugin-1.8.0-bin.zip=a8d40013a3ff62d8c82236c9236aadd632099708535d6f2f911d01a67f7c18bcdaa4b4c5171635344e20d78b7180e52f577eb0ddcde93b449e959b4ed6ad3e00
> commons-release-plugin-1.8.0-javadoc.jar=108fd9bd1979f606a6ce25bfee6a4f9d7b87afcf28ab46ef12a99e6cbf0a062eb75c9d46a259890993d750009c3b0ac95b715ba97784b712eee4da27bcaed2aa
> commons-release-plugin-1.8.0-sources.jar=0b5eeb6c28498a61e7c23a66d72eb31e2a0a6fc1842ddef77513e266c77175639e106f9507e1b6067c0b0260fe0933b8e39d920941b3b83c80a53464bf405f49
> commons-release-plugin-1.8.0-src.tar.gz=75c9e64b156586cfadc888ac045a8d185e1b40885aaf9c5912d0ff78fc0bcca4cc4ac3898ed58ad82ac94dc65d8ea9eef0c4b44f2762ef8d5f772228a70467b0
> commons-release-plugin-1.8.0-src.zip=f39b8648b6baf62177f9a037f870133c072ea8093e6b5018f56555254525a5d16147002bf34c378e5a6b142b3c96c9ed2d7505cebd83515e726bd79912ab184a
> commons-release-plugin-1.8.0-test-sources.jar=a84cf4f0c8b49f058b8a8a2f1139f2e261ba8ecb3c107355c2abcf1825a0981a5e128345b91cc397e767aac815a9d8f9e88ac5fa70304c7324a35c9e7ebd0bfe
> commons-release-plugin-1.8.0-tests.jar=3d16b44b310c698002b460093bac5c44e5209615cfd3771d6c7c528c718a7918d25695a64cf8b71fb1a29a9c22efde2b1c6f101072e26ef428418722b2806d6f
> 
> I have tested this with 'mvn clean install -DskipTests && mvn -V
> -Duser.name=$my_apache_id -Dcommons.release-plugin.version=1.8.0 -Prelease
> -Pjacoco -Pjapicmp -Ptest-deploy clean package site deploy'
> 
> Using:
> 
> Apache Maven 3.8.4 (9b656c72d54e5bacbed989b64718c159fe39b537)
> Maven home: /usr/local/Cellar/maven/3.8.4/libexec
> Java version: 1.8.0_322, vendor: Homebrew, runtime:
> /usr/local/Cellar/openjdk@8/1.8.0+322/libexec/openjdk.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "12.2.1", arch: "x86_64", family: "mac"
> Darwin --- 21.3.0 Darwin Kernel Version 21.3.0: Wed Jan  5 21:37:58 PST
> 2022; root:xnu-8019.80.24~20/RELEASE_X86_64 x86_64
> 
> Details of changes since 1.7 are in the release notes:
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/RELEASE-NOTES.txt
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/site/changes-report.html
> 
> Site:
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.8.0 directories are
> not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 1.7):
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.0-RC1/site/japicmp.html
> 
> RAT Report:
> 
> https://dist.apache.org/repos/dist/dev/commons/commons-release-plugin/1.8.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-release-plugin.git
> --branch commons-release-plugin-1.8.0-RC1 commons-release-plugin-1.8.0-RC1
> cd commons-release-plugin-1.8.0-RC1
> 
> 2) Check Apache licenses
> 
> This 

Re: [all] Do not build the project site with Maven 3.8.2

2022-03-13 Thread Rob Tompkins



> On Mar 13, 2022, at 6:27 PM, Gary Gregory  wrote:
> 
> We have a lazy release vote in flight for commons-release-plugin 1.8.0 that
> include a hack to workaround this issue..
> 

Many thanks Gary.

-Rob

> Gary
> 
>> On Fri, Mar 4, 2022, 14:53 Rob Tompkins  wrote:
>> 
>> 
>> 
>>>> On Mar 4, 2022, at 9:57 AM, Gary Gregory  wrote:
>>> 
>>> On Fri, Mar 4, 2022 at 9:56 AM Alex Herbert 
>>> wrote:
>>> 
>>>>> On Fri, 4 Mar 2022 at 14:43, Rob Tompkins  wrote:
>>>>> 
>>>>> Yes that is on my plate to fix, but I haven’t gotten time to fix it.
>>>> I’ve for the first time in a while got some time this weekend away from
>> my
>>>> standard obligations and will try to put some time in on it. Pardon my
>>>> being remiss, my personal life has been quite hectic over the past 2
>> months
>>>> both at home and at work.
>>>>> 
>>>>> -Rob
>>>> 
>>>> Hi Rob,
>>>> 
>>>> IIRC I think the issue you would like to fix is in the commons release
>>>> plugin trying to modify collections that are now immutable in Maven
>>>> 3.8.
>>>> 
>>> 
>>> Indeed, I created a while back
>>> https://issues.apache.org/jira/browse/MNG-7316
>> 
>> Yep. And I appreciate that help :-)
>> 
>> -Rob
>> 
>>> 
>>> Gary
>>> 
>>>> 
>>>> This is another issue with Maven 3.8, specifically a regression in
>>>> 3.8.2 in how it computes inheritance from parent projects. So for now
>>>> it may be recommended to try releasing and building the site using
>>>> Maven 3.6.3.
>>>> 
>>>> Alex
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>> 
>>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [all] Do not build the project site with Maven 3.8.2

2022-03-04 Thread Rob Tompkins



> On Mar 4, 2022, at 9:57 AM, Gary Gregory  wrote:
> 
> On Fri, Mar 4, 2022 at 9:56 AM Alex Herbert 
> wrote:
> 
>>> On Fri, 4 Mar 2022 at 14:43, Rob Tompkins  wrote:
>>> 
>>> Yes that is on my plate to fix, but I haven’t gotten time to fix it.
>> I’ve for the first time in a while got some time this weekend away from my
>> standard obligations and will try to put some time in on it. Pardon my
>> being remiss, my personal life has been quite hectic over the past 2 months
>> both at home and at work.
>>> 
>>> -Rob
>> 
>> Hi Rob,
>> 
>> IIRC I think the issue you would like to fix is in the commons release
>> plugin trying to modify collections that are now immutable in Maven
>> 3.8.
>> 
> 
> Indeed, I created a while back
> https://issues.apache.org/jira/browse/MNG-7316

Yep. And I appreciate that help :-)

-Rob

> 
> Gary
> 
>> 
>> This is another issue with Maven 3.8, specifically a regression in
>> 3.8.2 in how it computes inheritance from parent projects. So for now
>> it may be recommended to try releasing and building the site using
>> Maven 3.6.3.
>> 
>> Alex
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [all] Do not build the project site with Maven 3.8.2

2022-03-04 Thread Rob Tompkins
Yes that is on my plate to fix, but I haven’t gotten time to fix it. I’ve for 
the first time in a while got some time this weekend away from my standard 
obligations and will try to put some time in on it. Pardon my being remiss, my 
personal life has been quite hectic over the past 2 months both at home and at 
work. 

-Rob

> On Mar 4, 2022, at 5:33 AM, Alex Herbert  wrote:
> 
> FYI: Release managers
> 
> I have found an issue when building the site using maven 3.8.2.
> 
> The project site descriptor (site.xml) is inherited from
> commons-parent. This should be merged with the site.xml from the
> project. The parent brings in a lot of extra menu items and
> commons-skin.
> 
> I have been building the site without reports for speed (it takes a
> few seconds):
> 
>> mvn clean site site:stage -DgenerateReports=false
> 
> (The site:stage is only required for multi-module projects.)
> 
> Running with maven 3.8.2 the site is rendered using
> 'org.apache.maven.skins:maven-default-skin:jar:1.3'. It lacks all the
> extra menus from the commons-parent site.xml.
> 
> Running with a previous stable version (maven 3.6.3) the site is
> rendered using 'org.apache.commons:commons-skin:jar:4.2'.
> 
> This appears to have been a regression introduced by MNG-7170 and
> fixed by MNG-7216. I confirm that version 3.8.3 of maven does not have
> the issue.
> 
> https://issues.apache.org/jira/browse/MNG-7170
> https://issues.apache.org/jira/browse/MNG-7216
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons Codec 1.16 based on RC1

2022-01-22 Thread Rob Tompkins
I’m in with the partent pom right now….can work on getting that sorted…plus I 
need to to get our release plugin working with the latest version of maven.

-Rob

> On Jan 22, 2022, at 5:42 PM, Matt Sicker  wrote:
> 
> Alright, digging through the parent parent parent pom, it looks like the 
> Apache parent pom has a release date from 2020 which is what ended up getting 
> used by the javadocs. This was fixed in that parent pom version 24, so we 
> could probably use an updated version of the commons parent pom as well to 
> pick that up.
> —
> Matt Sicker
> 
>> On Jan 22, 2022, at 15:33, Gary Gregory  wrote:
>> 
>> The copyright year is derived from POM properties or can be hard coded.
>> Trying to have a reproducible build can further muck things up where you
>> end up with 1969 as then end year as I recently fixed in Log4j. AFK but
>> there is a property called output build timestamp or something like that
>> that I set to the milliseconds for Jan 1 2022 (in the log4j POM). You might
>> want to do something like that here.
>> 
>> Gary
>> 
>> 
>> On Sat, Jan 22, 2022, 14:54 Matt Sicker  wrote:
>> 
>>> Looks like some of the non-blockers are things I didn’t notice before
>>> (like the user’s guide). I suppose I assumed that the site build
>>> automatically added links to the new release, though that only seems to be
>>> for the download page. I can update this in git (though it might require a
>>> second release candidate to stage the site unless there’s a way to
>>> regenerate that from master).
>>> 
>>> That FindBugs warning on Blake3 is worrying about unsigned shifts being
>>> converted to signed data, but that’s a Java limitation (byte is signed; no
>>> unsigned version available) and not a problem in practice (i.e., this is
>>> intentional: the method is to encode an integer into little endian as all
>>> the Salsa/ChaCha-related cryptography code uses little endian encodings).
>>> 
>>> I can rename the tag to match the proper convention, though it’d still be
>>> the lowercase version in the pom file if that’s a problem.
>>> 
>>> As for the javadoc copyright year, do you know where this gets specified?
>>> I figured it was auto-generated at build time.
>>> —
>>> Matt Sicker
>>> 
 On Jan 22, 2022, at 08:10, Gary Gregory  wrote:
 
 Thank you for cutting the RC! :-)
 
 Maybe blocker:
 
 The Javadoc end copyright year is 2020 instead of 2022.
 
 Not blockers:
 
 The git tag name does not match the instructions below so the git clone
 command fails (upper case instructions, lower case in actuality).
 
 New Blake3 class has a FindBugs style issue.
 
 Build uses FindBugs instead of SpotBugs.
 
 The site overview page does not include this release.
 
 The site left hand menu does not include a 1.16 link. In other sites,
>>> like
 Lang, I've done away with a Javadoc laundry list of version and replaced
>>> it
 with a single link to "Javadoc Archives".
 
 The user's guide could include a reference the new Blake3 code.
 
 Gary
 
 
 On Sat, Jan 22, 2022, 00:34 Matt Sicker  wrote:
 
> We have fixed quite a few bugs and added some significant enhancements
> since Apache Commons Codec 1.15 was released, so I would like to release
> Apache Commons Codec 1.16.
> 
> Apache Commons Codec 1.16 RC1 is available for review here:
>  https://dist.apache.org/repos/dist/dev/commons/codec/1.16-RC1 (svn
> revision 52215)
> 
> The Git tag commons-codec-1.16-RC1 commit for this RC is
> a7af6b2159c8868899608a5fe89228c50ab985a5 which you can browse here:
> 
> 
>>> https://gitbox.apache.org/repos/asf?p=commons-codec.git;a=commit;h=a7af6b2159c8868899608a5fe89228c50ab985a5
> You may checkout this tag using:
>  git clone https://gitbox.apache.org/repos/asf/commons-codec.git
> --branch commons-codec-1.16-RC1 commons-codec-1.16-RC1
> 
> Maven artifacts are here:
> 
> 
>>> https://repository.apache.org/content/repositories/orgapachecommons-1577/org/apache/commons/commons-codec/1.16/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Fri Jan 21 23:21:15 CST 2022
> 
> 
>>> commons-codec-1.16-bin.tar.gz=eb7721c3d4200531f5b403130ae5ebdbe2d4819ac65204feec403fe47af77182a499625649d6f54cd15240e9b65b193b66acbe450a6823162de6317c418050ba
> 
> 
>>> commons-codec-1.16-bin.tar.gz.asc=6e0cb2c1da47b40169ea7862c797797083a983ea6a4bf171c4465870c6383c61e3fe63effe4ca5211ec6210299ba7b2b1de5c39eebc2fdcaa3cf29560ba0549e
> 
> 
>>> commons-codec-1.16-bin.zip=018005d512dfbff989edad012b35c76aea1785fa7812e7a04bd718d0bd7146723e5d66d5ad4b0adf4b2c7d02f8c889b0aaa79277a8529f747afe238e9eb091bf
> 
> 
>>> commons-codec-1.16-bin.zip.asc=bc4e43ba5b4b430097be7ce308ed7f94f22911bc50fe2f0feb25cccb2e955933551441a003dfe6641e3b9e4f12e3027c2db91fb5396b405db98a42b4ea996032
> 
> 
>>> 

Re: [commons-io] branch master updated: Add CharsetEncoders.

2022-01-11 Thread Rob Tompkins


> On Jan 11, 2022, at 8:41 AM, Gilles Sadowski  wrote:
> 
> Le mar. 11 janv. 2022 à 14:21,  > a écrit :
>> 
>> This is an automated email from the ASF dual-hosted git repository.
>> 
>> ggregory pushed a commit to branch master
>> in repository https://gitbox.apache.org/repos/asf/commons-io.git
>> 
>> 
>> The following commit(s) were added to refs/heads/master by this push:
>> new 7ffb81b  Add CharsetEncoders.
>> 7ffb81b is described below
>> 
>> commit 7ffb81b956ff2c148cb27a1b05635a9ea7a98a6d
>> Author: Gary Gregory 
>> AuthorDate: Tue Jan 11 08:21:54 2022 -0500
>> 
>>Add CharsetEncoders.
>> ---
>> src/changes/changes.xml|  3 ++
>> .../apache/commons/io/charset/CharsetEncoders.java | 36 +++
>> .../apache/commons/io/charset/package-info.java| 22 +
>> .../commons/io/charset/CharsetEncodersTest.java| 54 
>> ++
>> 4 files changed, 115 insertions(+)
>> 
>> diff --git a/src/changes/changes.xml b/src/changes/changes.xml
>> index 5fd6789..c6d4778 100644
>> --- a/src/changes/changes.xml
>> +++ b/src/changes/changes.xml
>> @@ -293,6 +293,9 @@ The  type attribute can be add,update,fix,remove.
>>   
>> Add and reuse IOConsumer.forEach(T[], IOConsumer) and 
>> forEachIndexed(Stream, IOConsumer).
>>   
>> +  
>> +Add CharsetEncoders.
>> +  
>>   
>>   
>> Update FileEntry to use FileTime instead of long for file time 
>> stamps.
>> diff --git 
>> a/src/main/java/org/apache/commons/io/charset/CharsetEncoders.java 
>> b/src/main/java/org/apache/commons/io/charset/CharsetEncoders.java
>> new file mode 100644
>> index 000..815aaef
>> --- /dev/null
>> +++ b/src/main/java/org/apache/commons/io/charset/CharsetEncoders.java
>> @@ -0,0 +1,36 @@
>> +/*
>> + * Licensed to the Apache Software Foundation (ASF) under one or more
>> + * contributor license agreements.  See the NOTICE file distributed with
>> + * this work for additional information regarding copyright ownership.
>> + * The ASF licenses this file to You under the Apache License, Version 2.0
>> + * (the "License"); you may not use this file except in compliance with
>> + * the License.  You may obtain a copy of the License at
>> + *
>> + *  http://www.apache.org/licenses/LICENSE-2.0
>> + *
>> + * Unless required by applicable law or agreed to in writing, software
>> + * distributed under the License is distributed on an "AS IS" BASIS,
>> + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>> + * See the License for the specific language governing permissions and
>> + * limitations under the License.
>> + */
>> +
>> +package org.apache.commons.io.charset;
>> +
>> +import java.nio.charset.Charset;
>> +import java.nio.charset.CharsetEncoder;
>> +
>> +public class CharsetEncoders {
>> +
>> +/**
>> + * Returns the given non-null CharsetEncoder or a new default 
>> CharsetEncoder.
>> + *
>> + * @param charsetEncoder The CharsetEncoder to test.
>> + * @return the given non-null CharsetEncoder or a new default 
>> CharsetEncoder.
>> + * @since 2.12.0
>> + */
>> +public static CharsetEncoder toCharsetEncoder(CharsetEncoder 
>> charsetEncoder) {
>> +return charsetEncoder != null ? charsetEncoder : 
>> Charset.defaultCharset().newEncoder();
>> +}
> 
> What's the use-case for such a function?
> 
> void userFunction(CharsetEncoder charsetEncoder) { /* ... */ }
> 
> Not using Commons IO:
> ---CUT---
>  userFunction(csEnc == null ? Charset.defaultCharset().newEncoder() : csEnc);
> ---CUT---
> vs using Commons IO:
> ---CUT---
>  userFunction(CharsetEncoders.toCharsetEncoder(csEnc));
> ---CUT---
> 
> IMO, the former call is clearer (self-documenting) and safer (explicit request
> for a default).


If things are unclear in the code, why not check in comments as to why 
we’re doing what we’re doing. I’ve found that comments about what’s going on 
are over the top, but why comments are of great value.

-Rob

> 
>> [...]
> 
> Gilles
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org 
> 
> For additional commands, e-mail: dev-h...@commons.apache.org 
> 


Re: can we get rid of dependabot?

2021-12-30 Thread Rob Tompkins
I believe that we already have begun to do this. -Rob

> On Dec 30, 2021, at 6:16 PM, sebb  wrote:
> 
> Those of you who want to keep the robot, please use the instructions
> to reduce the spam.
> 
>> On Thu, 30 Dec 2021 at 22:51, Rob Tompkins  wrote:
>> 
>> 
>> 
>>>> On Dec 30, 2021, at 5:50 PM, Matt Sicker  wrote:
>>> 
>>> There are tons of options to configure. The defaults are handy for smaller 
>>> projects, but they are clearly spammy for larger ones like this.
>>> 
>>> https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates
>>>  
>>> <https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates>
>>> 
>> 
>> +1
>> 
>>> --
>>> Matt Sicker
>>> 
>>>>> On Dec 30, 2021, at 16:48, Rob Tompkins  wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> On Dec 30, 2021, at 5:37 PM, sebb >>>>> <mailto:seb...@gmail.com>> wrote:
>>>>> 
>>>>> On Thu, 30 Dec 2021 at 21:39, Rob Tompkins >>>> <mailto:chtom...@gmail.com>> wrote:
>>>>>> 
>>>>>> Guys. The fundamental argument underpinng all this is whether it’s 
>>>>>> better to have robot eyes on the code and human eyes on the code. Stop 
>>>>>> arguing one side or the other. We need to find a way to do both 
>>>>>> successfully.
>>>>> 
>>>>> The issue is *not* about robot or no robot.
>>>>> 
>>>>> It is about this particular robot that causes so much noise.
>>>> 
>>>> Yes! That’s right so we need to figure out how to use the robot correctly!
>>>> 
>>>>> 
>>>>>> 
>>>>>> 
>>>>>>>> On Dec 29, 2021, at 1:57 PM, Phil Steitz >>>>>>> <mailto:phil.ste...@gmail.com>> wrote:
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On 12/29/21 8:43 AM, sebb wrote:
>>>>>>>>> On Wed, 29 Dec 2021 at 14:53, Gary Gregory >>>>>>>> <mailto:garydgreg...@gmail.com>> wrote:
>>>>>>>>>> On Wed, Dec 29, 2021 at 9:42 AM sebb >>>>>>>>> <mailto:seb...@gmail.com>> wrote:
>>>>>>>>> 
>>>>>>>>>> On Wed, 29 Dec 2021 at 14:18, Gary Gregory >>>>>>>>> <mailto:garydgreg...@gmail.com>> wrote:
>>>>>>>>>>> On Wed, Dec 29, 2021 at 9:07 AM sebb >>>>>>>>>> <mailto:seb...@gmail.com>> wrote:
>>>>>>>>>>> 
>>>>>>>>>>>> On Wed, 29 Dec 2021 at 13:54, Gary Gregory >>>>>>>>>>> <mailto:garydgreg...@gmail.com>>
>>>>>>>>>> wrote:
>>>>>>>>>>>>> One critical feature is that dependabot does all the builds for 
>>>>>>>>>>>>> you
>>>>>>>>>> on
>>>>>>>>>>>>> GitHub Actions, this is an enormous time and resource saver!
>>>>>>>>>>>> Not at all.
>>>>>>>>>>>> Just the reverse.
>>>>>>>>>>>> 
>>>>>>>>>>>> It does NOT save resources, because it runs builds for updates that
>>>>>>>>>>>> are not necessary at that point in time (or ever, in some cases).
>>>>>>>>>>>> 
>>>>>>>>>>>> Nor does it same time, because the the noise that it generates.
>>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> Please stop pretending that Dependabot does things it does not (and
>>>>>>>>>>>> likely cannot) do.
>>>>>>>>>>>> 
>>>>>>>>>>> Oh, boy, Sebb, it feels like you are purposely misunderstanding my 
>>>>>>>>>>> POV.
>>>>>>>>>>> It's as simple as I stated:
>>>>>>>>>>> 
>>>>>

Re: can we get rid of dependabot?

2021-12-30 Thread Rob Tompkins



> On Dec 30, 2021, at 5:50 PM, Matt Sicker  wrote:
> 
> There are tons of options to configure. The defaults are handy for smaller 
> projects, but they are clearly spammy for larger ones like this.
> 
> https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates
>  
> <https://docs.github.com/en/code-security/supply-chain-security/keeping-your-dependencies-updated-automatically/configuration-options-for-dependency-updates>
> 

+1

> --
> Matt Sicker
> 
>>> On Dec 30, 2021, at 16:48, Rob Tompkins  wrote:
>>> 
>>> 
>>> 
>>>> On Dec 30, 2021, at 5:37 PM, sebb >>> <mailto:seb...@gmail.com>> wrote:
>>> 
>>> On Thu, 30 Dec 2021 at 21:39, Rob Tompkins >> <mailto:chtom...@gmail.com>> wrote:
>>>> 
>>>> Guys. The fundamental argument underpinng all this is whether it’s better 
>>>> to have robot eyes on the code and human eyes on the code. Stop arguing 
>>>> one side or the other. We need to find a way to do both successfully.
>>> 
>>> The issue is *not* about robot or no robot.
>>> 
>>> It is about this particular robot that causes so much noise.
>> 
>> Yes! That’s right so we need to figure out how to use the robot correctly!
>> 
>>> 
>>>> 
>>>> 
>>>>>> On Dec 29, 2021, at 1:57 PM, Phil Steitz >>>>> <mailto:phil.ste...@gmail.com>> wrote:
>>>>> 
>>>>> 
>>>>> 
>>>>>> On 12/29/21 8:43 AM, sebb wrote:
>>>>>>> On Wed, 29 Dec 2021 at 14:53, Gary Gregory >>>>>> <mailto:garydgreg...@gmail.com>> wrote:
>>>>>>>> On Wed, Dec 29, 2021 at 9:42 AM sebb >>>>>>> <mailto:seb...@gmail.com>> wrote:
>>>>>>> 
>>>>>>>> On Wed, 29 Dec 2021 at 14:18, Gary Gregory >>>>>>> <mailto:garydgreg...@gmail.com>> wrote:
>>>>>>>>> On Wed, Dec 29, 2021 at 9:07 AM sebb >>>>>>>> <mailto:seb...@gmail.com>> wrote:
>>>>>>>>> 
>>>>>>>>>> On Wed, 29 Dec 2021 at 13:54, Gary Gregory >>>>>>>>> <mailto:garydgreg...@gmail.com>>
>>>>>>>> wrote:
>>>>>>>>>>> One critical feature is that dependabot does all the builds for you
>>>>>>>> on
>>>>>>>>>>> GitHub Actions, this is an enormous time and resource saver!
>>>>>>>>>> Not at all.
>>>>>>>>>> Just the reverse.
>>>>>>>>>> 
>>>>>>>>>> It does NOT save resources, because it runs builds for updates that
>>>>>>>>>> are not necessary at that point in time (or ever, in some cases).
>>>>>>>>>> 
>>>>>>>>>> Nor does it same time, because the the noise that it generates.
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> Please stop pretending that Dependabot does things it does not (and
>>>>>>>>>> likely cannot) do.
>>>>>>>>>> 
>>>>>>>>> Oh, boy, Sebb, it feels like you are purposely misunderstanding my 
>>>>>>>>> POV.
>>>>>>>>> It's as simple as I stated:
>>>>>>>>> 
>>>>>>>>> If Dependabot detects that a new version of a dependency is available,
>>>>>>>>> creates a branch, runs a build, tells me the result and I have a PR I 
>>>>>>>>> can
>>>>>>>>> merge, *that is all work and time *I* do not have to do manually! Why 
>>>>>>>>> is
>>>>>>>>> that so hard to understand?*
>>>>>>>> Of course I understand that.
>>>>>>>> 
>>>>>>> Phew! :-)
>>>>>>> 
>>>>>>>> However, just because a new version is available does NOT mean that it
>>>>>>>> has to be updated there and then.
>>>>>>>> Sometimes it never needs to be updated.
>>>>>>>> 
>>>>>>> You can't know if you need to make a decision unless someone asks you to

Re: can we get rid of dependabot?

2021-12-30 Thread Rob Tompkins



> On Dec 30, 2021, at 5:37 PM, sebb  wrote:
> 
> On Thu, 30 Dec 2021 at 21:39, Rob Tompkins  wrote:
>> 
>> Guys. The fundamental argument underpinng all this is whether it’s better to 
>> have robot eyes on the code and human eyes on the code. Stop arguing one 
>> side or the other. We need to find a way to do both successfully.
> 
> The issue is *not* about robot or no robot.
> 
> It is about this particular robot that causes so much noise.

Yes! That’s right so we need to figure out how to use the robot correctly!

> 
>> 
>> 
>>>> On Dec 29, 2021, at 1:57 PM, Phil Steitz  wrote:
>>> 
>>> 
>>> 
>>>> On 12/29/21 8:43 AM, sebb wrote:
>>>>> On Wed, 29 Dec 2021 at 14:53, Gary Gregory  wrote:
>>>>>> On Wed, Dec 29, 2021 at 9:42 AM sebb  wrote:
>>>>> 
>>>>>> On Wed, 29 Dec 2021 at 14:18, Gary Gregory  
>>>>>> wrote:
>>>>>>> On Wed, Dec 29, 2021 at 9:07 AM sebb  wrote:
>>>>>>> 
>>>>>>>> On Wed, 29 Dec 2021 at 13:54, Gary Gregory 
>>>>>> wrote:
>>>>>>>>> One critical feature is that dependabot does all the builds for you
>>>>>> on
>>>>>>>>> GitHub Actions, this is an enormous time and resource saver!
>>>>>>>> Not at all.
>>>>>>>> Just the reverse.
>>>>>>>> 
>>>>>>>> It does NOT save resources, because it runs builds for updates that
>>>>>>>> are not necessary at that point in time (or ever, in some cases).
>>>>>>>> 
>>>>>>>> Nor does it same time, because the the noise that it generates.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> Please stop pretending that Dependabot does things it does not (and
>>>>>>>> likely cannot) do.
>>>>>>>> 
>>>>>>> Oh, boy, Sebb, it feels like you are purposely misunderstanding my POV.
>>>>>>> It's as simple as I stated:
>>>>>>> 
>>>>>>> If Dependabot detects that a new version of a dependency is available,
>>>>>>> creates a branch, runs a build, tells me the result and I have a PR I 
>>>>>>> can
>>>>>>> merge, *that is all work and time *I* do not have to do manually! Why is
>>>>>>> that so hard to understand?*
>>>>>> Of course I understand that.
>>>>>> 
>>>>> Phew! :-)
>>>>> 
>>>>>> However, just because a new version is available does NOT mean that it
>>>>>> has to be updated there and then.
>>>>>> Sometimes it never needs to be updated.
>>>>>> 
>>>>> You can't know if you need to make a decision unless someone asks you to
>>>>> make it. I don't know out of thin air that a new version is available.
>>>> You can be pro-active and do a dependency check yourself.
>>>> And you can look out for security bulletins.
>>>> 
>>>> That's what we used to do.
>>>> 
>>>>>> Changes to dependencies occur much more frequently than component 
>>>>>> releases.
>>>>>> So often there will be several mails for the same dependency.
>>>>>> 
>>>>>> In the past, the approach was to check for new (and useful) updates
>>>>>> shortly before a release.
>>>>>> 
>>>>> That must have been before my time and it seems like a horrible idea: The
>>>>> software is stable after a few months of activity and it's time to make a
>>>>> release, so the day before a release, you change all the dependencies, and
>>>>> cross your fingers? Yikes!
>>>> That is NOT what I said.
>>>> 
>>>> Obviously one would start working on version updates some time before
>>>> the release.
>>>> Days or weeks rather than months or years.
>>>> 
>>>>>> Generally all the versions would be updated at the same time, instead
>>>>>> of individually.
>>>>>> 
>>>>> Not here, if update 10 dependencies and a build fails, then what? I go 
>>>>> back
>>>>> to square one and update each, one at a time, until I find the culprit,
>>>>> which to me is a waste of time. BTW, 10 dependencies is n

Re: can we get rid of dependabot?

2021-12-30 Thread Rob Tompkins
Guys. The fundamental argument underpinng all this is whether it’s better to 
have robot eyes on the code and human eyes on the code. Stop arguing one side 
or the other. We need to find a way to do both successfully. 



> On Dec 29, 2021, at 1:57 PM, Phil Steitz  wrote:
> 
> 
> 
>> On 12/29/21 8:43 AM, sebb wrote:
>>> On Wed, 29 Dec 2021 at 14:53, Gary Gregory  wrote:
>>>> On Wed, Dec 29, 2021 at 9:42 AM sebb  wrote:
>>> 
>>>> On Wed, 29 Dec 2021 at 14:18, Gary Gregory  wrote:
>>>>> On Wed, Dec 29, 2021 at 9:07 AM sebb  wrote:
>>>>> 
>>>>>> On Wed, 29 Dec 2021 at 13:54, Gary Gregory 
>>>> wrote:
>>>>>>> One critical feature is that dependabot does all the builds for you
>>>> on
>>>>>>> GitHub Actions, this is an enormous time and resource saver!
>>>>>> Not at all.
>>>>>> Just the reverse.
>>>>>> 
>>>>>> It does NOT save resources, because it runs builds for updates that
>>>>>> are not necessary at that point in time (or ever, in some cases).
>>>>>> 
>>>>>> Nor does it same time, because the the noise that it generates.
>>>>>> 
>>>>>> 
>>>>>> Please stop pretending that Dependabot does things it does not (and
>>>>>> likely cannot) do.
>>>>>> 
>>>>> Oh, boy, Sebb, it feels like you are purposely misunderstanding my POV.
>>>>> It's as simple as I stated:
>>>>> 
>>>>> If Dependabot detects that a new version of a dependency is available,
>>>>> creates a branch, runs a build, tells me the result and I have a PR I can
>>>>> merge, *that is all work and time *I* do not have to do manually! Why is
>>>>> that so hard to understand?*
>>>> Of course I understand that.
>>>> 
>>> Phew! :-)
>>> 
>>>> However, just because a new version is available does NOT mean that it
>>>> has to be updated there and then.
>>>> Sometimes it never needs to be updated.
>>>> 
>>> You can't know if you need to make a decision unless someone asks you to
>>> make it. I don't know out of thin air that a new version is available.
>> You can be pro-active and do a dependency check yourself.
>> And you can look out for security bulletins.
>> 
>> That's what we used to do.
>> 
>>>> Changes to dependencies occur much more frequently than component releases.
>>>> So often there will be several mails for the same dependency.
>>>> 
>>>> In the past, the approach was to check for new (and useful) updates
>>>> shortly before a release.
>>>> 
>>> That must have been before my time and it seems like a horrible idea: The
>>> software is stable after a few months of activity and it's time to make a
>>> release, so the day before a release, you change all the dependencies, and
>>> cross your fingers? Yikes!
>> That is NOT what I said.
>> 
>> Obviously one would start working on version updates some time before
>> the release.
>> Days or weeks rather than months or years.
>> 
>>>> Generally all the versions would be updated at the same time, instead
>>>> of individually.
>>>> 
>>> Not here, if update 10 dependencies and a build fails, then what? I go back
>>> to square one and update each, one at a time, until I find the culprit,
>>> which to me is a waste of time. BTW, 10 dependencies is not unreasonable
>>> for components like VFS, Configuration, and others.
>> Well yes, but how likely is there to be a failure in such circumstances?
>> 
>> If the build does not fail, you have saved the noise from at least 9
>> updates which are generally 3 emails per update.
>> 
>> If it does fail, you will have wasted 2 cycles: the original commit of
>> 10, and the revert. And only 2 emails.
> 
> +1 and you will get many thanks from those trying to follow commits and 
> better review of the actual commits.  It seems badly broken to me that in 
> order to effectively review commits to the commons components that I watch I 
> have to write filters to ignore most of them.  The damage from making it 
> harder to review commits is far greater than the benefit this thing provides. 
>  Actual code commits are where bugs and vulnerabilities get introduced.  Just 
> like mixing formatting changes with functional code changes is a bad 
> practice, spamming commits@ with a bun

Re: can we get rid of dependabot?

2021-12-29 Thread Rob Tompkins
I still yet don’t see how thoughtful automation using dependabot doesn’t win 
out. 

So the idea behind using a double negative in a sentence like above, is to 
imply that there is more than just a “yes/no” answer to the question. There is 
the beginnings (a few choices) of a veritable continuum of possibilities using 
computers to help us here with our security. The question isn’t if we 
implement!!! It’s how* we implement. 

-Rob

> On Dec 29, 2021, at 10:44 AM, sebb  wrote:
> 
> On Wed, 29 Dec 2021 at 14:53, Gary Gregory  wrote:
>> 
>>> On Wed, Dec 29, 2021 at 9:42 AM sebb  wrote:
>>> 
>>> On Wed, 29 Dec 2021 at 14:18, Gary Gregory  wrote:
>>>> 
>>>> On Wed, Dec 29, 2021 at 9:07 AM sebb  wrote:
>>>> 
>>>>> On Wed, 29 Dec 2021 at 13:54, Gary Gregory 
>>> wrote:
>>>>>> 
>>>>>> One critical feature is that dependabot does all the builds for you
>>> on
>>>>>> GitHub Actions, this is an enormous time and resource saver!
>>>>> 
>>>>> Not at all.
>>>>> Just the reverse.
>>>>> 
>>>>> It does NOT save resources, because it runs builds for updates that
>>>>> are not necessary at that point in time (or ever, in some cases).
>>>>> 
>>>>> Nor does it same time, because the the noise that it generates.
>>>>> 
>>>>> 
>>>> 
>>>>> Please stop pretending that Dependabot does things it does not (and
>>>>> likely cannot) do.
>>>>> 
>>>> 
>>>> Oh, boy, Sebb, it feels like you are purposely misunderstanding my POV.
>>>> It's as simple as I stated:
>>>> 
>>>> If Dependabot detects that a new version of a dependency is available,
>>>> creates a branch, runs a build, tells me the result and I have a PR I can
>>>> merge, *that is all work and time *I* do not have to do manually! Why is
>>>> that so hard to understand?*
>>> 
>>> Of course I understand that.
>>> 
>> 
>> Phew! :-)
>> 
>>> 
>>> However, just because a new version is available does NOT mean that it
>>> has to be updated there and then.
>>> Sometimes it never needs to be updated.
>>> 
>> 
>> You can't know if you need to make a decision unless someone asks you to
>> make it. I don't know out of thin air that a new version is available.
> 
> You can be pro-active and do a dependency check yourself.
> And you can look out for security bulletins.
> 
> That's what we used to do.
> 
>> 
>>> 
>>> Changes to dependencies occur much more frequently than component releases.
>>> So often there will be several mails for the same dependency.
>>> 
>>> In the past, the approach was to check for new (and useful) updates
>>> shortly before a release.
>>> 
>> 
>> That must have been before my time and it seems like a horrible idea: The
>> software is stable after a few months of activity and it's time to make a
>> release, so the day before a release, you change all the dependencies, and
>> cross your fingers? Yikes!
> 
> That is NOT what I said.
> 
> Obviously one would start working on version updates some time before
> the release.
> Days or weeks rather than months or years.
> 
>> 
>>> Generally all the versions would be updated at the same time, instead
>>> of individually.
>>> 
>> 
>> Not here, if update 10 dependencies and a build fails, then what? I go back
>> to square one and update each, one at a time, until I find the culprit,
>> which to me is a waste of time. BTW, 10 dependencies is not unreasonable
>> for components like VFS, Configuration, and others.
> 
> Well yes, but how likely is there to be a failure in such circumstances?
> 
> If the build does not fail, you have saved the noise from at least 9
> updates which are generally 3 emails per update.
> 
> If it does fail, you will have wasted 2 cycles: the original commit of
> 10, and the revert. And only 2 emails.
> 
>> Gary
>> 
>> 
>>>> Gary
>>>> 
>>>> 
>>>>>> Gary
>>>>>> 
>>>>>> On Wed, Dec 29, 2021, 08:51 Rob Tompkins  wrote:
>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>>> On Dec 29, 2021, at 8:45 AM, Romain Manni-Bucau <
>>>>> rmannibu...@gmail.com>
>>>>>>> wrote:
>>>>>>>> 
>

Re: can we get rid of dependabot?

2021-12-29 Thread Rob Tompkins



> On Dec 29, 2021, at 10:29 AM, Matt Benson  wrote:
> 
> On Wed, Dec 29, 2021, 9:21 AM Mark Thomas  wrote:
> 
>>> On 29/12/2021 15:04, Gary Gregory wrote:
>>>> On Wed, Dec 29, 2021 at 9:37 AM Rob Tompkins  wrote:
>>> 
>>>> Why not just run dependabot weekly. We move slowly enough that weekly
>>>> currently works. Until we can get more hands on the project, slower
>> comms
>>>> are indeed reasonable…right?
>>>> 
>>> 
>>> I would be OK with it once a week.
>> 
>> I think the improvement resulting from moving to once a week will be
>> minimal.
>> 
>> I get the desire to keep things up to date but the way dependabot is
>> currently working creates a lot of traffic on both issues@ and commits@
>> That noise makes it much harder to follow any other activity that might
>> be happening in the project. I am finding it a lot more effort to keep
>> track of the Commons projects I am interested in.
>> 
>> Most commons libraries have very few "real" dependencies. Most of the
>> dependencies are there to support testing or building. I would argue
>> that updates to test/build libraries are far less critical and low risk
>> to update en masse just before a release.
>> 
>> I may look at applying local filters in the short term but that strikes
>> me very much as fixing the symptom rather than the cause and I don't
>> think it is efficient for every subscriber to have to do this if there
>> is an approach available that addresses the root cause.
>> 
>> As an aside, we also need to keep repeatable builds in mind. Simply
>> defining a version dependency as "latest" (or anything other than an
>> explicit version) is going to be problematic.
>> 
>> So, is there a way we could do something like the following with any
>> combination of dependabot and/or Versions Maven plugin and/or something
>> else?
>> 
>> - dependabot like behaviour (daily check, separate PR) for dependencies
>>   that are used (required or optional) at runtime
>> 
>> - a weekly (or even monthly?) check for test libraries, build tools etc.
>>   (i.e. everything that isn't a runtime dependency) that provides,
>>   ideally, a single PR with one commit per update
>> 
>> Emphasis on the "something like" the above.
>> 
> 

+1

> To jump into the discussion, I think these are sensible and constructive
> suggestions.
> 
> Matt
> 
> Mark
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: can we get rid of dependabot?

2021-12-29 Thread Rob Tompkins
Guys….let us blind our eyes to the source. We are taking about kicking our most 
excited contributor. Are we not? If dependabot were a person they would likely 
have gotten commit rights and be in the PMC. Granted, they’d have taken some 
advice and slowed down a bit and maybe with some steering we can accomplish 
just that. 

My last penny,
-Rob

> On Dec 29, 2021, at 9:53 AM, Gary Gregory  wrote:
> 
> On Wed, Dec 29, 2021 at 9:42 AM sebb  wrote:
> 
>>> On Wed, 29 Dec 2021 at 14:18, Gary Gregory  wrote:
>>> 
>>>> On Wed, Dec 29, 2021 at 9:07 AM sebb  wrote:
>>> 
>>>> On Wed, 29 Dec 2021 at 13:54, Gary Gregory 
>> wrote:
>>>>> 
>>>>> One critical feature is that dependabot does all the builds for you
>> on
>>>>> GitHub Actions, this is an enormous time and resource saver!
>>>> 
>>>> Not at all.
>>>> Just the reverse.
>>>> 
>>>> It does NOT save resources, because it runs builds for updates that
>>>> are not necessary at that point in time (or ever, in some cases).
>>>> 
>>>> Nor does it same time, because the the noise that it generates.
>>>> 
>>>> 
>>> 
>>>> Please stop pretending that Dependabot does things it does not (and
>>>> likely cannot) do.
>>>> 
>>> 
>>> Oh, boy, Sebb, it feels like you are purposely misunderstanding my POV.
>>> It's as simple as I stated:
>>> 
>>> If Dependabot detects that a new version of a dependency is available,
>>> creates a branch, runs a build, tells me the result and I have a PR I can
>>> merge, *that is all work and time *I* do not have to do manually! Why is
>>> that so hard to understand?*
>> 
>> Of course I understand that.
>> 
> 
> Phew! :-)
> 
>> 
>> However, just because a new version is available does NOT mean that it
>> has to be updated there and then.
>> Sometimes it never needs to be updated.
>> 
> 
> You can't know if you need to make a decision unless someone asks you to
> make it. I don't know out of thin air that a new version is available.
> 
> 
>> 
>> Changes to dependencies occur much more frequently than component releases.
>> So often there will be several mails for the same dependency.
>> 
>> In the past, the approach was to check for new (and useful) updates
>> shortly before a release.
>> 
> 
> That must have been before my time and it seems like a horrible idea: The
> software is stable after a few months of activity and it's time to make a
> release, so the day before a release, you change all the dependencies, and
> cross your fingers? Yikes!
> 
> 
>> Generally all the versions would be updated at the same time, instead
>> of individually.
>> 
> 
> Not here, if update 10 dependencies and a build fails, then what? I go back
> to square one and update each, one at a time, until I find the culprit,
> which to me is a waste of time. BTW, 10 dependencies is not unreasonable
> for components like VFS, Configuration, and others.
> 
> Gary
> 
> 
>>> Gary
>>> 
>>> 
>>>>> Gary
>>>>> 
>>>>> On Wed, Dec 29, 2021, 08:51 Rob Tompkins  wrote:
>>>>> 
>>>>>> 
>>>>>> 
>>>>>>> On Dec 29, 2021, at 8:45 AM, Romain Manni-Bucau <
>>>> rmannibu...@gmail.com>
>>>>>> wrote:
>>>>>>> 
>>>>>>> @Rob: dependabot is mainly about dependencies upgrades and it is
>>>> also
>>>>>> why
>>>>>>> it is so chatty and has so much false positives.
>>>>>> 
>>>>>> Yes, I am well aware. But I do not see how a robot telling you to
>>>> simply
>>>>>> upgrade is a problem?
>>>>>> 
>>>>>> Maybe I’m missing something but my impression is that’s what
>> dependabot
>>>>>> does right? Tell you you need to upgrade?
>>>>>> 
>>>>>> -Rob
>>>>>> 
>>>>>>> If you want to focus on
>>>>>>> CVE then setting up on the CI
>>>>>>> https://sonatype.github.io/ossindex-maven/maven-plugin/ is way
>> more
>>>>>>> efficient and accurate (basically when it fails you must act) so
>>>>>> dependabot
>>>>>>> is a great reporting tool for managers but not to work on an
>> everyday
>>>>>&g

Re: can we get rid of dependabot?

2021-12-29 Thread Rob Tompkins
Why not just run dependabot weekly. We move slowly enough that weekly currently 
works. Until we can get more hands on the project, slower comms are indeed 
reasonable…right?

-Rob

> On Dec 29, 2021, at 9:31 AM, Romain Manni-Bucau  wrote:
> 
> Saving dev/human resources is about having a CI, all mentionned plugins of
> the thread support it properly while cronned.
> Difference is the scope of the checks: CVE only, all deps, plugins and code
> (which is where most people don't like since it is trivial to have false
> positive and dependabot falls there).
> 
> I agree CVE are a crucial topic but dependabot is NOT done for them, it is
> done for dependencies as a whole and is full of bugs so until it is refined
> to be more relevant and bulked differently (maybe *1* mail a week) then it
> is not an option for an everyday work IMHO.
> 
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://rmannibucau.metawerx.net/> | Old Blog
> <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> <https://www.packtpub.com/application-development/java-ee-8-high-performance>
> 
> 
>> Le mer. 29 déc. 2021 à 15:18, Gary Gregory  a
>> écrit :
>> 
>>> On Wed, Dec 29, 2021 at 9:07 AM sebb  wrote:
>>> 
>>> On Wed, 29 Dec 2021 at 13:54, Gary Gregory 
>> wrote:
>>>> 
>>>> One critical feature is that dependabot does all the builds for you on
>>>> GitHub Actions, this is an enormous time and resource saver!
>>> 
>>> Not at all.
>>> Just the reverse.
>>> 
>>> It does NOT save resources, because it runs builds for updates that
>>> are not necessary at that point in time (or ever, in some cases).
>>> 
>>> Nor does it same time, because the the noise that it generates.
>>> 
>>> 
>> 
>>> Please stop pretending that Dependabot does things it does not (and
>>> likely cannot) do.
>>> 
>> 
>> Oh, boy, Sebb, it feels like you are purposely misunderstanding my POV.
>> It's as simple as I stated:
>> 
>> If Dependabot detects that a new version of a dependency is available,
>> creates a branch, runs a build, tells me the result and I have a PR I can
>> merge, *that is all work and time *I* do not have to do manually! Why is
>> that so hard to understand?*
>> 
>> Gary
>> 
>> 
>>>> Gary
>>>> 
>>>> On Wed, Dec 29, 2021, 08:51 Rob Tompkins  wrote:
>>>> 
>>>>> 
>>>>> 
>>>>>> On Dec 29, 2021, at 8:45 AM, Romain Manni-Bucau <
>>> rmannibu...@gmail.com>
>>>>> wrote:
>>>>>> 
>>>>>> @Rob: dependabot is mainly about dependencies upgrades and it is
>>> also
>>>>> why
>>>>>> it is so chatty and has so much false positives.
>>>>> 
>>>>> Yes, I am well aware. But I do not see how a robot telling you to
>>> simply
>>>>> upgrade is a problem?
>>>>> 
>>>>> Maybe I’m missing something but my impression is that’s what
>> dependabot
>>>>> does right? Tell you you need to upgrade?
>>>>> 
>>>>> -Rob
>>>>> 
>>>>>> If you want to focus on
>>>>>> CVE then setting up on the CI
>>>>>> https://sonatype.github.io/ossindex-maven/maven-plugin/ is way
>> more
>>>>>> efficient and accurate (basically when it fails you must act) so
>>>>> dependabot
>>>>>> is a great reporting tool for managers but not to work on an
>> everyday
>>>>> basis
>>>>>> IMHO until it is very finely configure but commons is far to need
>> so
>>> much
>>>>>> investment since there already have solutions for everything needed
>>> IMHO.
>>>>>> 
>>>>>> Romain Manni-Bucau
>>>>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>>>>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>>>>> <http://rmannibucau.wordpress.com> | Github <
>>>>> https://github.com/rmannibucau> |
>>>>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>>>>>> <
>>>>> 
>>> 
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>>>>>> 
>>>&g

Re: can we get rid of dependabot?

2021-12-29 Thread Rob Tompkins



> On Dec 29, 2021, at 8:54 AM, Gary Gregory  wrote:
> 
> One critical feature is that dependabot does all the builds for you on
> GitHub Actions, this is an enormous time and resource saver!
> 

Ding ding ding ding….we have a winner. We just don’t yet know how to implement. 



> Gary
> 
>> On Wed, Dec 29, 2021, 08:51 Rob Tompkins  wrote:
>> 
>> 
>> 
>>> On Dec 29, 2021, at 8:45 AM, Romain Manni-Bucau 
>> wrote:
>>> 
>>> @Rob: dependabot is mainly about dependencies upgrades and it is also
>> why
>>> it is so chatty and has so much false positives.
>> 
>> Yes, I am well aware. But I do not see how a robot telling you to simply
>> upgrade is a problem?
>> 
>> Maybe I’m missing something but my impression is that’s what dependabot
>> does right? Tell you you need to upgrade?
>> 
>> -Rob
>> 
>>> If you want to focus on
>>> CVE then setting up on the CI
>>> https://sonatype.github.io/ossindex-maven/maven-plugin/ is way more
>>> efficient and accurate (basically when it fails you must act) so
>> dependabot
>>> is a great reporting tool for managers but not to work on an everyday
>> basis
>>> IMHO until it is very finely configure but commons is far to need so much
>>> investment since there already have solutions for everything needed IMHO.
>>> 
>>> Romain Manni-Bucau
>>> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
>>> <https://rmannibucau.metawerx.net/> | Old Blog
>>> <http://rmannibucau.wordpress.com> | Github <
>> https://github.com/rmannibucau> |
>>> LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
>>> <
>> https://www.packtpub.com/application-development/java-ee-8-high-performance
>>> 
>>> 
>>> 
>>>> Le mer. 29 déc. 2021 à 14:39, Rob Tompkins  a
>> écrit :
>>>> 
>>>> Guys. I think dependabot is our greatest advantage in the work against
>>>> security problems. I know she has her failings and is chatty. But, I
>> think
>>>> we should open a line of thinking about how best she can help.
>>>> 
>>>> The reason she’s a pain in the ass is that we don’t have enough hands on
>>>> the project making it better. I know I would help more, but I have to
>> keep
>>>> up with my father who’s a quadriplegic as well as a currently failing
>>>> marriage.
>>>> 
>>>> The answer is that we need more hands on the project. I wish I could be
>>>> those hands but time and priorities keep me chained.
>>>> 
>>>> Cheers,
>>>> -Rob
>>>> 
>>>>> On Dec 29, 2021, at 8:26 AM, Gilles Sadowski 
>>>> wrote:
>>>>> 
>>>>> Le mer. 29 déc. 2021 à 12:18, Thomas Vandahl  a écrit
>> :
>>>>>> 
>>>>>> +1
>>>>>> Thank you, Phil. This thing is a P.I.T.A.
>>>>> 
>>>>> In effect, from day one:
>>>>> https://markmail.org/message/2vutc4p3b3eqv73f
>>>>> 
>>>>> Basically, the argument is that
>>>>> * the (dependabot) feature is too important to be disabled
>>>>> * the annoyed people should filter out those mails (which I
>>>>> did since no one at the time supported that they be diverted
>>>>> to another ML).
>>>>> Did anything change since then?
>>>>> [Or do we eventually question the general anomaly that code
>>>>> discussions have been almost completely off-loaded to GH?]
>>>>> 
>>>>> Gilles
>>>>> 
>>>>>> 
>>>>>>>> Am 28.12.2021 um 19:20 schrieb Phil Steitz :
>>>>>>> 
>>>>>>> I can no longer effectively monitor commits@ due to the spam
>>>> generated by this tool.  I am afraid my eyeballs aren't the only ones
>> going
>>>> missing here and that is a problem much more severe than any value
>> provided
>>>> by this tool, IMO.
>>>>>>> 
>>>>>>> Phil
>>>>>> 
>>>>>> Bye, Thomas
>>>>> 
>>>>> -
>>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>>> 
>>>> 
>>>> -
>>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>> 
>>>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: can we get rid of dependabot?

2021-12-29 Thread Rob Tompkins
Guys. I think dependabot is our greatest advantage in the work against security 
problems. I know she has her failings and is chatty. But, I think we should 
open a line of thinking about how best she can help. 

The reason she’s a pain in the ass is that we don’t have enough hands on the 
project making it better. I know I would help more, but I have to keep up with 
my father who’s a quadriplegic as well as a currently failing marriage. 

The answer is that we need more hands on the project. I wish I could be those 
hands but time and priorities keep me chained. 

Cheers,
-Rob

> On Dec 29, 2021, at 8:26 AM, Gilles Sadowski  wrote:
> 
> Le mer. 29 déc. 2021 à 12:18, Thomas Vandahl  a écrit :
>> 
>> +1
>> Thank you, Phil. This thing is a P.I.T.A.
> 
> In effect, from day one:
>   https://markmail.org/message/2vutc4p3b3eqv73f
> 
> Basically, the argument is that
> * the (dependabot) feature is too important to be disabled
> * the annoyed people should filter out those mails (which I
> did since no one at the time supported that they be diverted
> to another ML).
> Did anything change since then?
> [Or do we eventually question the general anomaly that code
> discussions have been almost completely off-loaded to GH?]
> 
> Gilles
> 
>> 
 Am 28.12.2021 um 19:20 schrieb Phil Steitz :
>>> 
>>> I can no longer effectively monitor commits@ due to the spam generated by 
>>> this tool.  I am afraid my eyeballs aren't the only ones going missing here 
>>> and that is a problem much more severe than any value provided by this 
>>> tool, IMO.
>>> 
>>> Phil
>> 
>> Bye, Thomas
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: can we get rid of dependabot?

2021-12-29 Thread Rob Tompkins



> On Dec 28, 2021, at 1:57 PM, Gary Gregory  wrote:
> 
> Please no. Dependabot is a key tool for me. Inbox rules should be able to
> help you depending on your client.

Huge +1

I think we need to help GitHub figure out how to make it better. 

-Rob

> 
> Someone had suggested creating a new mailing lists for bots/tools a while
> back but it never happened.
> 
> Gary
> 
>> On Tue, Dec 28, 2021 at 1:20 PM Phil Steitz  wrote:
>> 
>> I can no longer effectively monitor commits@ due to the spam generated
>> by this tool.  I am afraid my eyeballs aren't the only ones going
>> missing here and that is a problem much more severe than any value
>> provided by this tool, IMO.
>> 
>> Phil
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



[ANNOUNCE] Apache Commons CLI 1.5.0

2021-10-29 Thread Rob Tompkins
The Apache Commons project announces the release of Apache Commons CLI 1.5.0.


Commons CLI requires at least Java 8.


The Apache Commons CLI library provides a simple command Line arguments parser.


This is a Feature and bug fix release (Java 8)


Historical list of changes:
https://commons.apache.org/proper/commons-cli/changes-report.html


For complete information on Apache Commons CLI, including instructions on
how to submit bug reports, patches, or suggestions for improvement, see the
Apache Apache Commons CLI website:


https://commons.apache.org/proper/commons-cli/


Download page:
https://commons.apache.org/proper/commons-cli/download_cli.cgi


Have fun!
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



[ANNOUNCE] Apache Commons CLI 1.5.0

2021-10-29 Thread Rob Tompkins
The Apache Commons project announces the release of Apache Commons CLI
1.5.0.


Commons CLI requires at least Java 8.


The Apache Commons CLI library provides a simple command Line arguments parser.


This is a Feature and bug fix release (Java 8)


Historical list of changes:
https://commons.apache.org/proper/commons-cli/changes-report.html


For complete information on Apache Commons CLI, including instructions on
how to submit bug reports, patches, or suggestions for improvement, see the
Apache Apache Commons CLI website:


https://commons.apache.org/proper/commons-cli/


Download page:
https://commons.apache.org/proper/commons-cli/download_csv.cgi


Have fun!
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



[ALL, SITE] Publishing Main Website

2021-10-28 Thread Rob Tompkins
Hello all,

In going through the CLI release of 1.5.0 (most of which I’ve finished), I 
needed to publish the main site. In following the standard directions [1], I’ve 
made the requisite commits to SVN, but I just don’t know how to publish the 
code out to the site. Note, I used to use the cms application that existed on 
top of the svn repository. I’m curious if I could just use mvn site-deploy to 
get it to work (I tried this but it didn’t), or if anyone (maily asking Sebb 
here) could steer me in the correct direction for top level site updates.

Many thanks and all the best,
-Rob


[1] http://commons.apache.org/site-publish.html
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



[RESULT][VOTE] Release Apache Commons CLI 1.5.0 based on RC1

2021-10-27 Thread Rob Tompkins
Hello all,

This vote passes with the following votes:

Gary Gregory: +1
Bruno Kinoshita: +1
Rob Tompkins: +1

I’ll go ahead work through the promotion process today. Many thanks to those 
that voted on the RC.

Cheers,
-Rob

> On Oct 23, 2021, at 5:58 PM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons CLI 1.4 was released, so I would like to release Apache 
> Commons CLI 1.5.0.
> 
> Apache Commons CLI 1.5.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1 (svn revision 
> 50583)
> 
> The Git tag commons-cli-1.5.0-RC1 commit for this RC is 
> e81a871025cd2dd5bc1d3b473c3c495533e7b8f4 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=e81a871025cd2dd5bc1d3b473c3c495533e7b8f4
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-cli.git --branch 
> commons-cli-1.5.0-RC1 commons-cli-1.5.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1573/org/apache/commons/commons-cli/1.5.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Oct 23 17:47:54 EDT 2021
> commons-cli-1.5.0-bin.tar.gz=7d952d49f1899f5f7ceca28f806730013b93004d852dcf3f3ce0149e932fdc387bc289c22f6f9e52835611813571925f0c8563cc11e2aebf5a1597c8be7d
> commons-cli-1.5.0-bin.tar.gz.asc=d77f4776d6380a6618d5c850fe944ffa2d4b1277f5d6bcfeb38088a42d52492c189bfd3d8670e2bd5bdd171039b460a3575018de2afc633609fe55b51d75e66d
> commons-cli-1.5.0-bin.zip=216d8b1f4c3e6b6337a820ce0296a29982664c230139ec5d8a2c1c554c205e2cc8584c3e7bee43eebe042b3731454f6c5caa9bff87a54c9e3955a955f99d5ee1
> commons-cli-1.5.0-bin.zip.asc=00556819fd85478d939c7bd4cb72b13f2f4f1578dcbfb64e7c4a64d42bd06c4ed7b0c4e4892d42a2816fb38e6a4609a72cc2dcbbb3d36b5b91bd6963e3bd9a6d
> commons-cli-1.5.0-javadoc.jar=332eec1017e8f7dfee218426414df9e45428f2458629728aace8a2fac3afaf0aab64467eda1f1d6d075a7c8abf06bf39f0cb3f1e6b1c9e45f53deb0ed595063b
> commons-cli-1.5.0-javadoc.jar.asc=ceba76dc81d26f14a36ba4e8f00ea3a50e2cf828ba91b5303f369dc0b876bc1e1141a3279df6345209f042f4cdd68b80f7447448f63e004b1ddedf30cbe45782
> commons-cli-1.5.0-sources.jar=21045e9ec71c420a9eba3539ed96bf349e9053f6cc7f0d1a67ed40a699b37993bbb0c7b8b9a97ea88625f2235da23275533ab7ac8cde9111f72f7314369dc132
> commons-cli-1.5.0-sources.jar.asc=a5ff72e46e99affb7ea6caecb525ed4f1a3079e7b9e061bf5902f96e1bf4ef7ac4de54c16605e3dd4686b81bdd212ea83f0d632a126063c82dde300af2676c72
> commons-cli-1.5.0-src.tar.gz=aa2165695177c3e4561f68585cafb5434758138d8a863f3db1860477f660cf78664d2afb07cc3bc767bc8fa87befc7eaa5bdead423ee8b883c62ff00aec7cdda
> commons-cli-1.5.0-src.tar.gz.asc=619b1d3105fffa9841a0f551da482374c276245ff6aec58bb6d4d175146fe3d841c722cd5a8c13e9a686628cd0729c133ece266574b04a042cf7bfa4675b5bda
> commons-cli-1.5.0-src.zip=de9dcb3d9a1cb65279b1d9604ce61e3522d661e024dd8062c811b07a52761c0a0e2290a01ef91276c8a2155cdb94e05d1f6c76557c29fc2c743b9196731b914b
> commons-cli-1.5.0-src.zip.asc=f4ee644ac50636182a39cf2ee700e91eb46f340ae2772d51c4764a4e85da3fe02703b8391fb11f386cf6ed25ab24a5e2b91ca7e62506659574b4ae5010a52039
> commons-cli-1.5.0-test-sources.jar=23ade4f439e5de53e1b654b27a4857e91c261d25a62fcf833227055d4dbf7f7aad06a6e63b7fb043870a6911e3dfda74c4acd4b671860293f96cc3e41fde2d2f
> commons-cli-1.5.0-test-sources.jar.asc=a1aaf3a4ca273a8ecf2b619faf63cc917568f9e6bbcb1fcedf816dd39f30567638dd272441e1feb8c02d7a9692265b43075bfd01ea7e449dfe8e38dfde31bb14
> commons-cli-1.5.0-tests.jar=d6c01aa748dab3747ebb28f675ed0395bfe41d73c9ddf6fd1968f80b1b3edd769e0fa01ac800bd378319bfb03dd9df74dafe51f4a870338c4c9ff841589cf999
> commons-cli-1.5.0-tests.jar.asc=04025ee90f190200b7e07433362d0da45cea23d21590aa1d75c0134159c3ce90ecc6df2f0ada47ca7a52af21e849a657c16d5402e90a4c24730cf874412d61ba
> commons-cli-1.5.0.jar.asc=d1bcc1690ca026bc4f8709c6a7544818e6c4b6348beb13ee0c7f0d5f7255f3e403349e63a74ac18c3ba4885db1518f841a93dcdd42d9f755663fd717ad25
> commons-cli-1.5.0.pom.asc=68a82edaae73a71740624dad1466e2101f5b1152c7bea2cd315fb6ed249a59998afdd270706f760453dd5f047caeb8f91c6304610a8687379d2b689450e477d3
> 
> 
> (no need for .asc hashes!)
> 
> I have tested this with ***'mvn clean install site'*** using: 
> ***
> Use the output from "mvn -version" for each combination you tested.
> ***
> 
> Details of changes since 1.4 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.5.0 directories are not 
> yet created - t

Re: [VOTE] Release Apache Commons CLI 1.5.0 based on RC1

2021-10-27 Thread Rob Tompkins
Here’s my +1.

-Rob

> On Oct 23, 2021, at 5:58 PM, Rob Tompkins  wrote:
> 
> We have fixed quite a few bugs and added some significant enhancements since 
> Apache Commons CLI 1.4 was released, so I would like to release Apache 
> Commons CLI 1.5.0.
> 
> Apache Commons CLI 1.5.0 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1 (svn revision 
> 50583)
> 
> The Git tag commons-cli-1.5.0-RC1 commit for this RC is 
> e81a871025cd2dd5bc1d3b473c3c495533e7b8f4 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-cli.git;a=commit;h=e81a871025cd2dd5bc1d3b473c3c495533e7b8f4
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-cli.git --branch 
> commons-cli-1.5.0-RC1 commons-cli-1.5.0-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1573/org/apache/commons/commons-cli/1.5.0/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Oct 23 17:47:54 EDT 2021
> commons-cli-1.5.0-bin.tar.gz=7d952d49f1899f5f7ceca28f806730013b93004d852dcf3f3ce0149e932fdc387bc289c22f6f9e52835611813571925f0c8563cc11e2aebf5a1597c8be7d
> commons-cli-1.5.0-bin.tar.gz.asc=d77f4776d6380a6618d5c850fe944ffa2d4b1277f5d6bcfeb38088a42d52492c189bfd3d8670e2bd5bdd171039b460a3575018de2afc633609fe55b51d75e66d
> commons-cli-1.5.0-bin.zip=216d8b1f4c3e6b6337a820ce0296a29982664c230139ec5d8a2c1c554c205e2cc8584c3e7bee43eebe042b3731454f6c5caa9bff87a54c9e3955a955f99d5ee1
> commons-cli-1.5.0-bin.zip.asc=00556819fd85478d939c7bd4cb72b13f2f4f1578dcbfb64e7c4a64d42bd06c4ed7b0c4e4892d42a2816fb38e6a4609a72cc2dcbbb3d36b5b91bd6963e3bd9a6d
> commons-cli-1.5.0-javadoc.jar=332eec1017e8f7dfee218426414df9e45428f2458629728aace8a2fac3afaf0aab64467eda1f1d6d075a7c8abf06bf39f0cb3f1e6b1c9e45f53deb0ed595063b
> commons-cli-1.5.0-javadoc.jar.asc=ceba76dc81d26f14a36ba4e8f00ea3a50e2cf828ba91b5303f369dc0b876bc1e1141a3279df6345209f042f4cdd68b80f7447448f63e004b1ddedf30cbe45782
> commons-cli-1.5.0-sources.jar=21045e9ec71c420a9eba3539ed96bf349e9053f6cc7f0d1a67ed40a699b37993bbb0c7b8b9a97ea88625f2235da23275533ab7ac8cde9111f72f7314369dc132
> commons-cli-1.5.0-sources.jar.asc=a5ff72e46e99affb7ea6caecb525ed4f1a3079e7b9e061bf5902f96e1bf4ef7ac4de54c16605e3dd4686b81bdd212ea83f0d632a126063c82dde300af2676c72
> commons-cli-1.5.0-src.tar.gz=aa2165695177c3e4561f68585cafb5434758138d8a863f3db1860477f660cf78664d2afb07cc3bc767bc8fa87befc7eaa5bdead423ee8b883c62ff00aec7cdda
> commons-cli-1.5.0-src.tar.gz.asc=619b1d3105fffa9841a0f551da482374c276245ff6aec58bb6d4d175146fe3d841c722cd5a8c13e9a686628cd0729c133ece266574b04a042cf7bfa4675b5bda
> commons-cli-1.5.0-src.zip=de9dcb3d9a1cb65279b1d9604ce61e3522d661e024dd8062c811b07a52761c0a0e2290a01ef91276c8a2155cdb94e05d1f6c76557c29fc2c743b9196731b914b
> commons-cli-1.5.0-src.zip.asc=f4ee644ac50636182a39cf2ee700e91eb46f340ae2772d51c4764a4e85da3fe02703b8391fb11f386cf6ed25ab24a5e2b91ca7e62506659574b4ae5010a52039
> commons-cli-1.5.0-test-sources.jar=23ade4f439e5de53e1b654b27a4857e91c261d25a62fcf833227055d4dbf7f7aad06a6e63b7fb043870a6911e3dfda74c4acd4b671860293f96cc3e41fde2d2f
> commons-cli-1.5.0-test-sources.jar.asc=a1aaf3a4ca273a8ecf2b619faf63cc917568f9e6bbcb1fcedf816dd39f30567638dd272441e1feb8c02d7a9692265b43075bfd01ea7e449dfe8e38dfde31bb14
> commons-cli-1.5.0-tests.jar=d6c01aa748dab3747ebb28f675ed0395bfe41d73c9ddf6fd1968f80b1b3edd769e0fa01ac800bd378319bfb03dd9df74dafe51f4a870338c4c9ff841589cf999
> commons-cli-1.5.0-tests.jar.asc=04025ee90f190200b7e07433362d0da45cea23d21590aa1d75c0134159c3ce90ecc6df2f0ada47ca7a52af21e849a657c16d5402e90a4c24730cf874412d61ba
> commons-cli-1.5.0.jar.asc=d1bcc1690ca026bc4f8709c6a7544818e6c4b6348beb13ee0c7f0d5f7255f3e403349e63a74ac18c3ba4885db1518f841a93dcdd42d9f755663fd717ad25
> commons-cli-1.5.0.pom.asc=68a82edaae73a71740624dad1466e2101f5b1152c7bea2cd315fb6ed249a59998afdd270706f760453dd5f047caeb8f91c6304610a8687379d2b689450e477d3
> 
> 
> (no need for .asc hashes!)
> 
> I have tested this with ***'mvn clean install site'*** using: 
> ***
> Use the output from "mvn -version" for each combination you tested.
> ***
> 
> Details of changes since 1.4 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/index.html
>(note some *relative* links are broken and the 1.5.0 directories are not 
> yet created - these will be OK once the site is deployed.)
> 
> CLIRR Report (compared to 1.4):
>
> https://dist.apache.org/repos/dist/dev/commons/cli/1.5.0-RC1/site/clirr-report.html
> 
> JApiCmp R

[VOTE] Release Apache Commons CLI 1.5.0 based on RC1

2021-10-23 Thread Rob Tompkins
- etc.
***

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/cli/1.5.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 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,

Rob Tompkins, 
Release Manager (using key B6E73D84EA4FCC47166087253FAAD2CD5ECBB314)

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-cli.git --branch 
commons-cli-1.5.0-RC1 commons-cli-1.5.0-RC1
cd commons-cli-1.5.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

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


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [CLI] release soon

2021-10-19 Thread Rob Tompkins
Gotcha. Thanks for the heads up. 

Cheers,
-Rob

> On Oct 19, 2021, at 7:38 AM, Gary Gregory  wrote:
> 
> Hi All,
> 
> I intend to create a release candidate for CLI 1.5 soon. This will be the
> last Java 7 release IMO and I plan on this being a simple kinde of release,
> no big new feature. Feel free to look at Jira.
> 
> Beyond that, the snapshot POM can go to Java 8.
> 
> I am not sure if CLI has a future without a ton of work considering the
> feature gap with other FOSS projects like JCommander and Picocli.
> 
> Gary
> 
> 
> Gary

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: Top Contributor in the Commons PMC

2021-09-07 Thread Rob Tompkins
+1 for Gary. 

being in the top 5 overall at Apache is super impressive! Congrats man!

-Rob

> On Sep 3, 2021, at 12:38 PM, Matt Juntunen  wrote:
> 
> I second this congratulations. Thank you for all of your hard work!
> 
> -Matt J
> 
> On Fri, Sep 3, 2021 at 8:46 AM Gary Gregory  wrote:
>> 
>> If only quantity was equivalent to quality ;-)
>> 
>> Thanks Bernd :-)
>> 
>> Gary
>> 
>> 
>> On Tue, Aug 31, 2021, 11:44 Bernd Eckenfels  wrote:
>> 
>>> Congrats Gary to be recognized as a top committer and top (mail) sender in
>>> the recent ASF Report ,)
>>> 
>>> https://s.apache.org/FY2021AnnualReport
>>> 
>>> Gruss
>>> Bernd
>>> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org



Re: [VOTE] Release Apache Commons Pool 2.11.1 based on RC1

2021-08-16 Thread Rob Tompkins
Validates out succesfully +1

> On Aug 14, 2021, at 10:13 AM, Gary Gregory  wrote:
> 
> We have fixed a few regression bugs since Apache Commons Pool 2.11.0
> was released and performed some internal cleanups, so I would like to
> release Apache Commons Pool 2.11.1.
> 
> Apache Commons Pool 2.11.1 RC1 is available for review here:
>https://dist.apache.org/repos/dist/dev/commons/pool/2.11.1-RC1
> (svn revision 49499)
> 
> The Git tag commons-pool-2.11.1-RC1 commit for this RC is
> abb1a0797b406566f0214c688871ab7e8fdc2601 which you can browse here:
>
> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=abb1a0797b406566f0214c688871ab7e8fdc2601
> You may checkout this tag using:
>git clone https://gitbox.apache.org/repos/asf/commons-pool.git
> --branch commons-pool-2.11.1-RC1 commons-pool-2.11.1-RC1
> 
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-1563/org/apache/commons/commons-pool2/2.11.1/
> 
> These are the artifacts and their hashes:
> 
> #Release SHA-512s
> #Sat Aug 14 09:59:47 EDT 2021
> commons-pool2-2.11.1-bin.tar.gz=04da8f6ab10df0d3bf8d458ae9c8810c55f99dd6ad5e1a98ed084adbdc09c99114985cc4311c0f3e336c01a7e3569d9311712a8a8e5144fab94a17d5b33c7dbc
> commons-pool2-2.11.1-bin.zip=b6a4fdf8bf0368372ca57d741542e842339ff6f2a5ba452b1179e9a6cf139224169100593be166d655d0d1d04be596822fc72a0086b9d585421db628d1898091
> commons-pool2-2.11.1-javadoc.jar=cff2a69aa7b2864fb813adce2ff8c05a89a5e2d979bc8f213f2cc987f99ef9b4f0050ef91d9ecb5270fa17e42afc77f292b5725a7419b46bf60eacad3286f771
> commons-pool2-2.11.1-sources.jar=e7b2d88c3e17d7be9e0c39215912516381ef46d141f2f17797bbcfc01da61b41d549f91767e856a32c00e227e78e4d23fe02f23903b3a470656f0a24175a973b
> commons-pool2-2.11.1-src.tar.gz=5550418757f6614e00af54aa9483c46a25b2f92f207c90c6dbea0269dd318a80f55a62c7348076bd7719fc948b778a35c952d4f92e7a43e8b1d0bc76e06e92a0
> commons-pool2-2.11.1-src.zip=bc75da13acb020096b871b461fd4b9112917cd3b3c3bc0e45cd74b808796ce6f89863aafffcec025ee07d9ac04e4d4f738977220bbb1107f24621011cfede708
> commons-pool2-2.11.1-test-sources.jar=ba3ef9fcbb8b25cb18de9b28322fe888c3b1e78cb845787f667c691b7ad0f7d25314c2eaceca542a50e77c0e0960be0344fef6501ddef55c3a3e66a966c57e6b
> commons-pool2-2.11.1-tests.jar=1fbdfda9ecd8917e18c06d9a48dd5d139449b8c9ae3b64fc1655f642d27853d73989edea9630e9bd50466afba91b9adc29138a0fcb996eb05ffd30d506112236
> 
> 
> I have tested this with
> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site deploy
> 
> using:
> Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
> Maven home: /usr/local/Cellar/maven/3.8.1/libexec
> Java version: 1.8.0_292, 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.16", arch: "x86_64", family: "mac"
> 
> Darwin xxx.local 20.6.0 Darwin Kernel Version 20.6.0: Wed Jun 23
> 00:26:31 PDT 2021; root:xnu-7195.141.2~5/RELEASE_X86_64 x86_64
> 
> Details of changes since 2.11.0 are in the release notes:
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.1-RC1/RELEASE-NOTES.txt
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.1-RC1/site/changes-report.html
> 
> Site:
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.1-RC1/site/index.html
>(note some *relative* links are broken and the 2.11.1 directories
> are not yet created - these will be OK once the site is deployed.)
> 
> JApiCmp Report (compared to 2.11.0):
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.1-RC1/site/japicmp.html
>You'll note two "new" public APIs in DefaultPooledObject that are
> just overrides, which is why this version is 2.11.1 and not 2.12.0.
> 
> RAT Report:
>
> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.1-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-pool.git
> --branch commons-pool-2.11.1-RC1 commons-pool-2.11.1-RC1
> cd commons-pool-2.11.1-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 

Re: [VOTE] Release Apache Commons Pool 2.11.0 based on RC1

2021-08-11 Thread Rob Tompkins
+1 signatures good, builds on 8 and 11, rat good reports good.

send it :-)

> On Aug 11, 2021, at 5:45 PM, Gary Gregory  wrote:
> 
> May I get at least one more PMC review please?
> 
> Gary
> 
> On Sun, Aug 8, 2021, 18:12 Gary Gregory  wrote:
> 
>> We have fixed a few bugs and added some enhancements since Apache
>> Commons Pool 2.10.0 was released, so I would like to release Apache
>> Commons Pool 2.11.0.
>> 
>> Apache Commons Pool 2.11.0 RC1 is available for review here:
>>https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1
>> (svn revision 49387)
>> 
>> The Git tag commons-pool-2.11.0-RC1 commit for this RC is
>> b94e8bec1a056e2784799cba51c79bc3b801d4cd which you can browse here:
>> 
>> https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=b94e8bec1a056e2784799cba51c79bc3b801d4cd
>> You may checkout this tag using:
>>git clone https://gitbox.apache.org/repos/asf/commons-pool.git
>> --branch 
>> commons-pool-2.11.0-RC1 commons-pool-2.11.0-RC1
>> 
>> Maven artifacts are here:
>> 
>> https://repository.apache.org/content/repositories/orgapachecommons-1560/org/apache/commons/commons-pool2/2.11.0/
>> 
>> These are the artifacts and their hashes:
>> 
>> #Release SHA-512s
>> #Sun Aug 08 17:25:31 EDT 2021
>> 
>> commons-pool2-2.11.0-bin.tar.gz=e3fd5e2841ea5d357b875c2bf669b7f903e0c8914e45bd40ffbfe28ea9fe48a995b0c80a1d4a9e859b8bc9f69c0544701c302bfed6903e5a647a5ae388b17bac
>> 
>> commons-pool2-2.11.0-bin.zip=a9c500bff6d014e0ee0ab49c410e66c3777c55ae94c4490c3125bd7e0bb92ee55fc8067e7d8ecaecd1ac467c201ef1aae3dc73751bfb9bc94ec620dab7f48862
>> 
>> commons-pool2-2.11.0-javadoc.jar=e1c253021b5980bafb4ff11fd2f0dc46752c24d37b6b4b363ddd5ef1c8bd6e70c4b27b0ad95759d2102efb4d3f42128ec248809e11a977a39ebc55f8fd032619
>> 
>> commons-pool2-2.11.0-sources.jar=336ae1927ed517c8168ae3c85dd8b84eb45d46288fba3e64b324accbe07f1b8fd44eded3a5f62c36e0280f444a91a6659722e47149c926a8a4ecdf3bb7a6c53e
>> 
>> commons-pool2-2.11.0-src.tar.gz=1316ed17d3bb11f8fa15733dd79a09c9d117ed2410b2854ce72067fd5ea1ccde5612a2f3246d857d55913ddf81db6c03e94a0d17a05e8bfd11b045c982e3d40a
>> 
>> commons-pool2-2.11.0-src.zip=30686059d9932f75d413cdb93c6333ccbf432dd7864f3075981d1721ee87642c7b481fe84fd1fd3d075acf469f939ad4a753384177cafcd5bd90af722b0c34bb
>> 
>> commons-pool2-2.11.0-test-sources.jar=d983d4a97362cc74bdca1987697e482431e2f84ecc8943b8e1c1cc20a82e889b4d2b5aac57708fbafdcaa00a1fb6f135bd94072c7c956f0275d7a925a27396fc
>> 
>> commons-pool2-2.11.0-tests.jar=62a9b7d5a2f67933d72479efe59974578ed8eaf58a4be449aea6014fe9c0063cb1a7aca974eb45f9e69b4b0b495a01396aedd622a053f8c2d504b6efe64ef61c
>> 
>> I have tested this with
>> 
>> mvn -V -Prelease -Ptest-deploy -P jacoco -P japicmp clean package site
>> deploy
>> 
>> using:
>> 
>> Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
>> Maven home: /usr/local/Cellar/maven/3.8.1/libexec
>> Java version: 1.8.0_292, 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.16", arch: "x86_64", family: "mac"
>> 
>> Details of changes since 2.10.0 are in the release notes:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/RELEASE-NOTES.txt
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/site/changes-report.html
>> 
>> Site:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/site/index.html
>>(note some *relative* links are broken and the 2.11.0 directories
>> are not yet created - these will be OK once the site is deployed.)
>> 
>> JApiCmp Report (compared to 2.10.0):
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.0-RC1/site/japicmp.html
>> 
>> RAT Report:
>> 
>> https://dist.apache.org/repos/dist/dev/commons/pool/2.11.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-pool.git
>> --branch commons-pool-2.11.0-RC1 commons-pool-2.11.0-RC1
>> cd commons-pool-2.11.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 

  1   2   3   4   5   6   7   8   9   10   >