> -----Original Message-----
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
>
> on 12/18/2000 10:01 AM, "Greg Bailey" <[EMAIL PROTECTED]> wrote:
>
> > As a use of Tomcat 3.1 on several production machines, may I
> say "thanks" also
> > to
> > Costin and everyone else who supports 3.1 (and 3.1.1, 3.2,
> 3.2.1, etc.) We
> > are
> > in no position to jump to 4.0 just because its trendy and has more
> > "development
> > activity"...
> >
> > Thanks again,
> > -Greg Bailey
>
> I wish people would pay more attention to what the overall issues are
> instead of focusing on entirely the wrong things. That isn't what I was
> saying at all.
>
> The issue is the idea of a 3.3 and I'm not saying to "jump" to 4.0.
>
> Please look at all the information available to you about what is
> happening
> before commenting again.
It really is part of the same issue. Because Greg is not willing to jump to
4.0, the idea of continuing development on the 3.x branch (work towards 3.3)
is welcome and reassuring. There will likely be some issues with porting
applications to 4.0 which can't be easily resolved.
I see no problems with Costin (and others) continuing work on the 3.3
release, especially considering his recent comments about doing development
on Tomcat with the Apache group:
Costin said (quoting Jon):
> > simply fork what you are doing into another project
> > that is hosted somewhere else.
> It's the second time an Apache member is asking me to
> go somewhere else. Believe me, right now it's my
> biggest wish - I've had more than enough !
The way I see it, having Costin stopping work on the 3.x tree won't free up
any substantial amount of resources for the 4.x tree. Costin doesn't seem
to be planning on any future development on Tomcat after 3.3 is done!
Either way, what does it matter if Costin is doing development work on the
3.x tree under Apache or under his own project?
Frankly, I am disappointed in the development process of Tomcat. I posted a
simple documentation patch (See bug report 528) two weeks ago for the FAQ
included with the Tomcat 3.x and posted a couple messages about it. I
haven't heard a thing about it and saw the release of 3.2.1 come and go
without the documentation fix.
-Dave
