> -Original Message-
> From: Hans Bergsten [mailto:[EMAIL PROTECTED]]
> Sent: Saturday, November 18, 2000 00:34
>
> Regarding the proposed changes, I'm +0. I'd like to see 3.3 (or ideally it
> should be called 3.2.x if you decide to start from scratch with the 3.2
> base) as the continuati
My intention was to make sure we all agree about what
goes into 3.3, and we all agree that those changes are
not just "feature-ism", but things that will give us
a better tomcat.
Please review the list of changes - I'm willing to
undo any of them if you have good arguments or a
better solution (
[EMAIL PROTECTED] wrote:
>
> Tomcat3.2 had a large number of bugfixes that were not incorporated
> in 3.3, and 3.3 has a probably a (possibly large) number
> of new bugs resulting from the big changes and refactoring.
>
> Now, that I have a bit more time ( I hope :-), I can start spending
> more
> 1. In the current "main branch", incorporate all the fixes from
> tomcat3.2,
> plus fixes for the new bugs.
>
> 2. Start with tomcat3.2, and re-do all the changes.
Hi Costin,
My preference is for 1. I think that the major changes that have been
made in Tomcat 3.3 are needed, and I would pre
Hola Costin:
I suspect that if you want to do the 2) proposal, we will not get the
full potential of the changes already done ( that works despite the fact
that there are many bugs to clean ) in the main branch as people willl
say that is better to have a stable/robust release instead of a
stable
, it's normal evolution of tomcat3 - if you are only interested in
3.2 bug fixes that can be done in 3.2.1, etc - but I can't see why/how
tomcat3.3 can't evolve in the same way as 3.1 did.
> > - new utils
>
> If they are truly reusable (e.g. used in both Tomcat and Jasper), wouldn't
> org.apache.util be a better package name?
I would love to - but it's not that easy :-)
Costin
[EMAIL PROTECTED] wrote:
> [...]
> Now, that I have a bit more time ( I hope :-), I can start spending
> more time working on tomcat. There are 2 possible ways to do that:
>
> 1. In the current "main branch", incorporate all the fixes from tomcat3.2,
> plus fixes for the new bugs.
>
> 2. Start w
Hola Costin:
> 1. In the current "main branch", incorporate all the fixes
> from tomcat3.2,
> plus fixes for the new bugs.
>
+1
Saludos ,
Ignacio J. Ortega
Hi,
As you know, 1-2 months ago, when Tomcat3.2 was frozen, I started to work
on all the long-delayed things that were too "dangerous" to implement in
tomcat3.2 time frame ( the list is at the end ).
Most of that has been implemented ( I sent quite a few mails in addition
to the normal CVS commi
