Re: Where's 4.1.31?
Jess Holle wrote: The offer to do this is great, but I am more than a little curious: Why would anyone bother with a 4.1.x upgrade at this point? 5.0.27 is faster, more stable, etc, at this point as best I can tell. Because the 5.0 branch has a memory leak I haven't been able to pin down, so I am stuck with 4.1.x in production. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where's 4.1.31?
Jeanfrancois Arcand wrote, On 8/20/2004 9:45 AM: Althrough I agree with peoples that can't move to Tomcat 5, Tomcat 5 has been available for more that 1 year. That will be good for Tomcat if people migrate from 4.1.x to 5 and find bugs (that way they will not be carried into 5.5/6). Although I would love to upgrade all of my sites to Tomcat 5, unfortunately there is one particular showstopper for me in the behavior difference between Tomcat 4 and 5. Specifically, it is the fact that TC5 no longer pauses request processing during a context reload while TC4 does. While this behavior could be worked around with load-balanced Tomcats, until mod_jk (or the Apache proxy module improvements) support dynamic reconfiguration, having to make a class change during operations can be disruptive. Currently, if you wish to disable a Tomcat using mod_jk, you have to at least have Apache gracefully restart, which is not always very graceful. IMO, if there are enough commiters willing to make/support another 4.1 release, let them! -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Where's 4.1.31?
Hi, You can't expect a 4.1.31 anytime soon. It's in a maintenance mode where only Spec violations and security flaws are the things that would get a new release out. We suggest the same thing we've been suggesting for a while now, upgrade to 5.x. Yoav Shapira Millennium Research Informatics -Original Message- From: Tom Anderson [mailto:[EMAIL PROTECTED] Sent: Thursday, August 19, 2004 9:32 PM To: Tomcat Developers List Subject: Where's 4.1.31? There have been some important bug fixes in the baseline since April that haven't made it to a release version yet. Are there plans to release another version of Tomcat 4.1? The changes I am interested in some fixes that were done by Glenn and Markt but some thought they might be too risky. But I applaud those changes since they could allow me to discard my own internal patches that I have had to make to address these same problems.Some of the problems/fixes I'm talking about are: 1. Inefficient database queries for persistent sessions 2. Session expiration problems caused by differing interpretations of the getLastAccessedTime() method 3. NPEs in StoreBase 4. Remove non-serializable attributes from sessions 5. Changed classes throw InvalidClassExceptions on de-serialization These seem like pretty significant issues to me and I doubt I'm the only one to have encountered them. Can I expect a new release any time soon? ~Tom - 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: Where's 4.1.31?
Yoav, I haven't RM'd a release yet but if you or another RM-pro is willing to show me what is involved I might be willing to wear the hat for 4.1.31. Here is how I understand the process: - tag and create a release canidate - email to announce@ - wait 48 hours for show stoppers - delcare the RC a release - email to announce@, update jakarta site I'd even be willing to document this process if it is not already. [EMAIL PROTECTED] -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 9:13 AM To: Tomcat Developers List Subject: RE: Where's 4.1.31? Hi, You can't expect a 4.1.31 anytime soon. It's in a maintenance mode where only Spec violations and security flaws are the things that would get a new release out. We suggest the same thing we've been suggesting for a while now, upgrade to 5.x. Yoav Shapira Millennium Research Informatics - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where's 4.1.31?
The offer to do this is great, but I am more than a little curious: Why would anyone bother with a 4.1.x upgrade at this point? 5.0.27 is faster, more stable, etc, at this point as best I can tell. -- Jess Holle Keith Wannamaker wrote: Yoav, I haven't RM'd a release yet but if you or another RM-pro is willing to show me what is involved I might be willing to wear the hat for 4.1.31. Here is how I understand the process: - tag and create a release canidate - email to announce@ - wait 48 hours for show stoppers - delcare the RC a release - email to announce@, update jakarta site I'd even be willing to document this process if it is not already. [EMAIL PROTECTED] -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 9:13 AM To: Tomcat Developers List Subject: RE: Where's 4.1.31? Hi, You can't expect a 4.1.31 anytime soon. It's in a maintenance mode where only Spec violations and security flaws are the things that would get a new release out. We suggest the same thing we've been suggesting for a while now, upgrade to 5.x. Yoav Shapira Millennium Research Informatics - 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: Where's 4.1.31?
Hi, The process is already somewhat documented. For example, http://cvs.apache.org/~yoavs/tomcatReleaseManager.html is my personal notes, and http://jakarta.apache.org/commons/releases/ is mostly Jakarta-general, not specific to Commons. It deviates from the process you posted in that we usually label a release alpha or beta, leave it out in the wild for a bit to give users a chance to use it, and then call it stable (with a new announcement). Tomcat RMing is more complicated than others due to the relative complexity of the product itself compared to most Apache products. There are many ways to screw it up as I've found out myself with my first couple of releases. In addition specifically for this, you'd have to backport patches committed to CVS HEAD to the TOMCAT_4_1 branch, which has significantly different code in many key modules. But that's not the issue here. I'd probably be willing to do the release if we decide one is needed. The issue is how long we maintain things. We don't want to be in the business of maintaining old branches forever. There's been a stable Tomcat 5 for more than a year now, and the past few months we've been closing Tomcat 4.1 bugs with the statement that it's not actively maintained and users should upgrade. This is of course a standard practice in many organizations. I don't want to introduce life into the 4.1 branch, have users using 4.1.31, filing new bugs against it, etc. We have very limited support resources as-is and it makes no sense to stretch them to old branches. Yoav Shapira Millennium Research Informatics -Original Message- From: Keith Wannamaker [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 10:34 AM To: Tomcat Developers List Subject: RE: Where's 4.1.31? Yoav, I haven't RM'd a release yet but if you or another RM-pro is willing to show me what is involved I might be willing to wear the hat for 4.1.31. Here is how I understand the process: - tag and create a release canidate - email to announce@ - wait 48 hours for show stoppers - delcare the RC a release - email to announce@, update jakarta site I'd even be willing to document this process if it is not already. [EMAIL PROTECTED] -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 9:13 AM To: Tomcat Developers List Subject: RE: Where's 4.1.31? Hi, You can't expect a 4.1.31 anytime soon. It's in a maintenance mode where only Spec violations and security flaws are the things that would get a new release out. We suggest the same thing we've been suggesting for a while now, upgrade to 5.x. Yoav Shapira Millennium Research Informatics - 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: Where's 4.1.31?
Hi Jess, in our case we don't have the resources at this point in time to certify our product with a completely new code base. I'm sure different people have different reasons. Keith -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 10:38 AM To: Tomcat Developers List Subject: Re: Where's 4.1.31? The offer to do this is great, but I am more than a little curious: Why would anyone bother with a 4.1.x upgrade at this point? 5.0.27 is faster, more stable, etc, at this point as best I can tell. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Where's 4.1.31?
Because a 4.1.x upgrade is not an api change. There is much more testing involved in upgrading to a new major version than a point release. The problem is finding the time to review the (possible)effects of 5.x on your installation and all your applications when you could roll out a point release with much less effort. Charlie -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 10:38 AM To: Tomcat Developers List Subject: Re: Where's 4.1.31? The offer to do this is great, but I am more than a little curious: Why would anyone bother with a 4.1.x upgrade at this point? 5.0.27 is faster, more stable, etc, at this point as best I can tell. -- Jess Holle Keith Wannamaker wrote: Yoav, I haven't RM'd a release yet but if you or another RM-pro is willing to show me what is involved I might be willing to wear the hat for 4.1.31. Here is how I understand the process: - tag and create a release canidate - email to announce@ - wait 48 hours for show stoppers - delcare the RC a release - email to announce@, update jakarta site I'd even be willing to document this process if it is not already. [EMAIL PROTECTED] -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 9:13 AM To: Tomcat Developers List Subject: RE: Where's 4.1.31? Hi, You can't expect a 4.1.31 anytime soon. It's in a maintenance mode where only Spec violations and security flaws are the things that would get a new release out. We suggest the same thing we've been suggesting for a while now, upgrade to 5.x. Yoav Shapira Millennium Research Informatics - 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: Where's 4.1.31?
Hi Yoav, thanks for the release documentation. Do you mind if I check this in to jt-4.0? I think it would be very helpful. I am aware that 5.0 uses significantly different code which is in itself a good reason for continuing maintenance releases of 4.1. Backporting patches would be a nice side-improvement if it were done, but I think there have been enough fixes to 4.1 itself to warrant a new release without said backports. From a procedural standpoint, it is my understanding that the only vote needed is one to label a rc (ie beta or stable). Is that correct? If so, I'd like to be the 4.1.31 RM and I will go to work on syncing the release notes and get an rc out this weekend. Keith -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 10:44 AM To: Tomcat Developers List Subject: RE: Where's 4.1.31? Hi, The process is already somewhat documented. For example, http://cvs.apache.org/~yoavs/tomcatReleaseManager.html is my personal notes, and http://jakarta.apache.org/commons/releases/ is mostly Jakarta-general, not specific to Commons. It deviates from the process you posted in that we usually label a release alpha or beta, leave it out in the wild for a bit to give users a chance to use it, and then call it stable (with a new announcement). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where's 4.1.31?
Keith Wannamaker wrote: Hi Jess, in our case we don't have the resources at this point in time to certify our product with a completely new code base. Hmmm... As someone who distributes Tomcat 4.1.x and 5.0.x to a broad customer base I see Tomcat 5.0.x certification as a 100% necessity for the future/present and see the incremental effort of verifying a new 4.1.x release as wasted when it could be focused on a 5.0.x verification against past and current releases of our own product. Then again I believe I have a pretty good record of all changes that were required to our product for Tomcat 5 for future releases that could be backed into previous ones... I'm sure different people have different reasons. Yes, I echo Yoav's sentiment, though that the community needs to focus on 5.0.x and beyond and really help push mindshare away from 3.x and 4.x releases. -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where's 4.1.31?
Cox, Charlie wrote: Because a 4.1.x upgrade is not an api change. There is much more testing involved in upgrading to a new major version than a point release. The problem is finding the time to review the (possible)effects of 5.x on your installation and all your applications when you could roll out a point release with much less effort. Unless your app is not moving into the future this should have already been done with 5.x by this point (just possibly not yet deployed) -- right? -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Where's 4.1.31?
Hi, I agree with Jess, this is the wrong direction in principle. We're encouraging users to stick with 4.1.x if we do this release. Normally we have just an informal if everyone is OK with this, I'd like to push out release X on this day and then a vote on labeling it as stable. The latter being the only official vote. But in this case, I'd want to have a more general vote of should we have 4.1.x maintenance releases, given the reasons stated earlier in this thread. If we have such a vote, and if it passes, and if you decide to go ahead with this release, then you will probably assume responsibility for bugs filed against 4.1.x. This is of course unofficial, but nonetheless this type of arrangement exists with Tomcat 3.3.x. None of us care much for the 4.1.x issues now, except that Mark moved the relevant Connector-related issues from 4.1.x to 5.0.x so that they don't get dropped. This type of move, which I didn't like originally, should definitely be stopped if 4.1.x is still in active development as indicated by regular releases. Man this is a bummer going into the weekend ;) Yoav Shapira Millennium Research Informatics -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 12:15 PM To: Tomcat Developers List Subject: Re: Where's 4.1.31? Keith Wannamaker wrote: Hi Jess, in our case we don't have the resources at this point in time to certify our product with a completely new code base. Hmmm... As someone who distributes Tomcat 4.1.x and 5.0.x to a broad customer base I see Tomcat 5.0.x certification as a 100% necessity for the future/present and see the incremental effort of verifying a new 4.1.x release as wasted when it could be focused on a 5.0.x verification against past and current releases of our own product. Then again I believe I have a pretty good record of all changes that were required to our product for Tomcat 5 for future releases that could be backed into previous ones... I'm sure different people have different reasons. Yes, I echo Yoav's sentiment, though that the community needs to focus on 5.0.x and beyond and really help push mindshare away from 3.x and 4.x releases. -- Jess Holle - 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: Where's 4.1.31?
I've said too much on this already, but if you really need 4.1.x and bug fixes thereto, then why not take Tomcat 4.1.30 and patch it as necessary to address bugs of sufficient concern and deliver that to your customer/user base? That seems like a better solution for all than a 4.1.31 release. -- Jess Holle Shapira, Yoav wrote: Hi, I agree with Jess, this is the wrong direction in principle. We're encouraging users to stick with 4.1.x if we do this release. Normally we have just an informal if everyone is OK with this, I'd like to push out release X on this day and then a vote on labeling it as stable. The latter being the only official vote. But in this case, I'd want to have a more general vote of should we have 4.1.x maintenance releases, given the reasons stated earlier in this thread. If we have such a vote, and if it passes, and if you decide to go ahead with this release, then you will probably assume responsibility for bugs filed against 4.1.x. This is of course unofficial, but nonetheless this type of arrangement exists with Tomcat 3.3.x. None of us care much for the 4.1.x issues now, except that Mark moved the relevant Connector-related issues from 4.1.x to 5.0.x so that they don't get dropped. This type of move, which I didn't like originally, should definitely be stopped if 4.1.x is still in active development as indicated by regular releases. Man this is a bummer going into the weekend ;) Yoav Shapira Millennium Research Informatics - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where's 4.1.31?
Shapira, Yoav wrote: Hi, I agree with Jess, this is the wrong direction in principle. We're encouraging users to stick with 4.1.x if we do this release. Normally we have just an informal if everyone is OK with this, I'd like to push out release X on this day and then a vote on labeling it as stable. The latter being the only official vote. But in this case, I'd want to have a more general vote of should we have 4.1.x maintenance releases, given the reasons stated earlier in this thread. If we have such a vote, and if it passes, You have my -1 for a release. Althrough I agree with peoples that can't move to Tomcat 5, Tomcat 5 has been available for more that 1 year. That will be good for Tomcat if people migrate from 4.1.x to 5 and find bugs (that way they will not be carried into 5.5/6). and if you decide to go ahead with this release, then you will probably assume responsibility for bugs filed against 4.1.x. This is of course unofficial, but nonetheless this type of arrangement exists with Tomcat 3.3.x. 3.3.x has been maintained because of the fork between 3.3 and 4.x. There is no longer such tension now None of us care much for the 4.1.x issues now, except that Mark moved the relevant Connector-related issues from 4.1.x to 5.0.x so that they don't get dropped. This type of move, which I didn't like originally, should definitely be stopped if 4.1.x is still in active development as indicated by regular releases. Your time is more important on 5.x IMO :-) --Jeanfrancois Man this is a bummer going into the weekend ;) Yoav Shapira Millennium Research Informatics -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 12:15 PM To: Tomcat Developers List Subject: Re: Where's 4.1.31? Keith Wannamaker wrote: Hi Jess, in our case we don't have the resources at this point in time to certify our product with a completely new code base. Hmmm... As someone who distributes Tomcat 4.1.x and 5.0.x to a broad customer base I see Tomcat 5.0.x certification as a 100% necessity for the future/present and see the incremental effort of verifying a new 4.1.x release as wasted when it could be focused on a 5.0.x verification against past and current releases of our own product. Then again I believe I have a pretty good record of all changes that were required to our product for Tomcat 5 for future releases that could be backed into previous ones... I'm sure different people have different reasons. Yes, I echo Yoav's sentiment, though that the community needs to focus on 5.0.x and beyond and really help push mindshare away from 3.x and 4.x releases. -- Jess Holle - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where's 4.1.31?
Patching Tomcat 4.1.30 is pretty much what I have done. I spent a lot of effort getting our installation working in a stable way. And a lot of that effort was in applying patches similar to the ones that are in the baseline but have never been released. As far as moving to Tomcat 5.x, I have a ton of applications running on 4.1.x and moving them forward is no small task for me. In fact, the effort of stabilizing Tomcat 4.1.x has me gun shy. I will probably wait a year or so more until I know things are REALLY good and stable first. Eventually I will have to bite the bullet and do so but I thought it might be nice to get a 4.1.31 release (which adds a ton of stability fixes) in the interim so I could remove my custom patches. Charlie Cox hit it on the head with his response: Because a 4.1.x upgrade is not an api change. There is much more testing involved in upgrading to a new major version than a point release. The problem is finding the time to review the (possible)effects of 5.x on your installation and all your applications when you could roll out a point release with much less effort. I appreciate everyone's feedback and understand why you don't want to release a new 4.1.x. I don't necessarily agree it's a good thing since there are a lot of installations of 4.1 out there that would benefit, but I can live with it. Maybe I'll be back next year with questions about 5.1. ;-) Sorry for rocking the boat and thanks, ~Tom On Aug 20, 2004, at 10:35 AM, Jess Holle wrote: I've said too much on this already, but if you really need 4.1.x and bug fixes thereto, then why not take Tomcat 4.1.30 and patch it as necessary to address bugs of sufficient concern and deliver that to your customer/user base? That seems like a better solution for all than a 4.1.31 release. -- Jess Holle Shapira, Yoav wrote: Hi, I agree with Jess, this is the wrong direction in principle. We're encouraging users to stick with 4.1.x if we do this release. Normally we have just an informal if everyone is OK with this, I'd like to push out release X on this day and then a vote on labeling it as stable. The latter being the only official vote. But in this case, I'd want to have a more general vote of should we have 4.1.x maintenance releases, given the reasons stated earlier in this thread. If we have such a vote, and if it passes, and if you decide to go ahead with this release, then you will probably assume responsibility for bugs filed against 4.1.x. This is of course unofficial, but nonetheless this type of arrangement exists with Tomcat 3.3.x. None of us care much for the 4.1.x issues now, except that Mark moved the relevant Connector-related issues from 4.1.x to 5.0.x so that they don't get dropped. This type of move, which I didn't like originally, should definitely be stopped if 4.1.x is still in active development as indicated by regular releases. Man this is a bummer going into the weekend ;) Yoav Shapira Millennium Research Informatics - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Where's 4.1.31?
Hi Jeanfrancois, we share enthusiasm but not opinions. I believe since there are pending 4.1 patches in bugzilla and committed 4.1 fixes then there is clearly an interest in preserving the 4.1 tree in maintenance mode, and that means maintenance releases. My understanding of the jakarta PMC guidelines is that a release plan is a lazy majority vote, so your -1 would trigger a majority vote on a 4.1.31 release. So, I will issue a vote on this release. Keith -Original Message- From: Jeanfrancois Arcand [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 12:46 PM To: Tomcat Developers List Subject: Re: Where's 4.1.31? You have my -1 for a release. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Where's 4.1.31?
I really hate comments like this. I'm glad you have plenty of free time to upgrade to 5.x. When Tomcat 5.x was released, I was already midstream in replacing IIS/ASP with Tomcat 4.1 and I'm happy to be able to do just that. Now we're focusing on business needs and less on upgrading something that is already 100% more stable and less buggy than IIS. So right now from a business perspective, upgrading because it's there is not a reason to upgrade. If I perceive that 4.x is slow for my application, then I have a reason to upgrade. If I need the new listeners, status monitor, or other enhancements, then I will consider an upgrade. This is about filling a need, which 4.x does for me right now. 5.x would fill that need as well (probably improved performance - I'll need to test it) but offers nothing that I must have right now. Am I concerned about performance? Yes. Is the current 4.1 performance bad? No. There are nice-to-haves, but not enough to trump my current workload. Nothing against 5.x, but it's not a priority for me yet. I'm impartial about another 4.1 release(no problems for me), and I don't expect it to be supported forever, however I get annoyed by people assuming that I have already implemented a newer version without realizing the potential effort required. We'll get there as time allows or requirements demand but not just because it's available. Charlie -Original Message- From: Jess Holle [mailto:[EMAIL PROTECTED] Sent: Friday, August 20, 2004 12:16 PM To: Tomcat Developers List Subject: Re: Where's 4.1.31? Cox, Charlie wrote: Because a 4.1.x upgrade is not an api change. There is much more testing involved in upgrading to a new major version than a point release. The problem is finding the time to review the (possible)effects of 5.x on your installation and all your applications when you could roll out a point release with much less effort. Unless your app is not moving into the future this should have already been done with 5.x by this point (just possibly not yet deployed) -- right? -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where's 4.1.31?
Cox, Charlie wrote: I really hate comments like this. I'm glad you have plenty of free time to upgrade to 5.x. Sorry to rankle you, but let's be honest -- if you want to be able to move forward you have to keep looking ahead. Either your app is so portable (and likely thus rather simple) that feel you can just snag the latest servlet engine du jour and use it -- or you keep an eye to (and some testing time slated for) future versions of servlet engines (and other components) you use. If your app is in pure maintenance mode and you're not moving it forward, then by all means pull back 1 patch at a time as appropriate. So right now from a business perspective, upgrading because it's there is not a reason to upgrade. If I perceive that 4.x is slow for my application, then I have a reason to upgrade. If I need the new listeners, status monitor, or other enhancements, then I will consider an upgrade. Getting all the bug fixes that would be in a hypothetical 4.1.31 (and setting yourself up to get those that would be in a hypothetical 4.1.32 and those that are already in 5.0.27 for that matter) are quite possibly ample reasons for one to upgrade -- and are a lot more than because it is there. -- Jess Holle - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
