On 23 November 2011 13:41, Gary Gregory <garydgreg...@gmail.com> wrote: > As a [math] outsider and curious watcher of the [math] "sub-ML" I can offer > the XP mantra: release early, release often. It will never be perfect ;)
I think this is a dangerous mantra for Commons, which strives for extreme compatibility (to coin a phrase). > Take care of API breaking changes, release 3, tweak features for 3.1 and so > on. Some API breaks are relatively easy to detect - use Clirr. Functional API breaks are a bit harder, though hopefully unit tests will reveal these. The problem with RERO is that it is all too easy to introduce a new API which turns out to be faulty. This can be difficult or impossible to correct later. There are several such examples in the Java libraries. > 2c, > Gary > > On Wed, Nov 23, 2011 at 4:19 AM, Luc Maisonobe <luc.maison...@free.fr>wrote: > >> Hello, >> >> I have had several questions about release plans for 3.0. >> >> I feel guilty for not having pushed this version out yet. It is not in >> release shape now and many thing are still ongoing. Typically, a new >> thread as been started a few hours ago about an important change in the >> linear algebra API (a needed change, so something important to discuss >> now). >> >> As far as I am concerned, here are the points I want to address myself >> (but if other people want to help, chime in!). I would like to see what >> other developers have in mind so wa can set up a release plan, and >> really work toward a release which is past due. >> >> My personal tasks are: >> - finish the adapters wrapping unbounded optimizers into simple bounds >> optimizers as set up by Gilles, using the two function adapters >> already available >> - stabilize Adams based ODE integrators using the >> MathUtils.linearCombination feature to ensure better accuracy and >> error estimates in the Nordsieck vectors >> - perhaps add back the BDF integrator for stiff problems, using the >> Nordsieck vectors once it has been stabilized for Adams methods >> - perhaps add a Radau integrator >> - replace the reset() method in step handler interface by init() >> (it's a simple rename), and add a similar init() in the events >> interface >> - fix the mapping between boundary representation/BSP representation >> in 2D/3D >> >> could other people add to this list the features they want to have in 3.0 ? >> >> Luc >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
