Hello. Le mer. 27 juil. 2022 à 12:34, Gary Gregory <garydgreg...@gmail.com> 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