Re: [Zope-dev] 2.6.1b2?
Hi, I'd just like to know when can we expect a 2.6.1b2. It would be nice to have a new release where we don't have to patch just to get ZClasses to work. Yes, it IS indeed a problem if there is no single Zope version out there that can be used without patches. 2.6.0 has the DateTime bug, the 2.6.1b1 has new issues. I have complained a lot about the lousy release management in the past, but nobody seems to listen. Joachim P.S.: After all, it's so easy: Take a Zope version that has some bugs, fix the bugs and release it as a bugfix release. DON'T add features that might trigger new bugs. THEN start working on the next feature release. AND: THERE SHOULD NEVER, I REPEAT: NEVER BE NEW FUNCTIONALITY OR CODE CHANGES BETWEEN A FINAL BETA AND A RELEASE! IF IT IS NOT FINAL; RELEASE ANOTHER BETA!! ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] 2.6.1b2?
--On Donnerstag, 23. Januar 2003 20:31 +0100 Joachim Werner [EMAIL PROTECTED] wrote: Hi, I'd just like to know when can we expect a 2.6.1b2. It would be nice to have a new release where we don't have to patch just to get ZClasses to work. Yes, it IS indeed a problem if there is no single Zope version out there that can be used without patches. 2.6.0 has the DateTime bug, the 2.6.1b1 has new issues. I have complained a lot about the lousy release management in the past, but nobody seems to listen. Joachim P.S.: After all, it's so easy: Take a Zope version that has some bugs, fix the bugs and release it as a bugfix release. DON'T add features that might trigger new bugs. THEN start working on the next feature release. AND: THERE SHOULD NEVER, I REPEAT: NEVER BE NEW FUNCTIONALITY OR CODE CHANGES BETWEEN A FINAL BETA AND A RELEASE! IF IT IS NOT FINAL; RELEASE ANOTHER BETA!! I think the situation has improved since new features will make it only into the major 2.X.0 releases. All other releases are bugfix releases only. This is at least true for the Zope 2.6 branch were only a minor feature was added to the DateTime module. -aj ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope reference counts
Ivo van der Wijk wrote at 2003-1-22 16:10 +0100: On Wed, Jan 22, 2003 at 11:57:20AM +, Toby Dickenson wrote: Is there a way to optimize this? 1. Obviously, use fewer threads. Do you have a component that otherwise benefits from many threads? No, except that the server is pretty heavy loaded sometimes, and multiple threads should improve responsiveness (right?) When you have both short and long requests, then multiple threads help that the short requests are processed faster. When all your requests take approximately the same time, you will not be more responsive but your average response time becomes much worser (provided you can only use a single processor which is normal for Python threads). Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
