tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: Tagging 1.2.12
Date Mon, 09 May 2005 21:05:04 GMT

----- Original Message -----
From: "William A. Rowe, Jr." <>
To: "Tomcat Developers List" <>
Cc: <>
Sent: Monday, May 09, 2005 1:28 PM
Subject: Re: Tagging 1.2.12

> At 02:30 PM 5/9/2005, Jean-Jacques Clar wrote:
> >Build and run on NetWare with apache 2.0.54.
> Woot!
> And thank you for the example, Jean-Jacques, of exactly why we
> need more than a few days before we declare 'stable' releases ;-)
> But I do think it's wonderful that the NetWare issues are gone.
> What about 1.3.33?  What about 2.1-dev?  What about other servers?
> And you mention it runs, but against which Tomcat, 5(.5)?

According to Gump, it still doesn't want to build against 2.1-dev ;-).

Of course, this is because of a httpd bug, so it shouldn't effect the
stability vote of mod_jk one way or the other.

> I hope you see my point, there is an incredible set of combinations
> which are quite useful and legitimate in tomcat-connectors.  I keep
> hearing the refrain "Lets deprecate all this stuff I don't test".
> Rather than deprecate, what about simply allowing enough time for
> dust to settle, and reports to roll in.  3 +1's that all looks like
> it's good, and then let the community (with all their goofy combinations
> of OS's, connectors, and backends) chime in with complaints.
> [Yes - I mean complaints, few ever give us the good news
> when all is well :-]
> Bill
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

View raw message