>>>>> "CY" == C Y <smustudent1@yahoo.com> writes:
CY> Jim's original proposal had this outline:
CY> Incorporate new build system when I am done with it. Clean up
CY> package. Call the new version Maxima 5.9. The purpose of this release
CY> is to act as a beta release for the first major release of the new
CY> Maxima project, 6.0. Focus for 5.9 should be the shift to parity among
CY> ANSI Common Lisp implementations.
Hmm, I tried to find Jim's original post, but couldn't. Hence the
posting.
CY> If i read this correctly, what he is saying (and I think it's a sound
CY> idea) is to focus on three thing right now - the new build system,
CY> trying to organize and clean up the structure and packages, and
CY> compiling on different Lisps. I'm not sure where the numerical code
CY> falls in that, but at a guess that's probably a 6.1 feature.
Sounds good. I guess what goes in depends on when 5.9/6.0 is
released. It gets hard to keep things in sync if changes are kept out
for a long time. Perhaps a branch for 5.9/6.0 and a development
branch that includes other stuff?
I'll leave these and other questions to the official maintainers. :-)
CY> Go through all the packages contained in places like share, share1,
CY> share2, etc. and figure out what they all do and why they are there.
CY> Also, which ones should be included, with an expectation that they be
CY> usable, and which need to be pulled until more extensive work is done.
CY> Also, if possible, duplication should be minimized to avoid confusion
CY> (the two vector packages is a good example - if I recall correctly each
CY> has bugs/features the other lacks, and it would make more sense to
CY> either combine them or if there is a definite reason for having two
CY> make it clear why there are two and what each does.)
Good luck figuring this all out! (I'm opposed to pulling things out.
There's no harm in leaving them there.)
Ray