Jeff Tulley wrote:
4.1.16 was released as alpha on 11/26. I introduced the bug in that release (when I was dumb enough not to figure out that the error flag would stay in its bad state forever). In theory, there should have been plenty of time to find the bug, except that few deployed the build on a test production server.Easier said than done. An interesting observation is the fact that everybody thought things were stable, and as far as any reports coming in, it seemed things were. However, once Remy declared 4.1.17 as stable, suddenly people actually started putting Catalina through it's paces(to see if they wanted to put it into production), and started finding problems. I think it was a good move, looking back.
The bug actually got reported once, but the report was unconclusive, without any data to reproduce it.
What would be best is if we had our own test server. httpd has www.apache.org to put the CVS version into production; M$ has their big traffic to test IIS, but Tomcat has nothing.I guess what I'm saying is that, unfortunately, the only way to be sure a release is really stable, is to convince many non-committers to stress-test it, and they only do that if they are told it is stable.Unless you want to come up with a stress / stability test procedure to be run against every build, that would be nice.
I don't know if it would be possible to consider hosting all or part of Jakarta on Tomcat to get some similar testing ;-)
Remy
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
