Yes, it is time for spring cleaning.
(1) Target 2.9.x code. Remove #ifdefs which support older versions of
(2) Remove functions that are duplicated in octave. For every function
in the core matlab package, use texinfo docs, octave coding standards
and write test cases. These should be part of octave before the 3.0
(3) It would also be nice to reorganize the project into a package
manager plus a set of independent packages.
Presumably we should maintain a separate branch in CVS for those who
don't want to do the 2.9.x upgrade and are interested in backporting
bug fixes. That won't be me.
Also, I foresee having even less time for octave work in the near term,
so if you see something on the list that you can address (such as
helping new and occasional contributors get their code into
octave-forge) please do so.
On Jun 13, 2005, at 5:59 AM, Stefan van der Walt wrote:
> With the new release out the door, I assume it is ok to make those
> changes now?
> On Sun, Jun 12, 2005 at 03:23:26PM -0400, Paul Kienzle wrote:
>> Use 2.1.70 for now.
>> After the next release we can purge any pre-2.9.x code. If somebody
>> interested in supporting 2.1.x code, they should create a branch after
>> the next release.
>> On Jun 9, 2005, at 4:35 AM, Stefan van der Walt wrote:
>>> Should the scripts in CVS be compatible with Octave 2.1.70, or is it
>>> OK to use functionality from the 2.9.x branch?
> This SF.Net email is sponsored by: NEC IT Guy Games. How far can you
> a projector? How fast can you ride your desk chair down the office
> luge track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> Octave-dev mailing list