Re: [OctDev] state of octave-forge code

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

Paul Kienzle a =E9crit :

> Yes, it is time for spring cleaning.
>
> (1) Target 2.9.x code.  Remove #ifdefs which support older versions of=20
> octave.
>
> (2) Remove functions that are duplicated in octave. For every function=20
> in the core matlab package, use texinfo docs, octave coding standards=20
> and write test cases.  These should be part of octave before the 3.0=20
> release.
>
> (3) It would also be nice to reorganize the project into a package=20
> manager plus a set of independent packages.
>
> Presumably we should maintain a separate branch in CVS for those who=20
> don't want to do the 2.9.x upgrade and are interested in backporting=20
> bug fixes.  That won't be me.


I feel the main branch in the CVS should probably be the 2.9.x code, but=20
that might be too agressive at the start with octave 2.9 still=20
considered as unstable. For that reason I'd suggest creating a 2.1 and a=20
2.9 branch right now, where 2.1 branch will follow the MAIN branch at=20
the start, and when 2.9 goes into testing we merge the 2.9 branch into=20
the main branch.

There is rather a lot of spring cleaning to do...

D.