[EMAIL PROTECTED] wrote:
> [...]
> Are you saying that a proposal that got 6 commiter votes ( which happen to
> be the full PMC, except Sam, plus Remy ) are representing the whole
> project ?
I'm preparing for the meeting tomorrow, so I'm interested in getting
as much input as possible. I've gone through the archives of this list
and read all relevant mails regarding this, so I'll try to give you a
feel for how I see things with regards to what have been decided and
not,
and what we need to decide next.
My reading on the voting on the proposal is that it passed, since there
where more than 3 +1 and no -1; that's all it takes according to the
rules. Any committer had a chance to -1 it but no one did that.
> Are you saying that the proposal meant to replace 3.x with 4.0 ? When 4.0
> was still 6 months away from alpha ?
No, the proposal consisted of three points: new CVS repository for
Tomcat 4.0, re-architecting of Jasper for JSP 1.2, and adoption of
Catalina as the code base for Tomcat 4.0.
Since the proposal passed, it means that it was decided by the
committers
in this project that the Catalina code base will be used for
implementation of the Servlet 2.3/JSP 1.2 APIs (this is both implied by
the 4.0 version according to the revision rules for Tomcat, and was
explicitly stated in both the proposal mail and the proposal document
referenced by the mail).
As a consequence, I feel that this decision means that Tomcat 3.x can
*not* implement Servlet 2.3/JSP 1.2, since it would be very confusing
for both developers and users with two code bases supporting the same
API levels within the same project.
The motivation for two separate repositories for TC 3.x and 4.x in the
proposal says (among other things) that
"Support and enhancements of the existing Tomcat 3.x can continue
uninterupted, without disruptions caused by development on the
next major version. This is important because many developers
(and server vendors) have adopted Tomcat 3.x (or plan to adopt
Tomcat 3.2 shortly) into their environments, and will need
continued support until they choose to migrate to Tomcat 4.x
at some future date."
So the issue at hand, IMHO, is not TC 3.x *or* TC 4.x for Servlet 2.3
and JSP 1.2; that decision has been made. Besides, the majority of
voices I hear in support of TC 3.3 say they want a better, stable
and supported Servlet 2.2/JSP 1.1 container, not a container that
competes with TC 4.x as a container for the new API versions.
The issue, IMHO, is how to best serve the TC 3.x community; continued
3.2 dot-releases or move to 3.3 (and dot-releases based on 3.3 after
that)? It's not a given, considering the large differences between
3.2 and 3.3 (even if they seem to be for the better).
The way I feel right now is that the best way to answer this question
is by a vote on this list, where all +1 votes for TC 3.3 also means a
commitment to help fix bugs in TC 3.3. That's pretty much how we got
from TC 3.1 to TC 3.2. Sam announced his intention to step up as the
release manager for TC 3.2 and and start cutting milestone releases
in a mail titled "Towards a 3.2 release" (14 June, 2000). For various
reasons the release dragged on for a very long time, and eventually
Craig took on the role as release manager and started to cut betas.
November 27, 2000, Craig asked for a vote on the release of 3.2 and
a plan for continued support of the 3.2.x branch. This vote got the
required +1 and no -1.
So the status right now is that we have a plan for continued support
of 3.2.x, with an appointed release manager, but we do not have a
proposal for releasing 3.3. Please do not make such a proposal before
the meeting ;-) I believe it's the right thing to do, but I want to
discuss it with the other PMC members first.
> Quick poll - how many of you ( who voted or not at that time ) read the
> proposal as "3.x development should stop, Catalina has proven to be
> better" ?
Not as "3.x development should stop", but as "development of the
new APIs will be done based on Catalina while TC 3.x continues to
be the RI for 2.2/1.1, with bugfixes and enhancements as needed".
> How many of you can name the fundamental differences between
> tomcat3 and catalina and explain why one choice is better ( not to mention
> that tomcat3.3 supports valves ).
>
> How many spent time reading 4.0 and 3.3 and believe that 4.0 is indeed
> simpler, better or faster ?
At the time, I did a quick review of TC 3.x and TC 4.x and found 4.x
to be the code base I believe in for the future. I still feel the same
way.
> And how many commiters ( including Hans and Duncan ) did stoped working on
> 3.x and started working on 4.0 ?
I don't have much time to spend on active development, so all I do
is "scratch my itches" now and then (and monitor the list to make sure
we stick to the specs). My biggest itch so far has been to get 3.2
released, so I helped out with a few patches there. For the future, I
will be more likely to contribute to TC 4.x though, since I will start
to play around with the new spec versions.
> Does it looks like a "project decision" ?
Yes, to me it does; it was voted on and got the required +1 votes and
no -1 votes. That's a "project decision" according to our rules for
decision making in this project.
Hans
--
Hans Bergsten [EMAIL PROTECTED]
Gefion Software http://www.gefionsoftware.com
Author of JavaServer Pages (O'Reilly), http://TheJSPBook.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
