I still plan to release the jakarta-tomcat HEAD as 3.3.1. 3.3a will be the original 3.3 source with just enough changes to avoid the DOS problem. This is for those who require a "validated" version of Tomcat 3.3 and can't just switch to a new version. Hopefully the minimal changes will make it feasible for them to update. I also plan to mention on the site that for those who can switch, the nightly 3.3.x would be as stable and more bug free than the current, or patched, Tomcat 3.3. It has been a requirement that Tomcat 3.x be able to run under JDK1.1.8. If we keep this requirement, the HEAD of jakarta-tomcat isn't releasable at the moment. I haven't tried to track this down yet, but I assume it won't be a problem to file. It's little issues like this that I don't routinely test that make me reluctant to try to release the HEAD right away. Cheers, Larry
-----Original Message----- From: Bojan Smojver [mailto:[EMAIL PROTECTED]] Sent: Wed 1/9/2002 10:45 PM To: Tomcat Developers List Cc: Subject: Re: Dealing with the Tomcat 3.3 "aux.jsp" DOS problem and a Tomca t 3. 3.1 release Larry Isaacs wrote: > Since it won't be possible to fetch the "patched 3.3" from > CVS using a tag or branch, I'm reluctant to give it a normal > version number. "3.3a" seems like a reasonable alternative. > I'll provide full tar.gzs and zips in addition to jars to update > an existing Tomcat 3.3 installation. So, the 3.3a will be 'current Tomcat 3.3 HEAD from CVS, but released as 3.3a'. Right? Bojan -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >
msg20066/bin00000.bin
Description: application/ms-tnef
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
