There are clearly 2 lines of "belief" in this project. Each group has
its own motivations and reasons.
We already went over this again and again and my conclusions were
always:
- People working on 3.3 have their own reasons to do it at the moment;
- Work is not being lost on 4.x because the 3.3 people do not have the
same motivation to work on 4.x;
- It is not a matter of one group being right and the other being
wrong.
Each of these groups is right - according to their respective reasons
and motivations.
I learned from Jon (*) that Open Source is mostly about scratching your
own itch in a cooperative way. And this is not a corporative project,
it is an Open Source one.
And that is what is happening here: at the moment (things will probably
evolve in some different direction) there are to big groups of itches
to scratch - 3.3 and 4.x.
Instead of loosing more time fighting about the stupid concept of one
of the groups having to be wrong, let's focus on how the two groups
still can cooperate scratching common itches.
There are some very interesting developments on this directions with
mod_jk and jasper. Focusing in this kind of thing is quite productive
and puts some of the 3.3 people cooperating in the development of the
4.x version and vice versa.
Trying to force one of the groups out of its way will just fragment
this project and take the 3.3 people somewhere else (SourceForge or
so).
In due time, the usual survival rules will tend to favor the
solution that proves to be the best and everybody will work together
again... until the next revolution.
Also, remember that 4.x itself started this way.
Have fun,
Paulo Gaspar
(*) - Yes, I sometimes learn from Jon, despite the flame wars.
=;o)
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Peter
> Mutsaers
> Sent: Saturday, May 05, 2001 7:35 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [PROPOSAL/VOTE] New Repositories for Collaborative
> Development
>
>
> >> "Bip" == Bip Thelin <[EMAIL PROTECTED]> writes:
>
> Bip> I guess more or less the only reason why TC4 hasn't been
> Bip> released as final is because the Servlet/Jsp spec's aren't
> Bip> final so when those get final I'll guess that we'll start
> Bip> working towards a "real" TC4 release. That release would then
> Bip> be the current Tomcat release and thus making TC < 4 more or
> Bip> less obsolete. Sure, user's won't be switching over
>
> I just switched from Apache/JRUN towards Tomcat, and tested Tomcat 3.2
> and 4.0 to decide which one to take (for the production site).
>
> I found some annoyances in the latest released 3.2 version (such as
> not filling in the RootCause in ServletExceptions, making tracing of
> run-time errors harder), so then I tried 4.0-b3. I found it to be as
> least as stable as 3.2 under some stress-testing, and also it is
> clearly faster.
>
> So I didn't even try or consider 3.3; why should I? AFAIAC using 3.3
> doesn't make sense: either the latest "real" release, or something
> which is better and closer to long-term development anyway, but not
> "official" yet.
>
> I understand that TC4 isn't a real release because of the Servlet/JSP
> specs aren't final yet, but that doesn't bother me, because:
>
> Whatever still might change to the specs, they shall remain backwards
> compatible with the current specs (servlet 2.2, jsp 1.1), so if I
> simply use TC4 according to the current specs, and don't use any
> features of the future specs, then even changes to future the specs
> that TC4 implements won't have consequences.
>
> --
> Peter Mutsaers | Dübendorf | UNIX - Live free or die
> [EMAIL PROTECTED] | Switzerland | Sent via FreeBSD 4.3-stable
>
