Re: [VOTE] 5.5.3 Stability Rating
Tomcat 5.5.3 should be rated: [ X ] Beta, it's getting closer to stable Sorry for the late vote. Better late than never. ;-) Amy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE] 5.5.3 Stability Rating
Hi, I was typing the RESULT message as you were typing this one ;) We're all set with the first 5.5 beta. Yoav Shapira http://www.yoavshapira.com >-Original Message- >From: Remy Maucherat [mailto:[EMAIL PROTECTED] >Sent: Monday, October 18, 2004 10:13 AM >To: Tomcat Developers List >Subject: Re: [VOTE] 5.5.3 Stability Rating > >Shapira, Yoav wrote: > >>Hi, >>Tomcat 5.5.3 has been available for about a week now, so it's time for a >>stability vote. I tentatively rated it Alpha when releasing as my own >>personal impression, but I haven't had any significant issues with it >>myself. It passes our internal tests, and with the StandardWrapper >>hotfix it passes the Servlet and JSP TCKs. So: >> >>Tomcat 5.5.3 should be rated: >>[ ] Alpha still, because ??? >>[ X ] Beta, it's getting closer to stable [what's missing?] >>[ ] Stable, it's rock solid >> >>My vote, as shown above, is for Beta. What's missing from Stable >>rating: StandardWrapper hotfix, a few minor features for the JDT >>compiler that are done only for the Ant compiler, JDT compiler support >>for J2SE 5.0, a few bells and whistles. >> >>This vote will run for about 72 hours as usual. Also as usual, only >>committer votes are binding, but opinions from other readers are >>welcome. Thanks, >> >> >So do we have a first beta ? ;) >(72H/24H = 3 days, so I'm getting impatient :) ) > >Rémy > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] 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: [VOTE] 5.5.3 Stability Rating
Shapira, Yoav wrote: Hi, Tomcat 5.5.3 has been available for about a week now, so it's time for a stability vote. I tentatively rated it Alpha when releasing as my own personal impression, but I haven't had any significant issues with it myself. It passes our internal tests, and with the StandardWrapper hotfix it passes the Servlet and JSP TCKs. So: Tomcat 5.5.3 should be rated: [ ] Alpha still, because ??? [ X ] Beta, it's getting closer to stable [what's missing?] [ ] Stable, it's rock solid My vote, as shown above, is for Beta. What's missing from Stable rating: StandardWrapper hotfix, a few minor features for the JDT compiler that are done only for the Ant compiler, JDT compiler support for J2SE 5.0, a few bells and whistles. This vote will run for about 72 hours as usual. Also as usual, only committer votes are binding, but opinions from other readers are welcome. Thanks, So do we have a first beta ? ;) (72H/24H = 3 days, so I'm getting impatient :) ) Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] 5.5.3 Stability Rating
Costin Manolache wrote: Remy Maucherat wrote: - Allowing pluggability for commons-modeler Can you elaborate a bit more on this ? The basic functionality of modeler is to take an object and a descriptor and return an mbean. This can be made pluggable - a simple interface with a single method is probably enough to hide most of modeler's logic. But all the descriptors need to be converted. But what do you want to use instead and how ? Move the mbean descriptors to conf/ so it can be replaced with another format ( since this is specific to modeler ) ? To give an example, in JBoss, I would use the XMBeans model MBean implementation. I would use XSL to convert the existing descriptors during the build process, and for the introspected ones, I'll have to add the same kind of support to XMBeans. This has an advantage from a configurability and management perspective. I didn't start yet (right now, I'm still finalizing the design of my cache), so I don't know at all if it'll be really practical. Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] 5.5.3 Stability Rating
Remy Maucherat wrote: - Allowing pluggability for commons-modeler Can you elaborate a bit more on this ? The basic functionality of modeler is to take an object and a descriptor and return an mbean. This can be made pluggable - a simple interface with a single method is probably enough to hide most of modeler's logic. But all the descriptors need to be converted. But what do you want to use instead and how ? Move the mbean descriptors to conf/ so it can be replaced with another format ( since this is specific to modeler ) ? Costin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] 5.5.3 Stability Rating
Shapira, Yoav wrote: [ X ] Beta, it's getting closer to stable [what's missing?] I can't really help Filip for any clustering issues, but it's a good build for the rest. I update my TODO list (it's not a before-stable todo list): - A simple host manager webapp (with Ant tasks) - A String cache for ByteChunk and maybe also CharChunk (configurable and manageable - it needs management, as it will work in two phases: statistics gathering, and then caching - using system properties and at runtime with JMX; this is an experiment, and I don't know if it'll be efficient or useless) - Allowing pluggability for commons-modeler - Optimized access log valve Rémy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] 5.5.3 Stability Rating
[ X ] Beta, it's getting closer to stable [what's missing?] Unfortunately due to an acquisition I am jammed at work. Cluster features that previously worked and need to be fixed: 1. Farm deployment I haven't had time to check the other stuff, I know that 5.0.28 had problem with reloading the context where it wouldn't assign a cluster manager properly when reloading, this worked in 5.0.25, it could be possible the same problem exists in 5.5 Filip - Original Message - From: "Shapira, Yoav" <[EMAIL PROTECTED]> To: "Tomcat Developers List" <[EMAIL PROTECTED]> Sent: Tuesday, October 12, 2004 10:36 AM Subject: [VOTE] 5.5.3 Stability Rating Hi, Tomcat 5.5.3 has been available for about a week now, so it's time for a stability vote. I tentatively rated it Alpha when releasing as my own personal impression, but I haven't had any significant issues with it myself. It passes our internal tests, and with the StandardWrapper hotfix it passes the Servlet and JSP TCKs. So: Tomcat 5.5.3 should be rated: [ ] Alpha still, because ??? [ X ] Beta, it's getting closer to stable [what's missing?] [ ] Stable, it's rock solid My vote, as shown above, is for Beta. What's missing from Stable rating: StandardWrapper hotfix, a few minor features for the JDT compiler that are done only for the Ant compiler, JDT compiler support for J2SE 5.0, a few bells and whistles. This vote will run for about 72 hours as usual. Also as usual, only committer votes are binding, but opinions from other readers are welcome. Thanks, Yoav Shapira http://www.yoavshapira.com 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] 5.5.3 Stability Rating
Hi, Tomcat 5.5.3 has been available for about a week now, so it's time for a stability vote. I tentatively rated it Alpha when releasing as my own personal impression, but I haven't had any significant issues with it myself. It passes our internal tests, and with the StandardWrapper hotfix it passes the Servlet and JSP TCKs. So: Tomcat 5.5.3 should be rated: [ ] Alpha still, because ??? [ X ] Beta, it's getting closer to stable [what's missing?] [ ] Stable, it's rock solid My vote, as shown above, is for Beta. What's missing from Stable rating: StandardWrapper hotfix, a few minor features for the JDT compiler that are done only for the Ant compiler, JDT compiler support for J2SE 5.0, a few bells and whistles. This vote will run for about 72 hours as usual. Also as usual, only committer votes are binding, but opinions from other readers are welcome. Thanks, Yoav Shapira http://www.yoavshapira.com 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]