Hi Jon,
> From: Jon Stevens [mailto:[EMAIL PROTECTED]]
>
> Of course not. That is why I'm suggesting to move away from it for the
> future and opening the discussion of that now. Would you rather that we
> continue to follow down this path of split trees forever? Would you rather
> that all of our users are consistently confused?
>
> I have learned long and hard over the years that you just can't please
> everyone. It is a sad thing indeed.
>
> It is amazing to me how you guys can just sit back and actually think that
> what Costin is doing to the overall project and the users is a good thing!
> :-(
Another 2 cents from me... :-)
Based upon your arguments I do agree that focusing development work on the
4.x tree is the way to go. After reading your message on "example case of
my hell", I can see why you're keen on keeping the Tomcat tree in one piece.
(Although you didn't quote the best example, as the problem that user was
experiencing with the /admin context was part of tightening up the security
holes in Tomcat, users are now forced to supply a username/password to gain
access to the /admin context. Didn't Craig mention that in the release
notes?)
>From my perspective, development (besides bug fixes) on the 3.x branch only
makes sense as long as the 4.x branch isn't stable. But seeing as the 4.x
branch is approaching beta-release phase, I would agree that the time to
stop enhancements to the 3.x tree is rapidly approaching if not past
already.
As for what to do with the work done on the "3.3" release (which looks like
it may be ready around the same time as the 4.0 release), forking it does
not seem like a bad idea if only to save developers the support headaches.
I'm sure that the committers will make the appropriate decision.
-Dave
