1+
The problem, of course, is that the critical functionality is evolving so
rapidly, that most "users" prefer the developer list, since that is where
the action is. This is the downside of a Open Source project such as Tomcat
(as opposed to the Apache Server project where CVS updates involve very
little change in the functionality, or usability of the server).
The alternative, as some implied, is to understand that the "developers"
group is going to consist of active contributors to the CVS codebase as
well as "active" alpha/beta testers looking to get a head start with what
is a cutting edge product, but not up to speed with the philosophical
underpinnings of the evolution of the system. They, by the way, are likely
to be the first real "users" of the "product" and their questions, concerns
and frustrations an indication of the likelihood of the product being
accepted.
Besides the current traffic on tomcat-dev is hardly so high as to suggest
these users pose a risk and one can simply ignore questions one doesn't
want to answer which is much less typing than biting someone's head off for
not having been here three months ago.
Sean
PS. Being on a couple of NNTP based newsgoups, I think I favor these to a
mailing list since it is easier to thread (and ignore) messages.
"David Rees"
<drees@ebetin To: <[EMAIL PROTECTED]>
c.com> cc:
Subject: RE: future questions
12/19/00
07:26 PM
Please
respond to
tomcat-dev
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
>
<snip>
> p.s. Costin, I had a great idea. I'm going to forward to you all of the
> personal email based Tomcat support questions that I get. Have
> fun answering
> them. :-)
How about forwarding them or pointing them to the tomcat-user list where
these questions will be answered?
-Dave
