[MATH] Legacy module debug files
These files exist in the legacy module: src/main/java//org/apache/commons/math4/legacy/linear/EigenDecomposition.java_PRINT src/main/java//org/apache/commons/math4/legacy/optim/nonlinear/scalar/noderiv/SimplexOptimizer.java.DEBUG I assume they were committed in error. OK to remove them? Alex
Re: [geometry] 1.0 release (take 2)
On Tue, 10 Aug 2021 at 22:12, Gilles Sadowski wrote: > Le mar. 10 août 2021 à 21:25, Matt Juntunen > a écrit : > > > > FYI, I'm planning to start the geometry release process within the > > next couple of days instead of waiting for the RNG release as > > mentioned previously. (Geometry only uses RNG for unit tests and > > benchmarks.) The reasons for this change of plans is that (1) I have > > need of the code in other projects and (2) I have time now to do the > > release but will most likely not later on. Please let me know if you > > have any objections. > > No problem. > [There is also no worry then to release RNG v1.4 and we can think > about RNG-127.] > I am finishing the performance work on the new ziggurat sampler. Then I was going to look at a RNG release. This would not be for 2 weeks as I am away next week and so cannot go through the full 3 day vote release before then. So go ahead with a geometry release since it does not require anything from RNG. I do not think RNG-127 will affect anything we currently have in v1.4. I think pushing out v1.4 now under Java 7 and then upgrading to Java 8 for changes that RNG-127 may bring. The use of Java 8 would allow work on a streaming API and also methods to be added as default methods to existing interfaces. It would give more time to digest exactly what to add for RNG-127 while putting out the changes that have built up for v1.4. Alex
Re: [geometry] 1.0 release (take 2)
Le mar. 10 août 2021 à 21:25, Matt Juntunen a écrit : > > FYI, I'm planning to start the geometry release process within the > next couple of days instead of waiting for the RNG release as > mentioned previously. (Geometry only uses RNG for unit tests and > benchmarks.) The reasons for this change of plans is that (1) I have > need of the code in other projects and (2) I have time now to do the > release but will most likely not later on. Please let me know if you > have any objections. No problem. [There is also no worry then to release RNG v1.4 and we can think about RNG-127.] Thanks, Gilles >> [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [geometry] 1.0 release (take 2)
FYI, I'm planning to start the geometry release process within the next couple of days instead of waiting for the RNG release as mentioned previously. (Geometry only uses RNG for unit tests and benchmarks.) The reasons for this change of plans is that (1) I have need of the code in other projects and (2) I have time now to do the release but will most likely not later on. Please let me know if you have any objections. Regards, Matt J On Mon, Aug 2, 2021 at 7:25 AM Alex Herbert wrote: > > On Mon, 2 Aug 2021 at 02:32, Matt Juntunen > wrote: > > > > > > Then, as a matter of preference, I'd still suggest that "Commons RNG" > > > be released first (if the latter's next release is pending). > > > > Ok. Any thoughts on a timeline for that? > > > > I am currently looking at it. > > The dryRun build of the release profile now works under JDK 11.0.11. This > is good. Previously JDK 11 complained about the JPMS modules using code > from packages in the unnamed module and this errored the build. It had to > be released using JDK 9. Now the latest JDK has a more lenient javadoc tool > and the warnings are printed but it does not fail the build. > > I am going to try updating the modules to use Java 11 in-place of Java 9 > and see if that works. It would be preferable to release the example JPMS > modules built using the first LTS version to support modules (i.e. JDK 11 > not not JDK 9). > > Alex - 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.0 based on RC1
[X] +1 Release these artifacts Build from tag on: Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f) Maven home: /opt/apache-maven-3.6.3 Java version: 11.0.11, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64 Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "5.4.0-80-generic", arch: "amd64", family: "unix" Site reports look good. Checked signatures, found nothing wrong. Manually inspected a couple files from the dist area, all looking good as well. Thanks! Bruno On Monday, 9 August 2021, 10:12:35 am NZST, 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 compatibility Older components
Re: [VOTE] Release Apache Commons Pool 2.11.0 based on RC1
[x] +1 Release these artifacts Building OK from tag, with `clean test install` targets. Building OK from tag, with `site:site` targets Site reports look good. Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) Maven home: /opt/apache-maven-3.8.1 Java version: 16, vendor: Oracle Corporation, runtime: /Users/abernal/Library/Java/JavaVirtualMachines/openjdk-16/Contents/Home Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: “Mac" Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) Maven home: /opt/apache-maven-3.8.1 Java version: 11.0.5, vendor: Oracle Corporation, runtime: /Library/Java/JavaVirtualMachines/jdk-11.0.5.jdk/Contents/Home Default locale: en_US, platform encoding: UTF-8 OS name: "mac os x", version: "10.16", arch: "x86_64", family: “mac" Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) Maven home: /opt/apache-maven-3.8.1 Java version: 1.8.0_275, 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" [INFO] Scanning for projects… Arturo Bernal arturobern...@yahoo.com > On 9 Aug 2021, at 00: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. > > [ ]
