Brent Chapman is certainly right when he writes:
>1.94 has NOT been released yet. It's still in alpha test, which means that
>there are almost guaranteed to be problems with it. If you want help with
>its development and testing, you should subscribe to and take part in
>Majordomo-Workers@GreatCircle.COM.
However, I disagree with the balance of his message, that
> If you don't want to take part in its
>development and testing, you should wait until it's released. Either way,
>Majordomo-Users@GreatCircle.COM is NOT the right place to be discussing
>1.94 yet.
What about people like me, who are definitely users and not developers,
but who have moved to 1.94 because it works better than 1.93 (you may
recall my recent postings about erratic resend behaviour in 1.93)?
Basically this is a group for people who are using MJ (I hate to
disagree with Brent on this, he started the whole thing!), and we are
using the versions we are because those are the ones that work best for
us. I put off installing 1.94 precisely because I didn't want to get
involved in the development process (mainly because I don't know perl
well enough to understand the code, much less change it), but I finally
decided that for my purposes 1.94 worked better than 1.93.
And Brent, have you noticed how many of the replies to questions about
1.93 and other released versions contain patches or suggestions to hack
the code? I don't really see a big difference between hacking released
code and using unreleased code that works.
I also think that even those who haven't moved to 1.94 may find the
postings here useful. That is how I learned that 1.94 was going to offer
some attractive features (like taboo_headers in the configuration file
instead of hacking majordomo itself), and helped me decide when to move.
--
Bill Silvert, Habitat Ecology Section, Bedford Institute of Oceanography,
P. O. Box 1006, Dartmouth, Nova Scotia, CANADA B2Y 4A2, Tel. (902)426-1577
Follow-Ups:
|
|
