Re: [Math][Statistics] Beta release?
I think it would be nice to detail in the beta release notes what expectations should be WRT API stability between the beta and release. Gary On Wed, Jul 27, 2022, 00:34 Matt Juntunen wrote: > +1 > > It would be great to get this code out to developers. > > Regards, > Matt J > > On Mon, Jul 25, 2022 at 11:46 AM Gilles Sadowski > wrote: > > > > Le lun. 25 juil. 2022 à 16:38, Alex Herbert > a écrit : > > > > > > On Mon, 25 Jul 2022 at 14:37, Gilles Sadowski > wrote: > > > > > > > Hello. > > > > > > > > How about making a "beta" release of the next major version: > > > > 4.0-beta1 > > > > ? > > > > > > > > This > > > >https://commons.apache.org/ > > > > page refers to a "1.0-beta1" release [Statistics] that does not > > > > seem to exist. This is a required dependency for [Math]. > > > > > > > > > > I have been held up with other things so have not made progress on the > > > releases: Numbers -> RNG -> Statistics > > > > > > Statistics requires: > > > > > > - a new version of numbers to obtain the updated more accurate Brent > solver > > > for the inverse CDF computation, plus all the work on the beta and > gamma > > > functions. - a new version of RNG that has updated distribution > samplers > > > > > > I think numbers could be released now. > > > > > > Ideally I would like to add a SplittableUniformRandomProvider > interface to > > > RNG before it is released with the new XBG generators. These are > splittable > > > in the JDK and it makes sense to do this now as RNG now supports Java > 8 and > > > this functionality applies to Splittable streams. This is not > essential and > > > it could be released as it is. However the splittable functionality > may be > > > limited if added later with constraints of binary compatibility. I > would > > > rather try to put it in now. I have done a lot of thinking on adding > to the > > > API so I could try and put this up on a Jira ticket for discussion. > > > > IMHO, we should expose the current, several years old, state of [Math] so > > that users may become aware of what they miss out (in [RNG], [Numbers] > > and [Geometry]) by still using version 3.6.1. > > A release makes it easier for application developers to test (and perhaps > > provide feedback and contribute here). A "beta" release will allow us > to fix > > things without BC constraints. > > We could also make a "beta" release of [RNG] (1.5-beta1), on which > > [Statistics] (1.0-beta1) and [Math] (4.0-beta1) would depend, with the > > same advantage. > > > > Best, > > 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: [Math][Statistics] Beta release?
Hello. Le mer. 27 juil. 2022 à 12:34, Gary Gregory a écrit : > > I think it would be nice to detail in the beta release notes what > expectations should be WRT API stability between the beta and release. Here[1] is an excerpt from the release notes: ---CUT--- This is a major release that requires source changes in applications. Lower-level functionality has been split off to new components, often with bug-fixes, performance enhancements and improved API: Commons RNG, Commons Numbers, Commons Geometry, Commons Statistics. Functionality still within Commons Math has been modularized and partly refactored. This is a work-in-progress (help welcome). Codes for which the refactoring has not been undertaken (or was deemed incomplete) have been moved to 'legacy' modules. The minimum version of the Java platform required to compile and use Commons Math is Java 8. Users are encouraged to upgrade to this version, and to the new components listed above (they are now Commons Math's dependencies). For codes that are now located in the 'commons-math-legacy' module, upgrading will be a matter of changing the top-level package name: From 'org.apache.commons.math3' to 'org.apache.commons.math4.legacy'. Codes that are now located in the 'commons-math-legacy-core' module comprise classes that moved from packages 'org.apache.commons.math3' and 'org.apache.commons.math3.util' (e.g. 'MathArrays') over to package 'org.apache.commons.math4.legacy.core'. Notes: Class 'FastMath' has been renamed 'AccurateMath' (now located in package 'org.apache.commons.math4.legacy.core.jdkmath'). Caveat: Although hundreds of issues have been fixed (see 'git log' and the reports in the bug-tracking system of all the listed components), many remain, due to the lack of human resources necessary in order to support the whole codebase. [The Commons Math maintenance nightmare was one of the main reasons for creating more focused components.] ---CUT--- Comments welcome. >From the above, some expectations are pretty obvious: * New code/modules will carry over to the "stable" release * Codes in "legacy" packages could be refactored/modularized (and thus moved to a different package) Judging from the activity in the past 3 or 4 years, it is however fairly unlikely that much of the "legacy" code will change before the stable release (new contributors interested in doing so would be a good surprise). Regards, Gilles [1] https://gitbox.apache.org/repos/asf?p=commons-math.git;a=blob_plain;f=src/changes/changes.xml;hb=HEAD > > > [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Math][Statistics] Beta release?
Le mer. 27 juil. 2022 à 14:06, Gilles Sadowski a écrit : > > Hello. > > Le mer. 27 juil. 2022 à 12:34, Gary Gregory a écrit : > > > > I think it would be nice to detail in the beta release notes what > > expectations should be WRT API stability between the beta and release. > > Here[1] is an excerpt from the release notes: > ---CUT--- > This is a major release that requires source changes in applications. > > Lower-level functionality has been split off to new components, often > with bug-fixes, performance enhancements and improved API: > Commons RNG, > Commons Numbers, > Commons Geometry, > Commons Statistics. > > Functionality still within Commons Math has been modularized and > partly refactored. > This is a work-in-progress (help welcome). > Codes for which the refactoring has not been undertaken (or was > deemed incomplete) have been moved to 'legacy' modules. > > The minimum version of the Java platform required to compile and use > Commons Math is Java 8. > > Users are encouraged to upgrade to this version, and to the new > components listed above (they are now Commons Math's dependencies). > > For codes that are now located in the 'commons-math-legacy' module, > upgrading will be a matter of changing the top-level package name: > From 'org.apache.commons.math3' to 'org.apache.commons.math4.legacy'. > Codes that are now located in the 'commons-math-legacy-core' module > comprise classes that moved from packages 'org.apache.commons.math3' > and 'org.apache.commons.math3.util' (e.g. 'MathArrays') over to > package 'org.apache.commons.math4.legacy.core'. > > Notes: > Class 'FastMath' has been renamed 'AccurateMath' (now located in > package 'org.apache.commons.math4.legacy.core.jdkmath'). > > Caveat: > Although hundreds of issues have been fixed (see 'git log' and the > reports in the bug-tracking system of all the listed components), > many remain, due to the lack of human resources necessary in order > to support the whole codebase. [The Commons Math maintenance > nightmare was one of the main reasons for creating more focused > components.] > ---CUT--- > > Comments welcome. > > From the above, some expectations are pretty obvious: > * New code/modules will carry over to the "stable" release > * Codes in "legacy" packages could be refactored/modularized (and >thus moved to a different package) > > Judging from the activity in the past 3 or 4 years, it is however fairly > unlikely that much of the "legacy" code will change before the stable > release (new contributors interested in doing so would be a good > surprise). Package org.apache.commons.math4.legacy.genetics will very probably disappear (once we agree on the refactoring[2]), to be replaced with a new commons-math-ga maven module. > > Regards, > Gilles > > [1] > https://gitbox.apache.org/repos/asf?p=commons-math.git;a=blob_plain;f=src/changes/changes.xml;hb=HEAD [2] https://markmail.org/message/2mzdbozc6nwobc37 > > > > > [...] - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Math] Web site borked
Hello. I tried to update the web site[1] with the same procedure I had used last time for the same purpose. But it deleted too many pages. Does anyone know how to simply revert to an older revision? What I found on SO is either incomplete, outdated, or does not work properly (resulting in several dozen conflicts). Sorry, Gilles [1] https://commons.apache.org/proper/commons-math/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Math] Web site borked
Le mer. 27 juil. 2022 à 17:42, Gilles Sadowski a écrit : > > Hello. > > I tried to update the web site[1] with the same procedure I had > used last time for the same purpose. > But it deleted too many pages. > Does anyone know how to simply revert to an older revision? > What I found on SO is either incomplete, outdated, or does not > work properly (resulting in several dozen conflicts). Obviously, I did not try all of them, but among the first solutions listed, nothing as straightforward as $ git reset some_commit_id Switching to "git", even if it entails one additional repository per component, would probably result in more robust behaviour in such cases. > > Sorry, > Gilles > > [1] https://commons.apache.org/proper/commons-math/ - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
Re: [Math][Statistics] Beta release?
FYI, For codes that are now located... -> For code that is now located... Gary On Wed, Jul 27, 2022, 08:05 Gilles Sadowski wrote: > Hello. > > Le mer. 27 juil. 2022 à 12:34, Gary Gregory a > écrit : > > > > I think it would be nice to detail in the beta release notes what > > expectations should be WRT API stability between the beta and release. > > Here[1] is an excerpt from the release notes: > ---CUT--- > This is a major release that requires source changes in applications. > > Lower-level functionality has been split off to new components, often > with bug-fixes, performance enhancements and improved API: > Commons RNG, > Commons Numbers, > Commons Geometry, > Commons Statistics. > > Functionality still within Commons Math has been modularized and > partly refactored. > This is a work-in-progress (help welcome). > Codes for which the refactoring has not been undertaken (or was > deemed incomplete) have been moved to 'legacy' modules. > > The minimum version of the Java platform required to compile and use > Commons Math is Java 8. > > Users are encouraged to upgrade to this version, and to the new > components listed above (they are now Commons Math's dependencies). > > For codes that are now located in the 'commons-math-legacy' module, > upgrading will be a matter of changing the top-level package name: > From 'org.apache.commons.math3' to 'org.apache.commons.math4.legacy'. > Codes that are now located in the 'commons-math-legacy-core' module > comprise classes that moved from packages 'org.apache.commons.math3' > and 'org.apache.commons.math3.util' (e.g. 'MathArrays') over to > package 'org.apache.commons.math4.legacy.core'. > > Notes: > Class 'FastMath' has been renamed 'AccurateMath' (now located in > package 'org.apache.commons.math4.legacy.core.jdkmath'). > > Caveat: > Although hundreds of issues have been fixed (see 'git log' and the > reports in the bug-tracking system of all the listed components), > many remain, due to the lack of human resources necessary in order > to support the whole codebase. [The Commons Math maintenance > nightmare was one of the main reasons for creating more focused > components.] > ---CUT--- > > Comments welcome. > > From the above, some expectations are pretty obvious: > * New code/modules will carry over to the "stable" release > * Codes in "legacy" packages could be refactored/modularized (and >thus moved to a different package) > > Judging from the activity in the past 3 or 4 years, it is however fairly > unlikely that much of the "legacy" code will change before the stable > release (new contributors interested in doing so would be a good > surprise). > > Regards, > Gilles > > [1] > https://gitbox.apache.org/repos/asf?p=commons-math.git;a=blob_plain;f=src/changes/changes.xml;hb=HEAD > > > > > [...] > > - > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > >
