>>>>> "BR" == Brock Rozen <email@example.com> writes:
BR> More or less. Minor design changes could also be included, but anything
BR> major really should wait.
Actually work on 1.95 has been ongoing for over a month. The latest round
of discussion is interesting, but these issues have been gone over more
than once already.
My 1.95 sources are basically a start down the path towards 2.0, basically
in the form of modularization. I'm going to take the time that 1.94 needs
to set up and work at separating the internal majordomo functions from the
external, interface-dependent functions. As a proof-of-concept I'll
probably kick out a little command-line interface that does a few
list manipulation functions without sending mail by calling core majordomo
This is still a couple of weeks away from fruition. I expect to remain
perl4 compatible. That means no objects, no modules, etc. This is
basically groundwork, an embodiment of my belief that Majordomo can evolve
to 2.0 rather than being completely rewritten.
On the subject of yet another mailing list, I must question that. That is
the idea behind this list. I may open a RUST queue to handle Majordomo
bugs and put selected people on that list, but that wouldn't be a place to
wax philosophical about Majordomo's future. (BTW, anyone who has any ideas
about what Majordomo should be like should read the RUST documents first.
There are good ideas there, along with good organization and design.
Majordomo cannot borrow from RUST code because of licensing issues, though.
RUST is at ftp.cs.utah.edu in /pub/rust.)
Jason L. Tibbitts III - firstname.lastname@example.org - 713/743-8684 - 221SR1
System Manager: University of Houston High Performance Computing Center
1994 PC800 "Kuroneko" DoD# 1723