>> 1) Release Tomcat 3.2 final (soon, please!)
>
+1
It will help at least to reduce the questions on TOMCAT 3.1 which
many users think the stable release.
2) Create a new proposal tree alongside with Catalina (new
>name to avoid
>> confusion, please)
-1, yes it will be hard to follow 3 tree.
My opinion is that TOMCAT 3.3 must be the evolution (bug fixes) of TC 3.2
(as TC 3.2 was for 3.1) and RI for SERVLET 2.2/JSP 1.1. Next releases 3.4
could
have SERVLET 2.3/JSP 1.2 support. I speak here as an end user, WE NEED NOW a
bullet
proof production servlet engine.
3) Release Tomcat 4.0 (with Catalina, as we all decided)
-1, Are you sure that TC 4.0 is the priority ? JSP 1.2 and SERLVET 2.3 are
still proposal
and still changes. JSP 1.1 AND SERLVET 2.2 are today, let play with future
tomorrow.
4) Decide wether Tomcat 5.0 will be Catalina based or "whatever" new
proposal comes along.
-1, 3.x / 4.x must be hardly tested in productions environment to decide
which
one is better suited (CPU use, MEMORY required...)
I'm a new commiter, and started to contribute to this project with a
end-user vision.
I conviced my company to select TOMCAT as our main servlet engine instead of
JRUN or
Websphere and I succeed since they saw TOMCAT as an APACHE product and
associated that
to the high quality of Apache Web Server (we allready use).
I deploy TOMCAT on productions servers (so the need for Linux RPM packaging)
and like
others I need more STABLE release than READY FOR THE FUTURE release.
My perception is that TC 3.x must be the release for production environment
and TC 4.x
for developpement and test envs.
So as a conclusion, please release 3.2, start 3.3 m1 or beta1, and have a TC
4.x branch.
If not you'll see many users tired or worried about this 'phylosophic
discussion' goes to
others Open implementations like resin.
Please don't play again the 'Xerces Balad'.
PS: If Costin need help, it could count me on.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
