Quoting David Bateman <[EMAIL PROTECTED]>: > Now that this octave-forge release is done, should we target future > octave-forge release for the 3.1.x/3.2.x tree? If so can I commit > the patch that moves the quaternions, control, and ?? toolboxes into > octave-forge. There are also several other changes that are > necessary to make octave-forge compatible with a 3.1.x/3.2.x release > including remove functions that have moved into Octave, adapting > user types for the new method of having mapper functions as part of > the octave-value class, etc. I suppose whether we should do this is > or not should be based on the expectation of when the 3.2.0 release > will be.
I guess it also depends on how much work needs to be done in Octave-Forge. If we just need two weeks to get things in a good shape, then I don't see the hurry. That being said, I think we should just go for it, and start updating Octave-Forge to 3.1.x. Vaguely related, I should say that making this release was quite a pain (release-forge didn't work for me, and I had to upgrade the version number of packages that hadn't been changed). So, if moving Octave-Forge to 3.1.x would mean we don't have any releases until 3.2.0 is released, then that would be just fine with me :-) Søren ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Octave-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/octave-dev
