Re: [5.0.3] Tag soon, 5.0 release plan
Remy Maucherat wrote: Shapira, Yoav wrote: 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 ;( Sure. Well, I was thinking writing new docs on setup and run would be useful. It's not only the basics. It should talk about using commons-daemon to run on Unix, and other stuff. Other docs about the new features are welcome also: - new monitoring features (JMX, how to use MC4J with TC, etc) Remmy, recently you wrote that it would be nice to ship with JMX 1.2 + a JSR 160 implementation if possible. Do you think it will be possible to get this from MX4J? Or is it possible to use JMX1.2 RI + JSR160 RI (when it will be finalized)? Radim - updates for the deployer tweaks and improvements - etc I think any useful docs will help, so feel free to contribute whatever you'd like ;-) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [5.0.3] Tag soon, 5.0 release plan
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]
Re: [5.0.3] Tag soon, 5.0 release plan
+1. Sounds good. I'll try to keep track of common topics from tomcat-user land to indicate what documentation areas need most help. A feature I want to add (post tagging and haven't started yet) is integrating lucene into the tomcat-docs. -Tim Remy Maucherat wrote: Hi, I am nearly done with the features I wanted to add for 5.0.3 (and the changelog is pretty big), so I plan to tag 5.0.3 at the end of this week (friday, but more likely saturday). I don't know if there are some more major features that people would like to see in 5.0.x (if that's the case, please add items to the status page in the docs), but as far as I am concerned, 5.0.x is nearly feature complete. What's missing is better docs, and lots of tweaks and fixes. Because of that, I plan to write a release plan for Tomcat 5.0.x, outlining a tentative schedule and objective for betas and eventually a stable release (which as a reminder won't happen until the new specs are final). 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. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.3] Tag soon, 5.0 release plan
Shapira, Yoav wrote: 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 ;( Sure. Well, I was thinking writing new docs on setup and run would be useful. It's not only the basics. It should talk about using commons-daemon to run on Unix, and other stuff. Other docs about the new features are welcome also: - new monitoring features (JMX, how to use MC4J with TC, etc) - updates for the deployer tweaks and improvements - etc I think any useful docs will help, so feel free to contribute whatever you'd like ;-) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [5.0.3] Tag soon, 5.0 release plan
Tim Funk wrote: +1. Sounds good. I'll try to keep track of common topics from tomcat-user land to indicate what documentation areas need most help. A feature I want to add (post tagging and haven't started yet) is integrating lucene into the tomcat-docs. Done in a convincing way, that looks like a very good idea :) Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[5.0.3] Tag soon, 5.0 release plan
Hi, I am nearly done with the features I wanted to add for 5.0.3 (and the changelog is pretty big), so I plan to tag 5.0.3 at the end of this week (friday, but more likely saturday). I don't know if there are some more major features that people would like to see in 5.0.x (if that's the case, please add items to the status page in the docs), but as far as I am concerned, 5.0.x is nearly feature complete. What's missing is better docs, and lots of tweaks and fixes. Because of that, I plan to write a release plan for Tomcat 5.0.x, outlining a tentative schedule and objective for betas and eventually a stable release (which as a reminder won't happen until the new specs are final). 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. Comments ? Remy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
