Howdy, >complete. What's missing is better docs, and lots of tweaks and fixes.
I'd like to help with the docs. Can you prioritize what docs you think need work (or need to be written from scratch)? I actually have tomcat commit access already, so there should be no delay like with commons-modeler ;( >Note: the rationale behind the "no final before the specs" is beacause: >- if the specs change and modify a behavior that was introduced in the >new specs, we'd have to break our API / behavior, which is not really >acceptable >- it's a chicken and egg problem: if there's no spec, people will >(likely) prefer using Tomcat 4.1.x, and so Tomcat 5.0.x wouldn't get >enough testing to warrant the "stable" label >Given the last point, the best IMO would be to make a "RC"-like release >when the specs are released, followed a few weeks later by a final. I fully agree with the rationale. We can't make a reference implementation stable release of a spec that hasn't been released ;) Having a beta (as opposed to the current alpha) release, marked as feature complete and just awaiting testing, is good. We'll be able to have minimal turnaround time from spec release to tomcat 5 stable release. Yoav Shapira This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
