On Thu, 14 Jun 2001 [EMAIL PROTECTED] wrote:
| +0 - most of my time will be split between jasper34 and tomcat33 ( and a
| bit j-t-c, after jasper34 stabilize a bit ).
How's 3.3 doing, Costin?
--
Mvh,
Endre
+1
Larry
-Original Message-
From: Marc Saegesser [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 14, 2001 11:49 AM
To: [EMAIL PROTECTED]
Subject: Plans for Tomcat 3.2.3 and later
Now that Tomcat 3.2.2 is out it's time to starting thinking
about 3.2.3. My
thoughts
Now that Tomcat 3.2.2 is out it's time to starting thinking about 3.2.3. My
thoughts are to have a release for 3.2.3 in three or four months. This will
be strictly a bug fix release. The only hard and fast release requirements
are to fix any specification compliance issues that may be
On Thu, 14 Jun 2001, Marc Saegesser wrote:
Now that Tomcat 3.2.2 is out it's time to starting thinking about 3.2.3. My
thoughts are to have a release for 3.2.3 in three or four months. This will
be strictly a bug fix release. The only hard and fast release requirements
are to fix any
+1
Marc,
You did a great job pulling together 3.2.2. I'll be happy to work on issues in 3.2.3.
Mike Anderson
[EMAIL PROTECTED] 06/14/01 09:49AM
Now that Tomcat 3.2.2 is out it's time to starting thinking about 3.2.3. My
thoughts are to have a release for 3.2.3 in three or four months.
+0 - most of my time will be split between jasper34 and tomcat33 ( and a
bit j-t-c, after jasper34 stabilize a bit ).
Costin
On Thu, 14 Jun 2001, Marc Saegesser wrote:
Now that Tomcat 3.2.2 is out it's time to starting thinking about 3.2.3. My
thoughts are to have a release for 3.2.3 in
+1 I will help with any SecurityManager issues
Marc Saegesser wrote:
Now that Tomcat 3.2.2 is out it's time to starting thinking about 3.2.3. My
thoughts are to have a release for 3.2.3 in three or four months. This will
be strictly a bug fix release. The only hard and fast release
Now that Tomcat 3.2.2 is out it's time to starting thinking
about 3.2.3. My
thoughts are to have a release for 3.2.3 in three or four
months. This will
be strictly a bug fix release. The only hard and fast release
requirements
are to fix any specification compliance issues that may be