Re: [OctDev] state of octave-forge code

[David B. <Dav...@mo...>]

Keith Goodman a =E9crit :

>I think it partly depends on the plans for Octave 2.9. When will it
>become the recommended stable version of Octave?
>
> =20
>

John has mentioned some time this summer as the release date for 3.0 a=20
couple of months ago. I'd say the very end of summer is realistic at the=20
moment. A testing release is vital before such a release and so I=20
wouldn't expect more than a couple of months before a testing version of=20
2.9.x, at which time it would make sense to start thinking about a new=20
release of octave-forge.

>And it partly depends on how much work is needed to be make
>Octave-Forge ready for 2.9.
> =20
>
octave-forge is already ready for 2.9.3 as you note... This is not the=20
issue. The issue is that there are many duplicate function in=20
octave-forge relative to octave that should be removed, and there are a=20
large number of version specific tests in octave-forge as Paul pointed=20
out that make the code rather crufty... The purpose of a 2.9 specific=20
version is to profit from the upcoming release of octave 3.0 to largely=20
simplify octave-forge..

Cheers
David